Aga MCP Server vs PDF Verify (PDF Agent Stack)
A side-by-side look at the Aga MCP Server and PDF Verify (PDF Agent Stack) 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 PDF Verify (PDF Agent Stack) 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 PDF Verify (PDF Agent Stack) when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PDF_VERIFY_TRUST_ANCHORS, PDF_VERIFY_VERAPDF. - You want tools like
verify_signatures, verify_integrity, detect_pades_level.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 61/100 · Good | 52/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 | PDF_VERIFY_TRUST_ANCHORSPDF_VERIFY_VERAPDF |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 15 | 7 |
| Full listing | View Aga MCP Server | View PDF Verify (PDF Agent Stack) |
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
PDF Verify (PDF Agent Stack) tools 7
verify_signaturesCryptographic verification, trust chain evaluation against trust anchors, revocation checking (embedded OCSP/CRL or online), RFC 3161 timestamp verificationverify_integrityTamper detection: incremental updates, changes after signing, **DocMDP certification violations assessed per P value** (below), and an object-level diff of the revision chain (which objects each update added, rewrote or freed). Incremental updates are legal, so the diff says what to review — no ver…detect_pades_levelPAdES baseline level (B-B / B-T / B-LT / B-LTA) with content-validated LTV dataidentify_conformanceDeclared PDF/A / PDF/UA conformance from XMP metadatavalidate_conformancePDF/A (ISO 19005) and PDF/UA (ISO 14289) validation: veraPDF when installed, built-in rule subset otherwisevalidate_clausesConstraints mapped from ISO 32000-1/-2 clauses — the specification body itself, which the PDF/A and PDF/UA profiles do not coverevaluate_policyDeterministic 4-value trust verdict (trust_and_use / use_with_caution / human_review_required / reject) from a fixed rule table over the verification facts, with domain profiles (contract, financial, legal, medical, government). The judge is code; the narrative is the LLM
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"
]
}
}
}
PDF Verify (PDF Agent Stack)
{
"mcpServers": {
"pdf-verify-pdf-agent-stack": {
"command": "npx",
"args": [
"-y",
"@shuji-bonji/pdf-verify-mcp@latest"
],
"env": {
"PDF_VERIFY_TRUST_ANCHORS": "YOUR_PDF_VERIFY_TRUST_ANCHORS_HERE",
"PDF_VERIFY_VERAPDF": "YOUR_PDF_VERIFY_VERAPDF_HERE"
}
}
}
}
Frequently asked questions
Aga MCP Server is categorized under Cryptography and uses a local stdio subprocess. PDF Verify (PDF Agent Stack) belongs to Cryptography and uses a local stdio subprocess. Pick Aga MCP Server for cryptography work and PDF Verify (PDF Agent Stack) 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. PDF Verify (PDF Agent Stack) 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 pdf-verify-pdf-agent-stack 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. PDF Verify (PDF Agent Stack) has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.