# AnchorRegistry

- Registry name: `io.github.AnchorRegistry/ar-mcp` · version 0.1.0
- Categories (automatic, keyword rules): Research & knowledge, Search & data
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: sse, streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.AnchorRegistry%2Far-mcp
- Server page: https://mcpstation.net/s/io.github.AnchorRegistry--ar-mcp.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://mcp.anchorregistry.ai/mcp`
- sse: `https://mcp.anchorregistry.ai/sse`

## Tools (as reported by the server, not verified)

- `ar\_verify\_arid`: 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 has been sealed, retra
- `ar\_verify\_by\_hash`: 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.
- `ar\_resolve\_tree`: 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 anchored as the root with

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html