# AnchorRegistry

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

- name: io.github.AnchorRegistry/ar-mcp
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 90/100
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.AnchorRegistry%2Far-mcp
- tools: https://api.protogrid.dev/v1/servers/io.github.AnchorRegistry%2Far-mcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "ar-mcp": {
      "type": "http",
      "url": "https://mcp.anchorregistry.ai/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 65
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-99% ~updated-173d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: ar_verify_arid (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ar_resolve_tree (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ar_verify_by_hash (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
- pass `tools.token_cost`: about 441 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 3, about 441 tokens to load them all
- tool set hash: bc7a88abc1b3d100a9799985f5f7ea91
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.AnchorRegistry/ar-mcp.svg)](https://protogrid.dev/servers/io.github.AnchorRegistry/ar-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mcp.anchorregistry.ai/mcp (streamable-http, auth none, reachable true, uptime30d 0.95535713)
- https://mcp.anchorregistry.ai/sse (sse, auth none, reachable true, uptime30d 0.99159664)

## Packages

_none_

## Tools (3)

- `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 anchored as the root with its training dataset and model weights as children.
- `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 has been sealed, retracted, voided, or affirmed. Free, public, no auth required.
- `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.