AnchorRegistry

anchorregistry/ar-mcp

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.

tools: 3
transport: HTTP, SSE
last updated: Apr 30, 2026

View on GitHub

Install

From registry metadata

$ npx add-mcp https://mcp.anchorregistry.ai/mcp --name ar-mcp

Run in your terminal. add-mcp asks which agents to add it to (Claude Code, Codex, Cursor and more). Add -g to install it for every project.

Review the command, arguments and environment values before installing. MCP servers run with your local permissions.

Other ways

Claude Code

$ claude mcp add --transport http ar-mcp https://mcp.anchorregistry.ai/mcp

Run in your terminal. Add --scope user to make it available in every project.

Tools

Verified live · 3 tools

Verified live against the running server on Nov 6, 2026.

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_id*string

AR-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_hash*string

Hex-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_id*string

Any AR-ID in the tree. The endpoint walks up to find the root and returns the full tree.

Readme

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?"

View the full README on GitHub

Details

Repository: github.com/anchorregistry/ar-mcp
Website: anchorregistry.com
Transport: HTTP, SSE
Registry: MCP registry, active
Tools verified: Nov 6, 2026