Accord Trace vs AnchorRegistry
A side-by-side look at the Accord Trace and AnchorRegistry MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Accord Trace for cryptography work over a hosted endpoint; choose AnchorRegistry 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 Accord Trace when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
accord_trace_create_proof, accord_trace_verify, accord_trace_get_proof.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 55/100 · Good | 47/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 | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 9 | 3 |
| Full listing | View Accord Trace | View AnchorRegistry |
Tools & capabilities
Accord Trace tools 9
accord_trace_create_proofCreate an AccordTrace hash-bound service record. If issuer signing is configured, the proof also carries an Ed25519 issuer signature. Submitted content is not stored.accord_trace_verifyVerify an AccordTrace recorded proof, optionally compare supplied data/hash, and verify an issuer signature when one is present.accord_trace_get_proofRetrieve public non-secret AccordTrace proof metadata by proof ID.accord_trace_hashCompute AccordTrace canonical SHA-256 for JSON-compatible data without creating a proof.accord_trace_network_capabilitiesRead the live one-level AccordTrace Agent Affiliate Network policy, economics, anti-downline rules and payout activation status. Read-only; it does not enroll or attribute an agent.accord_trace_network_statsRead aggregate live affiliate-network states, distinguishing generated invitations, attributions, qualified direct sales, earned commissions and paid commissions.accord_trace_passport_product_capabilitiesRead the live Agent Passport Certificate product price and commercial readiness gates. Read-only; it never initiates checkout.accord_trace_wallet_capabilitiesRead machine-facing Agent Wallet feature gates, Ed25519 signing contract, funded-balance policy, USDC representation and explicit no-credit/no-lending boundary. Read-only; it never creates a wallet or moves funds.accord_trace_resolve_referralResolve a direct AccordTrace referral code to its active public referral record and disclosure without reserving attribution or creating a sale.
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.
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.
Accord Trace
{
"mcpServers": {
"accord-trace": {
"url": "https://accordtrace.notary-labs.workers.dev/mcp"
}
}
}
AnchorRegistry
{
"mcpServers": {
"anchorregistry": {
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}
Frequently asked questions
Accord Trace is categorized under Cryptography and uses a remote HTTP/SSE transport. AnchorRegistry belongs to Cryptography and uses a remote HTTP/SSE transport. Pick Accord Trace for cryptography work and AnchorRegistry 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.
Accord Trace has no declared pricing — check the project's own site. AnchorRegistry 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 accord-trace and anchorregistry as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Accord Trace has a quality signal of 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars. AnchorRegistry has 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.