AnchorRegistry
REMOTE · MCP.ANCHORREGISTRY.AI · 2 COMPONENTS · SCANNED SEP 25
On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 318 tokens (~106/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the AnchorRegistry MCP server?
AnchorRegistry is a hosted endpoint at https://mcp.anchorregistry.ai/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.anchorregistry.ai
claude mcp add --transport http anchorregistry-ar-mcp 'https://mcp.anchorregistry.ai/sse'
{
"mcpServers": {
"anchorregistry-ar-mcp": {
"url": "https://mcp.anchorregistry.ai/sse"
}
}
} {
"servers": {
"anchorregistry-ar-mcp": {
"type": "http",
"url": "https://mcp.anchorregistry.ai/sse"
}
}
} [mcp_servers.anchorregistry-ar-mcp] url = "https://mcp.anchorregistry.ai/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"anchorregistry-ar-mcp": {
"type": "remote",
"url": "https://mcp.anchorregistry.ai/sse",
"enabled": true
}
}
} openclaw mcp add anchorregistry-ar-mcp --url 'https://mcp.anchorregistry.ai/sse' --transport streamable-http
mcp_servers:
anchorregistry-ar-mcp:
url: "https://mcp.anchorregistry.ai/sse" {
"McpServers": {
"anchorregistry-ar-mcp": {
"Transport": "http",
"Url": "https://mcp.anchorregistry.ai/sse"
}
}
} assistant mcp add anchorregistry-ar-mcp -t streamable-http -u 'https://mcp.anchorregistry.ai/sse'
{
"mcpServers": {
"anchorregistry-ar-mcp": {
"type": "http",
"url": "https://mcp.anchorregistry.ai/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://mcp.anchorregistry.ai/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=anchorregistry.ai | CN=WE1,O=Google Trust Services,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 8150940dbe856b1013c93b71283af2a8 |
| SANs: anchorregistry.ai, mcp.anchorregistry.ai, *.mcp.anchorregistry.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.anchorregistry.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| anchorregistry.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcp.anchorregistry.ai/sse | Verified | 200 | |
| http (plaintext) | http://mcp.anchorregistry.ai/sse | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ar_resolve_tree ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ar_id | string | yes | Any AR-ID in the tree. The endpoint walks up to find the root and returns the full tree. |
No output schema declared.
No examples provided.
ar_verify_arid ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ar_id | string | yes | AR-ID such as AR-2026-qnPOJ1z |
No output schema declared.
No examples provided.
ar_verify_by_hash ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| manifest_hash | string | yes | Hex-encoded SHA-256 manifest hash, no 0x prefix, 64 chars |
No output schema declared.
No examples provided.
What is the AnchorRegistry MCP server?
AnchorRegistry is an MCP server listed in the public MCP registry as io.github.AnchorRegistry/ar-mcp. On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless. This page covers its hosted endpoint (https://mcp.anchorregistry.ai/sse).
Is the AnchorRegistry MCP server safe to use?
AnchorRegistry scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AnchorRegistry MCP server expose?
AnchorRegistry exposes 3 tools: ar_verify_arid, ar_verify_by_hash, ar_resolve_tree. Their descriptions and schemas cost roughly 318 tokens of context every time the server is loaded.
Does the AnchorRegistry MCP server require authentication?
No. We connected to AnchorRegistry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AnchorRegistry MCP server still maintained?
AnchorRegistry is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.