Aga MCP Server vs APEX PSI
A side-by-side look at the Aga MCP Server and APEX PSI 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 APEX PSI 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 APEX PSI when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You want tools like
seal, verify, anchor.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 61/100 · Good | 60/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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 15 | 5 |
| Full listing | View Aga MCP Server | View APEX PSI |
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
APEX PSI tools 5
sealStamp a cryptographic receipt on content. Writes to the APEX PSI append-only ledger with SHA-256 hash, Ed25519 signature, and post-quantum LMS-W4-SHA256 signature. Proves existence and integrity at a point in time — not the truth of the contents.verifyConfirm a seal's integrity against the APEX PSI append-only ledger. Accepts a receipt object (from the seal tool) or a raw SHA-256 hash. Reports whether the hash is present and anchored — integrity, not the truth of the original content.anchorRead the Bitcoin (OpenTimestamps) anchoring state of the ledger's pending Merkle roots, or — only when action:'anchor' is passed explicitly — request that pending roots be aggregated and submitted to the OTS calendars. Defaults to 'status' (read-only) so a routine call never triggers a batch write. An anchor becomes confirmed only when a real Bitcoin block is found.citeGenerate a citation for a sealed receipt in APA, BibTeX, or MLA format, citing the APEX PSI ledger entry.verify_chainIndependently verify a chain of receipts against the APEX PSI ledger. Recomputes each hash's presence and integrity and reports Merkle chain continuity. Returns a verification report — a recomputation result, not an opinion or a certification.
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"
]
}
}
}
APEX PSI
{
"mcpServers": {
"apex-psi": {
"command": "npx",
"args": [
"-y",
"apex-psi-mcp"
]
}
}
}
Frequently asked questions
Aga MCP Server is categorized under Cryptography and uses a local stdio subprocess. APEX PSI belongs to Cryptography and uses a local stdio subprocess. Pick Aga MCP Server for cryptography work and APEX PSI 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. APEX PSI 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 apex-psi 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. APEX PSI has 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars.