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