AGT agent names — Claude Code MCP server: what it does, how to install
Reads owner, records and signature-verified agent manifest from the .agt registry. Works over HTTP or stdio.
claude mcp add --transport http agt https://agtnames.com/api/mcpWhat AGT agent names does
The server returns the owner of an agent name, its on-chain records (Polygon mainnet), and a manifest with verified signature: endpoints, keys, payment data. Five tools — agt_resolve, agt_manifest, agt_endpoint, agt_available, agt_namehash. Read-only. When the manifest signature does not match the registry owner, status becomes unverified and data comes back inside an untrusted envelope.
An HTTP endpoint at https://agtnames.com/api/mcp needs no installation. The stdio variant via npx -y @agtnames/mcp works in Cursor, Copilot, Windsurf, Cline, Zed. Optional variables AGT_RPC_URL, AGT_TIMEOUT_MS, AGT_IPFS_GATEWAY go in env.
Nine write tools unlock with AGT_SESSION_PASSPHRASE: create a session key, import a signed grant from the name owner, write a text record, address, endpoint, manifest URI or wallet. The grant is bounded by name list, setters, expiry and call count; the owner can revoke it in one transaction. Without the variable the server stays read-only.
What it helps with
- check the owner and expiry of a .agt agent name from the registry
- fetch a signed agent manifest with endpoints and keys
- see whether a name is available for registration
- write a new endpoint or wallet address for an agent via countersign grant
- read the pricing policy of an agent from its verified manifest
Example prompts for the agent
- Look up the owner and records for
alice.agt - Check if the name
bot-123.agtis available for registration - Get the MCP endpoint and pricing for agent
support.agt
How to install AGT agent names
1Platform CLI: remote server
claude mcp add --transport http agt https://agtnames.com/api/mcp2Platform CLI
claude mcp add --env AGT_CHAIN=<AGT_CHAIN> --env AGT_RPC_URL=<AGT_RPC_URL> --env AGT_REGISTRY=<AGT_REGISTRY> --env AGT_IPFS_GATEWAY=<AGT_IPFS_GATEWAY> --env AGT_TIMEOUT_MS=<AGT_TIMEOUT_MS> --transport stdio mcp -- npx -y @agtnames/mcpReplace <…> with your own values. 3 more environment variables are in the server README
1Platform CLI: remote server
codex mcp add mcp --url https://agtnames.com/api/mcp2Platform CLI
codex mcp add mcp --env AGT_CHAIN=<AGT_CHAIN> --env AGT_RPC_URL=<AGT_RPC_URL> --env AGT_REGISTRY=<AGT_REGISTRY> --env AGT_IPFS_GATEWAY=<AGT_IPFS_GATEWAY> --env AGT_TIMEOUT_MS=<AGT_TIMEOUT_MS> -- npx -y @agtnames/mcpReplace <…> with your own values. 3 more environment variables are in the server README
Config file
{
"mcpServers": {
"mcp": {
"url": "https://agtnames.com/api/mcp"
}
}
}{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@agtnames/mcp"
],
"env": {
"AGT_CHAIN": "<AGT_CHAIN>",
"AGT_RPC_URL": "<AGT_RPC_URL>",
"AGT_REGISTRY": "<AGT_REGISTRY>",
"AGT_IPFS_GATEWAY": "<AGT_IPFS_GATEWAY>",
"AGT_TIMEOUT_MS": "<AGT_TIMEOUT_MS>"
}
}
}
}Replace <…> with your own values. 3 more environment variables are in the server README
Config file
{
"servers": {
"mcp": {
"type": "http",
"url": "https://agtnames.com/api/mcp"
}
}
}{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agtnames/mcp"
],
"env": {
"AGT_CHAIN": "<AGT_CHAIN>",
"AGT_RPC_URL": "<AGT_RPC_URL>",
"AGT_REGISTRY": "<AGT_REGISTRY>",
"AGT_IPFS_GATEWAY": "<AGT_IPFS_GATEWAY>",
"AGT_TIMEOUT_MS": "<AGT_TIMEOUT_MS>"
}
}
}
}Replace <…> with your own values. 3 more environment variables are in the server README
1Platform CLI: remote server
gemini mcp add -t http mcp https://agtnames.com/api/mcp2Platform CLI
gemini mcp add -e AGT_CHAIN=<AGT_CHAIN> -e AGT_RPC_URL=<AGT_RPC_URL> -e AGT_REGISTRY=<AGT_REGISTRY> -e AGT_IPFS_GATEWAY=<AGT_IPFS_GATEWAY> -e AGT_TIMEOUT_MS=<AGT_TIMEOUT_MS> mcp npx -y @agtnames/mcpReplace <…> with your own values. 3 more environment variables are in the server README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about AGT agent names
How to install AGT agent names in Claude Code?
Add the HTTP endpoint with claude mcp add --transport http agt https://agtnames.com/api/mcp. For stdio run `claude mcp add --env AGT_CHAIN=<AGT_CHAIN> --env AGT_RPC_URL=<AGT_RPC_URL> --env AGT_REGISTRY=<AGT_REGISTRY> --env AGT_IPFS_GATEWAY=<AGT_IPFS_GATEWAY> --env AGT_TIMEOUT_MS=<AGT_TIMEOUT_MS> --transport stdio mcp -- npx -y @agtnames/mcp`.
What does AGT agent names do?
The server reads the owner, records and manifest of an agent name from the .agt blockchain registry, verifies the manifest signature and returns endpoints, keys, payment data. Optionally writes new data via a countersign grant.
Which network does AGT agent names use?
Polygon mainnet by default. Switch to another network by setting AGT_CHAIN, AGT_REGISTRY and AGT_RPC_URL in the environment.