mcp server
AnchorRegistry
On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless.
Description as published by the maintainer. Source
- version 0.1.0
- active
active — Most recent push to the repository was 2026-06-13.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
ar_resolve_tree(ar_id)- 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. Required: ar_id.
ar_verify_arid(ar_id)- 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. Required: ar_id.
ar_verify_by_hash(manifest_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. Required: manifest_hash.
Last successful function declaration observed on . Source: https://mcp.anchorregistry.ai/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.anchorregistry.ai/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-06-13 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 1 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-04-30 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-04-30 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.anchorregistry.ai | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | mcp.anchorregistry.ai |
Where to get it
Related, by what their authors tagged them
-
ActionProof
— last commit 2026-07-01, shares agentic-ai, provenance
Tamper-proof audit trail for AI agents. Signed receipts, offline-verifiable, zero backend.
-
dev.tatastu/proof
— last commit 2026-07-19, shares provenance
Stamp content with permanent, verifiable provenance. Hash locally, verify free forever.
-
io.github.Abracadabrastartup/deusproof-mcp
— last commit 2026-08-05, shares provenance
Prove your AI work existed first: timestamped, Bitcoin-anchored. Free, no account.
-
Nahuali
— last commit 2026-07-30, shares provenance
Trust-aware agent memory with evidence-backed recall, self-inspection, and audit history.
-
io.github.beeswaxpat/chronoverify
— last commit 2026-08-03, shares provenance
Verify a photo's capture time and provenance: C2PA validation, EXIF/XMP, and pixel forensics.
-
io.github.blackwell-systems/knowing
— last commit 2026-07-08, shares provenance
Content-addressed code graph with 22 MCP tools for AI agents.
-
io.github.chernistry/bernstein
— last commit 2026-08-06, shares provenance
Declarative agent orchestration for engineering teams
-
io.github.Christebob/meta-stamp-pockets
— last commit 2026-07-29, shares provenance
Attribution and settlement infrastructure for AI agent content access over HTTP 402 and MCP.
-
Intelligence Aeternum
— last commit 2026-02-25, shares provenance
AI training dataset marketplace: 2M+ museum artworks with Golden Codex enrichment
-
io.github.codex-curator/studiomcphub
— last commit 2026-05-14, shares provenance
32 creative AI tools (18 free) for agents: generate, upscale, mockup, print, watermark.
These share tags the maintainers applied themselves, such as agentic-ai, provenance. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: agentic-ai, ai-agents, blockchain, mcp-server, provenance.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json