Grantex runs on your own machine — the client starts it, so there is no endpoint to ping. 104 installs a week from npm. Last commit 1 Nov 2026.
OAuth 2.0 for AI agents — scoped delegation tokens, audit trails, and revocation.
What the code does
We read the source, 22 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
new Function(browserScript.content);
SELECT grant_id FROM dpdp_consent_records
WHERE developer_id = ${developerId} AND data_principal_id = ${dataPrincipalId}
completed = subprocess.run( # noqa: S603 - the command is operator configuration
path = self._agent_key_files.get(thumbprint) or os.path.join(self._state_dir, "agents", f"{thumbprint}.json")
return yaml.load(raw, Loader=_UniqueKeyLoader) # nosec B506 - SafeLoader subclass
const files = fs.readdirSync(dirPath).filter((f: string) => f.endsWith('.json'));
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add grantex -e 'GRANTEX_API_KEY=<GRANTEX_API_KEY>' -- npx -y @grantex/mcp{
"mcpServers": {
"grantex": {
"command": "npx",
"args": [
"-y",
"@grantex/mcp"
],
"env": {
"GRANTEX_API_KEY": "<GRANTEX_API_KEY>"
}
}
}
}[mcp_servers.grantex]
command = "npx"
args = ["-y", "@grantex/mcp"]
env = { GRANTEX_API_KEY = "<GRANTEX_API_KEY>" }{
"mcpServers": {
"grantex": {
"command": "npx",
"args": [
"-y",
"@grantex/mcp"
],
"env": {
"GRANTEX_API_KEY": "<GRANTEX_API_KEY>"
}
}
}
}{
"servers": {
"grantex": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@grantex/mcp"
],
"env": {
"GRANTEX_API_KEY": "<GRANTEX_API_KEY>"
}
}
}
}Put your own value in place of
<GRANTEX_API_KEY> (Your Grantex API key).
The author’s registry entry marks it as required.
Alternatives to Grantex
same job, measured the same wayOAuth 2.1 short-link tools for AI agents with scoped tokens, approvals, audit logs, and revocation.
Identity and auth for AI agents: credentials, tokens, delegations, and permission checks.
One memory for your AI agents: scoped, expiring, revocable per-agent tokens and an audit log.
MCP adapter for Agent_Sudo: authorization, delegation, provenance, and audit for AI agents.
Task and sprint coordination for humans and AI agents, with scoped API keys and full audit trail.
Permission gateway for AI agents: scoped MCP endpoints over 27 services, audited and revocable.
Keep credentials out of AI coding agents with local approvals, scoped injection, and audit trails.
Let AI agents query and operate business systems with authorization, approval and audit trails.
Grantex — questions
Answers built from our own checks of this server.