A side-by-side look at the ALEX Evidence Verify 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 ALEX Evidence Verify for cryptography work over a hosted endpoint; choose PDF Verify (PDF Agent Stack) for cryptography as a local process. You can also run both side by side in one mcpServers block.
PDF_VERIFY_TRUST_ANCHORS, PDF_VERIFY_VERAPDF.verify_signatures, verify_integrity, detect_pades_level.Rows where the two servers differ are marked.
| Spec | A ALEX Evidence Verify | |
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 43/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | PDF_VERIFY_TRUST_ANCHORSPDF_VERIFY_VERAPDF |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 7 |
| Full listing | View ALEX Evidence Verify | View PDF Verify (PDF Agent Stack) |
No tool names declared yet. Check the project README from the listing page.
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 LLMPaste 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.
{
"mcpServers": {
"alex-evidence-verify": {
"url": "https://alexproof.de/mcp"
}
}
}
{
"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"
}
}
}
}