# anchorregistry

The anchorregistry MCP server checks artifact provenance on Base L2 by AR-ID, SHA-256 hash, or anchor tree. It can verify an SPDX-Anchor tag in a README or model card.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · 212 installs
- Author: ic3moore
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://smithery.ai/server/ic3moore/anchorregistry
- Updated: 2026-04-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/mcp/anchorregistry

## What it does

It reaches `https://anchorregistry--ic3moore.run.tools` over HTTP and exposes three tools. `ar_verify_arid` turns an AR-ID into the record behind it: anchorer, timestamp, artifact type, manifest hash, and current tree state.

\`ar_verify_by_hash` starts from the SHA-256 hash of a manifest when you have no identifier at hand. `ar_resolve_tree` opens a whole chain: the root plus every descendant, with relationships, types and timestamps. Papers anchored as roots, with data and models hanging below, are the obvious case.

This is v0.1, verify-only. Records get read, not written. No API key, no account, no auth on any of the three. A project that needs to create an anchor has to look elsewhere.

## Requirements
- Remote server: `https://anchorregistry--ic3moore.run.tools`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http anchorregistry https://anchorregistry--ic3moore.run.tools
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add anchorregistry --url https://anchorregistry--ic3moore.run.tools
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "anchorregistry": {
            "url": "https://anchorregistry--ic3moore.run.tools"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "anchorregistry": {
            "type": "http",
            "url": "https://anchorregistry--ic3moore.run.tools"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http anchorregistry https://anchorregistry--ic3moore.run.tools
```

## When to use it
- Check an AR-ID found in a README before trusting the code
- Look up an artifact by its SHA-256 manifest hash
- Walk the provenance tree behind a research paper
- See whether an artifact was retracted or voided
- Confirm who anchored a model and when

## Example prompts
- This README carries an SPDX-Anchor tag, resolve the AR-ID with `ar_verify_arid` and tell me whether the artifact was retracted.
- Hash the manifest and run `ar_verify_by_hash` to see if it is anchored.
- Pull the full tree for this AR-ID with `ar_resolve_tree` and list what sits under it.

## Similar
- [Proof of Stock](https://affpapa.org/en/nevibecode/mcp/proof-of-stock.md) — MCP server · ★ 12 repo stars
- [TapeAPI: signed BNB Chain reads](https://affpapa.org/en/nevibecode/mcp/tapeapi-signed-bnb-chain-reads.md) — MCP server · ★ 6 repo stars
- [FactStamp](https://affpapa.org/en/nevibecode/mcp/factstamp.md) — MCP server
- [IP Geolocation — Country, City, ISP, VPN Detection](https://affpapa.org/en/nevibecode/mcp/ip-geolocation-country-city-isp-vpn-detection.md) — MCP server · 4543 installs
- [three.ws Provenance](https://affpapa.org/en/nevibecode/mcp/threews-provenance.md) — MCP server · ★ 284 repo stars
- [akf](https://affpapa.org/en/nevibecode/mcp/akf.md) — MCP server · ★ 22 repo stars

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
