Aga MCP Server vs AnchorRegistry
A side-by-side look at the Aga MCP Server 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 Aga MCP Server for cryptography work as a local process; 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 Aga MCP Server when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_server_info, get_portal_state, init_chain.
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 | 61/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 1 views 0 installs 0 upvotes |
| Tools | 15 | 3 |
| Full listing | View Aga MCP Server | View AnchorRegistry |
Tools & capabilities
Aga MCP Server tools 15
get_server_infoGet AGA server info, public keys, and portal state.get_portal_stateGet current portal state, loaded artifact info, and enforcement status.init_chainInitialize continuity chain with genesis event.attest_subjectAttest subject, generate sealed Policy Artifact. Auto-loads into portal.measure_integrityMeasure subject state, compare to sealed reference. Generates signed receipt for every measurement.revoke_artifactRevoke an active policy artifact mid-session. Portal terminates on next measurement. (NCCoE Phase 3b)verify_chainVerify continuity chain integrity.generate_evidence_bundleExport the canonical SEP evidence bundle: signed PERMITTED/DENIED tool-call receipts + Merkle proofs + a mandatory signed checkpoint, for offline third-party verification (verify_bundle_offline, aga-verify, or aga-receipt-spec/verify/verify-sep.mjs). Pin gateway_public_key to prove provenance.verify_bundle_offlineVerify a canonical SEP evidence bundle offline (full §6 algorithm: structural floor, receipt signatures, chain+ordering, leaf-recompute + Merkle bijection, signed checkpoint). Pass pinned_public_key to also prove provenance.request_claimRequest disclosure of a claim. Auto-substitutes if denied.list_claimsList available claims with sensitivity levels.delegate_to_subagentDerive a constrained policy artifact for a sub-agent. Scope can only diminish, never expand. (NCCoE constrained delegation)- +3 more on the listing page
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.
Aga MCP Server
{
"mcpServers": {
"aga-mcp-server": {
"command": "npx",
"args": [
"-y",
"@attested-intelligence/aga-mcp-server@3.6.6"
]
}
}
}
AnchorRegistry
{
"mcpServers": {
"anchorregistry": {
"url": "https://mcp.anchorregistry.ai/mcp"
}
}
}
Frequently asked questions
Aga MCP Server is categorized under Cryptography and uses a local stdio subprocess. AnchorRegistry belongs to Cryptography and uses a remote HTTP/SSE transport. Pick Aga MCP Server 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.
Aga MCP Server 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 aga-mcp-server and anchorregistry as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aga MCP Server has a quality signal of 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars. AnchorRegistry has 47/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.