anchorregistry — Claude Code MCP server: resolve artifact provenance
The anchorregistry MCP server checks artifact provenance on Base L2 by AR-ID, SHA-256 hash, or anchor tree. It can verify an SPDX-Anchor tag in a README or model card.
no license 212 installs updated 2026-04-29
claude mcp add --transport http anchorregistry https://anchorregistry--ic3moore.run.toolsWhat anchorregistry does
It reaches https://anchorregistry--ic3moore.run.tools over HTTP and exposes three tools. ar_verify_arid turns an AR-ID into the record behind it: anchorer, timestamp, artifact type, manifest hash, and current tree state.
ar_verify_by_hash starts from the SHA-256 hash of a manifest when you have no identifier at hand. ar_resolve_tree opens a whole chain: the root plus every descendant, with relationships, types and timestamps. Papers anchored as roots, with data and models hanging below, are the obvious case.
This is v0.1, verify-only. Records get read, not written. No API key, no account, no auth on any of the three. A project that needs to create an anchor has to look elsewhere.
What it helps with
- Check an AR-ID found in a README before trusting the code
- Look up an artifact by its SHA-256 manifest hash
- Walk the provenance tree behind a research paper
- See whether an artifact was retracted or voided
- Confirm who anchored a model and when
Example prompts for the agent
- This README carries an SPDX-Anchor tag, resolve the AR-ID with
ar_verify_aridand tell me whether the artifact was retracted. - Hash the manifest and run
ar_verify_by_hashto see if it is anchored. - Pull the full tree for this AR-ID with
ar_resolve_treeand list what sits under it.
How to install anchorregistry
Platform CLI: remote server
claude mcp add --transport http anchorregistry https://anchorregistry--ic3moore.run.toolsPlatform CLI: remote server
codex mcp add anchorregistry --url https://anchorregistry--ic3moore.run.toolsConfig file
{
"mcpServers": {
"anchorregistry": {
"url": "https://anchorregistry--ic3moore.run.tools"
}
}
}Config file
{
"servers": {
"anchorregistry": {
"type": "http",
"url": "https://anchorregistry--ic3moore.run.tools"
}
}
}Platform CLI: remote server
gemini mcp add -t http anchorregistry https://anchorregistry--ic3moore.run.toolsStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about anchorregistry
How do I install anchorregistry in Claude Code?
Run claude mcp add --transport http anchorregistry https://anchorregistry--ic3moore.run.tools. Nothing else is required.
What does anchorregistry do?
It resolves the provenance of a digital artifact: the anchorer, the timestamp, the artifact type, the manifest hash, and the state of its tree.
Can it anchor a new artifact?
No. This is the verify-only v0.1 edition; the three tools read records and never write one.