Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://agtnames.com/api/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http com.agtnames-agt https://agtnames.com/api/mcpRun in a terminal.
{ "mcpServers": { "com.agtnames-agt": { "command": "npx", "args": [ "-y", "mcp-remote", "https://agtnames.com/api/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
.agt names give AI agents a resolvable identity on Polygon: an owner, on-chain records, a signed manifest and endpoints (MCP, A2A, HTTP). This repository holds the public packages, the agent skill, the manifest specification and the registry manifests behind agtnames.com.
Resolve, verify and discover .agt agent names: owner, records, signed manifest, endpoints.
| Path | What | Install |
|---|---|---|
packages/resolver | @agtnames/resolver: resolve, verify and read manifests; A2A agent card and ERC-8004 export helpers; agt-resolve CLI | npm i @agtnames/resolver |
packages/cli | @agtnames/cli: the agt command. Register a name, publish its signed manifest, set records and verify, from a terminal; signs in MetaMask through a local page, or with an env or encrypted key | npx @agtnames/cli --help |
packages/mcp | @agtnames/mcp: MCP server (stdio) with five read-only tools; the hosted Streamable-HTTP endpoint is https://agtnames.com/api/mcp | npx -y @agtnames/mcp · claude mcp add --transport http agt https://agtnames.com/api/mcp |
packages/countersign | @agtnames/countersign: scoped session grants for record writes (EIP-7702 + Delegation Framework caveats) | npm i @agtnames/countersign |
packages/snap | @agtnames/snap: MetaMask Snap that resolves name.agt in the send field to the name's on-chain address (Polygon and the major EVM chains) | MetaMask Flask until allowlisted: wallet_requestSnaps with npm:@agtnames/snap |
skills/agt-names | Agent skill teaching when and how to use the tools and the public API | npx skills add agtnames/agt |
spec/ | The .agt manifest specification (v3 draft, v1 frozen); rendered at agtnames.com/spec | |
gemini-extension.json | Gemini CLI extension bundling the MCP server | gemini extensions install https://github.com/agtnames/agt |
Docs: agtnames.com/docs · Claude Code and other clients: /docs/claude-code · framework snippets: /docs/integrations.
The MCP server is listed in the official MCP registry as com.agtnames/agt (packages/mcp/server.json), on Smithery (packages/mcp/smithery.yaml) and wherever else packages/mcp/README.md "Listed in" records.
Each package is its own npm project: cd packages/<name> && npm ci && npm run build && npm test. packages/mcp links its siblings with file: dependencies, so build resolver and countersign first. packages/cli depends on the published resolver (a registry range; its prepublishOnly refuses file:), so publish a resolver change first. packages/snap is bundled by mm-snap (its snap.manifest.json carries the bundle shasum; npm run manifest:check must pass before a commit) and tested with @metamask/snaps-jest. .github/workflows/ci.yml runs the same steps plus node scripts/check-skills.mjs.
Releases: tag resolver-v*, countersign-v*, cli-v*, mcp-v* or snap-v* (or run the release workflow by hand with dry_run). The workflow publishes every package whose version is not on npm yet through npm trusted publishing with provenance, then re-lists the MCP server with mcp-publisher (DNS-verified namespace). A new Snap version must also be re-submitted to the MetaMask Snaps Directory by hand. See the header of .github/workflows/release.yml.
Vulnerabilities: see SECURITY.md. Issues and pull requests for anything in this repository are welcome here; see CONTRIBUTING.md. Questions about the agtnames.com service itself go to the contact addresses on the site.
MIT, © 2026 AGT Domains LLC.
© 2026 MCP Directory.
Resolve, verify and discover .agt agent names: owner, records, signed manifest, endpoints.
{ "mcpServers": { "com.agtnames-agt": { "url": "https://agtnames.com/api/mcp", "headers": {} } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: AGT_CHAIN, AGT_RPC_URL, AGT_REGISTRY, AGT_IPFS_GATEWAY, AGT_TIMEOUT_MS, AGT_RATE_PER_MIN, AGT_SESSION_PASSPHRASE, AGT_SESSION_DIR.
AGT Agent Names is reached over HTTP.
Last checked 2026-11-08. Resolve, verify and discover .agt agent names: owner, records, signed manifest, endpoints.