AnchorRegistry
About
AnchorRegistry is the open provenance layer for the agentic economy. Every digital artifact — code, research, data, models, media, agents, transactions — can be anchored to Base L2 with a permanent, machine-resolvable identifier (an AR-ID). When an AI assistant encounters an SPDX
Details
- Author
- AnchorRegistry
- Downloads
- 327
- Categories
- Search
Jump to
- Resolve AR-IDs to full provenance records (title, author, manifest hash, timestamp)
- Look up artifacts by SHA-256 manifest hash when no AR-ID is known
- Resolve full provenance trees including descendants, relationships, and timestamps
- Free to use — no API key or account required
- Smart contract on Base L2 with peer-reviewed game-theoretic security
- Open-source server (MIT) and contract (BUSL-1.1) on GitHub
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
AnchorRegistryCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install as an HTTP connector in Claude Desktop (Settings > Connectors > Add custom connector, URL https://mcp.anchorregistry.ai/mcp) or configure the MCP server in Cursor, VS Code, or Claude Code using the same URL. Once connected, call any of three tools: ar_verify_arid to resolve an AR‑ID, ar_verify_by_hash to look up by SHA‑256 manifest hash, or ar_resolve_tree to resolve a full provenance tree.
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.
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 its training dataset and model weights as children.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"anchorregistry": {
"anchorregistry": {
"type": "http",
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}
}McpServers
{
"anchorregistry": {
"type": "http",
"url": "https://mcp.anchorregistry.ai/mcp"
}
}What it does
AnchorRegistry's MCP server lets any AI assistant resolve provenance records for artifacts anchored on Base L2. When you see anSPDX-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
``json
{
"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.Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
