← Discover MCPs and Agents
A
MCPOtherMCP Registry

AGT agent names

Resolve, verify and discover .agt agent names: owner, records, signed manifest, endpoints.

Links

README

From the repo.

agt — open-source packages for .agt agent names

.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.

PathWhatInstall
packages/resolver@agtnames/resolver: resolve, verify and read manifests; A2A agent card and ERC-8004 export helpers; agt-resolve CLInpm i @agtnames/resolver
packages/mcp@agtnames/mcp: MCP server (stdio) with five read-only tools; the hosted Streamable-HTTP endpoint is https://agtnames.com/api/mcpnpx -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-namesAgent skill teaching when and how to use the tools and the public APInpx skills add agtnames/agt
spec/The .agt manifest specification (v3 draft, v1 frozen); rendered at agtnames.com/spec
gemini-extension.jsonGemini CLI extension bundling the MCP servergemini extensions install https://github.com/agtnames/agt

Docs: agtnames.com/docs · Claude Code and other clients: /docs/claude-code · framework snippets: /docs/integrations.

Registry listings

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.

Development

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/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*, 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.

Security and contributing

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.

Config for your environment

Use the endpoint URL below in your config. No API key — you connect directly.

Tool

OS

Config file: ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://agtnames.com/api/mcp"
    }
  }
}

Paste into mcpServers in the config file. Restart Cursor after saving.

If this MCP is also published on mcpchannel.ai, you can subscribe from Browse and use the gateway config there instead.