AnchorRegistry vs Elucora Evidence API
A side-by-side look at the AnchorRegistry and Elucora Evidence API MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AnchorRegistry for cryptography work over a hosted endpoint; choose Elucora Evidence API for cryptography over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AnchorRegistry when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
ar_verify_arid, ar_verify_by_hash, ar_resolve_tree.
Choose Elucora Evidence API when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
elucora_verify, elucora_get_receipt, elucora_capture.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 47/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 3 | 4 |
| Full listing | View AnchorRegistry | View Elucora Evidence API |
Tools & capabilities
AnchorRegistry tools 3
ar_verify_aridResolve 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_hashResolve 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.ar_resolve_treeResolve 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.
Elucora Evidence API tools 4
elucora_verifyChecks whether a receipt is genuine and unaltered, and what source bytes it covers.elucora_get_receiptReads a receipt: source, sealed passage, signature status, Bitcoin anchor state.elucora_captureFetches a public HTTP(S) source, preserves the original bytes, optionally pins an exact quote or JSON Pointer, and returns a signed receipt. Consumes quota and contacts the source.elucora_attestSeals a SHA-256 hash the caller already holds, for content with no URL. Proves the content existed then and has not changed since — not where it came from. Consumes quota.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AnchorRegistry
{
"mcpServers": {
"anchorregistry": {
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}
Elucora Evidence API
{
"mcpServers": {
"elucora-evidence-api-2": {
"url": "https://elucora.com/mcp"
}
}
}
Frequently asked questions
AnchorRegistry is categorized under Cryptography and uses a remote HTTP/SSE transport. Elucora Evidence API belongs to Cryptography and uses a remote HTTP/SSE transport. Pick AnchorRegistry for cryptography work and Elucora Evidence API for cryptography.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AnchorRegistry has no declared pricing — check the project's own site. Elucora Evidence API has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add anchorregistry and elucora-evidence-api-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AnchorRegistry has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Elucora Evidence API has 48/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.