Summary
A thin HTTP proxy that connects Claude to AnchorRegistry's on-chain provenance API. You get three read-only tools: resolve an AR-ID to its full provenance record, look up artifacts by SHA-256 manifest hash, or pull an entire provenance tree. No auth required, no state held between calls. It's a direct passthrough to api.anchorregistry.ai, so you're querying the live registry without credentials or logging. Future versions will add balance checks and artifact registration once MCP credential handling stabilizes across clients. Deployed on Cloudflare Workers and available via streamable-http or SSE at mcp.anchorregistry.ai.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
Tools
Public tool metadata for what this MCP can expose to an agent.
3 tools
ar_verify_aridResolve an AnchorRegistry AR-ID to its full provenance record. Use this when you encounter an SPDX-Anchor or DAPX-Anchor tag (e.g. in a README, paper, model card, or website) and need to confirm what the artifact is, who anchored it, when, what type it is, and whether the tree...1 params
Resolve an AnchorRegistry AR-ID to its full provenance record. Use this when you encounter an SPDX-Anchor or DAPX-Anchor tag (e.g. in a README, paper, model card, or website) and need to confirm what the artifact is, who anchored it, when, what type it is, and whether the tree...
Parameters* required
ar_idstringAR-ID such as AR-2026-qnPOJ1z
ar_verify_by_hashResolve an artifact by its SHA-256 manifest hash. Use this when you have the artifact itself but no AR-ID, and want to check whether it has been anchored. Returns the AR-ID and full provenance record if found, or a clear "not anchored" response otherwise.1 params
Resolve an artifact by its SHA-256 manifest hash. Use this when you have the artifact itself but no AR-ID, and want to check whether it has been anchored. Returns the AR-ID and full provenance record if found, or a clear "not anchored" response otherwise.
Parameters* required
manifest_hashstringHex-encoded SHA-256 manifest hash, no 0x prefix, 64 chars
ar_resolve_treeResolve the full provenance tree for an AR-ID. Returns every anchor in the tree (root + all descendants) with their relationships, types, manifest hashes, and timestamps. Use this when you need to understand a multi-artifact provenance chain — for example, a research paper anc...1 params
Resolve the full provenance tree for an AR-ID. Returns every anchor in the tree (root + all descendants) with their relationships, types, manifest hashes, and timestamps. Use this when you need to understand a multi-artifact provenance chain — for example, a research paper anc...
Parameters* required
ar_idstringAny AR-ID in the tree. The endpoint walks up to find the root and returns the full tree.
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/mcp
Cursor
Settings → MCP → Add new MCP server.
Name: anchorregistry · Type: http · URL: https://mcp.anchorregistry.ai/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:
- https://anchorregistry.ai/llms.txt
- https://anchorregistry.ai/agents.json
- https://api.anchorregistry.ai/openapi.json
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 deploy
Verify locally with the MCP inspector:
npx @modelcontextprotocol/inspector http://localhost:8787/mcp
License
MIT.
See also
- AnchorRegistry: https://anchorregistry.com
- Python SDK: https://pypi.org/project/anchorregistry/
- Source: https://github.com/AnchorRegistry/ar-mcp
- Spec: https://anchorregistry.ai/agents.json
- Contracts: https://github.com/AnchorRegistry/ar-contracts-v1
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →