AnchorRegistry

Name: AnchorRegistry
Author: AnchorRegistry

MCP serverMCP

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

by AnchorRegistryrepository ↗homepage ↗v0.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"anchorregistry","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability104/110 checks ok

when	check	result	http	latency	detail
3 h ago	mcp initialize	ok	200	600 ms	server AnchorRegistry 0.1.0 · protocol 2025-06-18 · 3 tools
10 h ago	mcp initialize	ok	200	678 ms	server AnchorRegistry 0.1.0 · protocol 2025-06-18 · 3 tools
16 h ago	mcp initialize	ok	200	464 ms	server AnchorRegistry 0.1.0 · protocol 2025-06-18 · 3 tools
23 h ago	mcp initialize	ok	200	469 ms	server AnchorRegistry 0.1.0 · protocol 2025-06-18 · 3 tools
29 h ago	mcp initialize	ok	200	567 ms	server AnchorRegistry 0.1.0 · protocol 2025-06-18 · 3 tools
35 h ago	mcp initialize	ok	200	585 ms	server AnchorRegistry 0.1.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	521 ms	server AnchorRegistry 0.1.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	439 ms	server AnchorRegistry 0.1.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	648 ms	server AnchorRegistry 0.1.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	595 ms	server AnchorRegistry 0.1.0 · protocol 2025-06-18 · 3 tools

Tools observed via MCP handshake

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 car
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. Retur
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 t

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.AnchorRegistry/ar-mcp

first seen 1 mo ago · fetched 9 h agoopen ↗

Field history (7 recent events)

1 mo ago · declared · summary → "On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless."
1 mo ago · declared · description → "On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless."
1 mo ago · declared · publisherName → "AnchorRegistry"
1 mo ago · declared · homepageUrl → "https://anchorregistry.com"
1 mo ago · declared · repoUrl → "https://github.com/anchorregistry/ar-mcp"
1 mo ago · declared · version → "0.1.0"
1 mo ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from