MCP.Market

AnchorRegistry MCP server

online · 100% uptime
by AnchorRegistry·io.github.AnchorRegistry/ar-mcp·v0.1.0
No reviews yet

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

B80/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed AnchorRegistry yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

AnchorRegistry tools (3)

write = sends, deletes, buys or posts
  • ar_resolve_treeFree

    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.

  • ar_verify_aridFree

    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_hashFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1764ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 106 days ago8/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How AnchorRegistry compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
3
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
739 ms
faster than 18% of 30,031 servers

What its tools let an agent do: 3 read

Install AnchorRegistry in Claude Code, Cursor or VS Code

claude mcp add --transport http ar-mcp https://mcp.anchorregistry.ai/mcp
Add to Cursor

What the publisher says

From the AnchorRegistry repository's README, as published. We do not edit it. Read it on GitHub

ar-mcp

The AnchorRegistry MCP server. Resolve any AR-ID, manifest hash, or provenance tree from any MCP-compatible AI client.

Endpoint: https://mcp.anchorregistry.ai/mcp

Install

Claude Desktop

Settings → Integrations → Add server. URL: https://mcp.anchorregistry.ai/mcp

Claude Code

claude mcp add --transport http anchorregistry https://mcp.anchorregistry.ai/mcp

Cursor

Settings → MCP → Add new MCP server. Name: anchorregistry · Type: http · URL: https://mcp.anchorregistry.ai/mcp

Tools

arverifyarid

Resolves an AR-ID to its full provenance record.

"What's at AR-2026-qnPOJ1z?"

arverifyby_hash

Resolves an artifact by SHA-256 manifest hash.

arresolvetree

Returns the full provenance tree for any AR-ID.

How it works

ar-mcp is a thin proxy. Every tool call hits api.anchorregistry.ai and returns the JSON unchanged. No data is logged, no credentials are stored, no state is held between requests.

The full surface is documented at:

  • https://anchorregistry.ai/llms.txt
  • https://anchorregistry.ai/agents.json
  • https://api.anchorregistry.ai/openapi.json

Roadmap

v0.2 will add archeckbalance and arregisterartifact once the MCP credential-handling pattern stabilizes across clients. arsealtree is deferred indefinitely (irreversible action; needs robust user-confirmation primitives the protocol does not yet provide). The deferred tools are fully implemented and live in src/future-tools.ts — enabling them is a one-line flip per tool.

Develop

npm install
npm test           # vitest, hits live api.anchorregistry.ai
npm run type-check
npm run dev        # wrangler dev — http://localhost:8787
npm run deploy     # wrangler deploy

Verify locally with the MCP inspector:

npx @modelcontextprotocol/inspector http://localhost:8787/mcp

License

MIT.

See also

  • AnchorRegistry: https://anchorregistry.com
  • Python SDK: https://pypi.org/project/anchorregistry/
  • Source: https://github.com/AnchorRegistry/ar-mcp
  • Spec: https://anchorregistry.ai/agents.json
  • Contracts: https://github.com/AnchorRegistry/ar-contracts-v1

Nothing above is checked by us. What we check is on the safety report.

AnchorRegistry: common questions

Is AnchorRegistry MCP server safe?
Mostly: it is graded B (80/100). Read the AnchorRegistry safety report
How do I install AnchorRegistry?
It runs remotely at mcp.anchorregistry.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does AnchorRegistry need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is AnchorRegistry maintained?
The last commit was 144 days ago (2026-06-13). The latest release is v0.1.0.
Is AnchorRegistry up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does AnchorRegistry compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.