Security & Testing

anchorregistry.com

Resolves and verifies artifact provenance records using AnchorRegistry.

x402 supported1 endpoint3 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://mcp.anchorregistry.ai/mcp

No auth detected

Capabilities

tools.listChanged

Resolve an AnchorRegistry AR-ID to its full provenance record.

Inferred read-only

Resolve an artifact by its SHA-256 manifest hash.

Inferred read-only

Resolve the full provenance tree for an AR-ID.

Inferred read-only

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.anchorregistry]
url = "https://mcp.anchorregistry.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "anchorregistry": {
      "type": "http",
      "url": "https://mcp.anchorregistry.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: anchorregistry
Remote MCP URL: https://mcp.anchorregistry.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "anchorregistry": {
      "url": "https://mcp.anchorregistry.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "anchorregistry": {
      "type": "http",
      "url": "https://mcp.anchorregistry.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "anchorregistry",
  "transport": "streamable-http",
  "url": "https://mcp.anchorregistry.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

BuiltWith Trust API v2 evidence for anchorregistry.ai was fetched 2026-07-26T07:49:37.936Z and is being refreshed.

Trust status Neutral

anchorregistry.ai is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.