AnchorRegistry

io.github.AnchorRegistry/ar-mcp · v0.1.0 · crypto-web3

AnchorRegistry is healthy: it completed an MCP handshake in 1733 ms and exposes 3 tools.

On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless.

Endpoint: https://mcp.anchorregistry.ai/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count3
Latency1733 ms
Last checked (UTC)2026-10-15T00:35:47.690Z

Health history

Checked (UTC)StatusLatencyError
2026-10-15T00:35:47.690ZHealthy1733

Tools (3)

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 has been sealed, retra
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.
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 anchored as the root with