AnchorRegistry
by anchorregistry.ai in Onchain & crypto
On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless.
https://mcp.anchorregistry.ai/mcp- Tools
- 3
- open to any client
- Uptime
- 100%
- last 30 days
- Response time
- 973 ms
- 1.5 s slowest 5%
- Last check
- Passed
- 3 h ago, next in 3 h
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"anchorregistry": {
"type": "http",
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}3 tools
- 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…
- 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…
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 3 h ago | Passed | 200 | 1.0 s |
| 12 h ago | Passed | 200 | 948 ms |
| 22 h ago | Passed | 200 | 769 ms |
| 31 h ago | Passed | 200 | 713 ms |
| 41 h ago | Passed | 200 | 1.5 s |
Show 8 older checks
| 2 days ago | Passed | 200 | 872 ms |
| 3 days ago | Passed | 200 | 976 ms |
| 3 days ago | Passed | 200 | 937 ms |
| 3 days ago | Passed | 200 | 1.4 s |
| 4 days ago | Passed | 200 | 1.2 s |
| 4 days ago | Passed | 200 | 881 ms |
| 4 days ago | Passed | 200 | 1.1 s |
| 5 days ago | Passed | 200 | 973 ms |