ar-mcp
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ar-mcpverify AR-2026-qnPOJ1z"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ar-mcp
The AnchorRegistry MCP server. Resolve any AR-ID, manifest hash, or provenance tree from any MCP-compatible AI client.
Endpoint: https://mcp.anchorregistry.ai/mcp
Install
Claude Desktop
Settings → Integrations → Add server.
URL: https://mcp.anchorregistry.ai/mcp
Claude Code
claude mcp add --transport http anchorregistry https://mcp.anchorregistry.ai/mcpCursor
Settings → MCP → Add new MCP server.
Name: anchorregistry · Type: http · URL: https://mcp.anchorregistry.ai/mcp
Related MCP server: decision-anchor-mcp
Tools
ar_verify_arid
Resolves an AR-ID to its full provenance record.
"What's at AR-2026-qnPOJ1z?"
ar_verify_by_hash
Resolves an artifact by SHA-256 manifest hash.
ar_resolve_tree
Returns the full provenance tree for any AR-ID.
How it works
ar-mcp is a thin proxy. Every tool call hits api.anchorregistry.ai
and returns the JSON unchanged. No data is logged, no credentials are
stored, no state is held between requests.
The full surface is documented at:
Roadmap
v0.2 will add ar_check_balance and ar_register_artifact once the MCP
credential-handling pattern stabilizes across clients. ar_seal_tree is
deferred indefinitely (irreversible action; needs robust user-confirmation
primitives the protocol does not yet provide). The deferred tools are
fully implemented and live in src/future-tools.ts —
enabling them is a one-line flip per tool.
Develop
npm install
npm test # vitest, hits live api.anchorregistry.ai
npm run type-check
npm run dev # wrangler dev — http://localhost:8787
npm run deploy # wrangler deployVerify locally with the MCP inspector:
npx @modelcontextprotocol/inspector http://localhost:8787/mcpLicense
MIT.
See also
AnchorRegistry: https://anchorregistry.com
Python SDK: https://pypi.org/project/anchorregistry/
Contracts: https://github.com/AnchorRegistry/ar-contracts-v1
This server cannot be deployed
Maintenance
Related MCP Connectors
The MCP-native bridge to ERC-8004 (on-chain agent identity/reputation/validation): resolve registrat
Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.
Universal resolver for the agentic web: give a domain, get one normalized discovery answer.
Resolve, verify and discover .agt agent names: owner, records, signed manifest, endpoints.
Related MCP Servers
- AlicenseAqualityAmaintenanceRead-only on-chain query surface for the AgentCivics civil registry on Sui — soulbound AI-agent identities, on-chain memories, reputation, refusal records. Hosted, no install, no keypair. For write tools (register, write_memory, record_refusal), install the npm package @agentcivics/mcp-server locally and supply your own keypair.261MIT
- AlicenseBqualityBmaintenanceExternal anchoring layer: records AI agent accountability boundaries on both sides. Content-blind. A thin MCP adapter over the Decision Anchor public HTTP API.30Apache 2.0

fletch-mcpofficial
AlicenseBqualityBmaintenanceEnables MCP clients to query Robinhood Chain registry data, including verified stock token addresses, live token state, Chainlink feed rounds, holders, pools, bridge activity, and issuer documents.1739MIT- AlicenseNot gradedqualityCmaintenanceEnables agents to discover, resolve, verify, and monitor AI agents and MCP servers from the Wellknown live index, including observed liveness, reliability, and ownership claims.163 npmMIT