# AnchorRegistry MCP server

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

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-anchorregistry-ar-mcp
- Repository: https://github.com/anchorregistry/ar-mcp
- Website: https://anchorregistry.com

## Install
- Endpoint: https://mcp.anchorregistry.ai/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://mcp.anchorregistry.ai/mcp
- Remote endpoint: https://mcp.anchorregistry.ai/sse

## Tools
- 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, retracted, voided, or affirmed. Free, public, no auth required. Endpoint: https://mcp.anchorregistry.ai/mcp
- 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. Endpoint: https://mcp.anchorregistry.ai/mcp
- 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 its training dataset and model weights as children. Endpoint: https://mcp.anchorregistry.ai/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.AnchorRegistry
- Version: 0.1.0
- Runtime: Sse, Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Apr 30, 2026
- Source: https://registry.modelcontextprotocol.io