What it does
The server exposes three tools. ar_verify_arid returns the full provenance record for an AR-ID, ar_verify_by_hash resolves an artifact from its SHA-256 manifest hash, and ar_resolve_tree returns the full provenance tree for an AR-ID. It works as a thin proxy: each tool call is sent to the AnchorRegistry API and the JSON response is returned unchanged.
It suits a user who wants to check what an AR-ID refers to, confirm an artifact from its hash, or trace its provenance tree from inside an MCP-compatible AI client. The publisher states that no data is logged, no credentials are stored and no state is kept between requests. The full API is documented in the publisher's llms.txt, agents.json and OpenAPI files.
Setup means adding the HTTP endpoint as an MCP server in a compatible client such as Claude Desktop, Claude Code or Cursor. No account or API key is needed, as the server is authless. The publisher describes local checks with the MCP inspector. The code is released under the MIT license.
Limitations and requirements
Requires an MCP-compatible AI client and a connection to the AnchorRegistry API. Only the three lookup tools are currently available: ar_check_balance and ar_register_artifact are planned for v0.2, and ar_seal_tree is deferred indefinitely.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
AnchorRegistry
On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it