AnchorRegistry is a remote MCP server that gives an AI agent 3 tools, among them ar_resolve_tree, ar_verify_arid, ar_verify_by_hash. It answers at https://mcp.anchorregistry.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 chai Inputs: ar_id |
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, Inputs: ar_id |
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" resp Inputs: manifest_hash |
Every block below points at https://mcp.anchorregistry.ai/mcp. Pick your client and copy.
claude mcp add --transport http anchorregistry https://mcp.anchorregistry.ai/mcp
{
"mcpServers": {
"anchorregistry": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.anchorregistry.ai/mcp"]
}
}
}{
"mcpServers": {
"anchorregistry": {
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}{
"servers": {
"anchorregistry": {
"type": "http",
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}{
"context_servers": {
"anchorregistry": {
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}{
"mcpServers": {
"anchorregistry": {
"serverUrl": "https://mcp.anchorregistry.ai/mcp"
}
}
}{
"mcpServers": {
"anchorregistry": {
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}name: AnchorRegistry
version: 0.0.1
schema: v1
mcpServers:
- name: AnchorRegistry
type: streamable-http
url: https://mcp.anchorregistry.ai/mcp{
"mcpServers": {
"anchorregistry": {
"httpUrl": "https://mcp.anchorregistry.ai/mcp"
}
}
}{
"mcpServers": {
"anchorregistry": {
"type": "http",
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}{
"mcpServers": {
"anchorregistry": {
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.anchorregistry.ai%2Fmcp&type=streamable_http&id=anchorregistry&name=AnchorRegistry
It answered our last check on 19 October 2026 in 417 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
3, as returned by the server's own tools/list on 12 September 2026: ar_resolve_tree, ar_verify_arid, ar_verify_by_hash.
It answered our last check on 19 October 2026 in 417 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.anchorregistry.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.anchorregistry. Endpoint host: mcp.anchorregistry.ai. ARD identifier: urn:air:io.github.anchorregistry:mcp:ar-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.