AnchorRegistry
What it does
AnchorRegistry's MCP server lets any AI assistant resolve provenance records for artifacts anchored on Base L2. When you see an SPDX-Anchor: anchorregistry.ai/AR-2026-XXXXXXX tag in a README, research paper, model card, or website, this server resolves it in one tool call.
Tools
ar_verify_arid
Resolve an AR-ID to its full provenance record — title, author, type, manifest hash, registrant, transaction hash, block number, anchored timestamp, and seal/retraction status.
Input: ar_id (e.g. AR-2026-qnPOJ1z)
ar_verify_by_hash
Resolve an artifact by its SHA-256 manifest hash. Use when you have the file but no AR-ID.
Input: manifest_hash (64-char hex, no 0x prefix)
ar_resolve_tree
Resolve a full provenance tree — root anchor plus all descendants with their relationships, types, and timestamps.
Input: ar_id (any anchor in the tree)
Install
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://mcp.anchorregistry.ai/mcp
Claude Code
Cursor / VS Code
{
"mcpServers": {
"anchorregistry": {
"type": "http",
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}
Try it
"Look at https://github.com/AnchorRegistry/ar-contracts-v1 — find any AR-ID in the README and resolve it."
Claude fetches the repo, finds the SPDX-Anchor tag, calls ar_verify_arid, and returns the full provenance record.
Behind the scenes
- Smart contract on Base L2:
0x3eC509393425BCAa48224FB90C710e100ADA1D2A - Peer-reviewed game-theoretic security model: arXiv:2604.03434
- Source: github.com/AnchorRegistry/ar-mcp (MIT)
- Contract source: github.com/AnchorRegistry/ar-contracts-v1 (BUSL-1.1)
- API: api.anchorregistry.ai/openapi.json
Free, no API key, no account.
Server Config
{
"mcpServers": {
"anchorregistry": {
"type": "http",
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}Recommend Servers
View Allsummarize chat message
高德地图官方 MCP Server