Aga MCP Server vs Proof Layer
A side-by-side look at the Aga MCP Server and Proof Layer 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 Proof Layer for cryptography as a local process. 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 Proof Layer when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PROOF_LAYER_API_KEY, PROOF_LAYER_API_URL. - You want tools like
pl_evaluate, pl_get_receipt, pl_verify_receipt.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 61/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | PROOF_LAYER_API_KEYPROOF_LAYER_API_URL |
| 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 | 15 | 8 |
| Full listing | View Aga MCP Server | View Proof Layer |
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
Proof Layer tools 8
pl_evaluateSubmit an AI agent action proposal to Proof Layer for governance evaluation. Returns a cryptographically-signed receipt with a verdict of EXECUTE, BLOCK, REVIEW, or SHADOW. Use this before any consequential agent action (sending emails, modifying data, making payments, etc.).pl_get_receiptRetrieve a Proof Layer audit receipt by its UUID. Returns the full receipt including verdict, signature, and policy pack hash.pl_verify_receiptCryptographically verify a Proof Layer receipt. Checks the Ed25519 signature and confirms the signing key is ACTIVE. Returns valid: true/false with a reason.pl_list_receiptsList recent Proof Layer audit receipts for the authenticated tenant. Supports filtering by agent and verdict.pl_usageGet current Proof Layer quota usage — receipts used, receipts remaining, credit balance, billing cycle dates, and plan tier.pl_list_policy_packsList all governance policy packs for the authenticated tenant, including which one is currently active.pl_create_planA human approves a governed plan — a scoped, time-bounded set of future actions across named agents. Returns a plan_id and JTI that agents use to request delegation receipts via pl_delegate. Scope patterns support wildcards: 'build:*' authorizes any action starting with 'build:'.pl_delegateAn agent requests authorization to perform a specific action under a parent plan. Returns 'ok' with a signed receipt (proceed with the action), 'checkpoint_required' (human must re-approve this specific action), or 'denied' (agent or action not authorized under the plan).
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"
]
}
}
}
Proof Layer
{
"mcpServers": {
"proof-layer": {
"command": "npx",
"args": [
"-y",
"@proof-layer/mcp@latest"
],
"env": {
"PROOF_LAYER_API_KEY": "YOUR_PROOF_LAYER_API_KEY_HERE",
"PROOF_LAYER_API_URL": "YOUR_PROOF_LAYER_API_URL_HERE"
}
}
}
}
Frequently asked questions
Aga MCP Server is categorized under Cryptography and uses a local stdio subprocess. Proof Layer belongs to Cryptography and uses a local stdio subprocess. Pick Aga MCP Server for cryptography work and Proof Layer 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. Proof Layer 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 proof-layer 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. Proof Layer has 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars.