PDF Verify (PDF Agent Stack) vs PEAC Protocol
A side-by-side look at the PDF Verify (PDF Agent Stack) and PEAC Protocol MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PDF Verify (PDF Agent Stack) for cryptography work as a local process; choose PEAC Protocol 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 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.
Choose PEAC Protocol when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 52/100 · Good | 43/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 | PDF_VERIFY_TRUST_ANCHORSPDF_VERIFY_VERAPDF | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 14 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View PDF Verify (PDF Agent Stack) | View PEAC Protocol |
Tools & capabilities
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
PEAC Protocol tools
No tool names declared yet. Check the project README from the listing page.
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.
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"
}
}
}
}
PEAC Protocol
{
"mcpServers": {
"peac-protocol": {
"url": "https://api.example.com"
}
}
}
Frequently asked questions
PDF Verify (PDF Agent Stack) is categorized under Cryptography and uses a local stdio subprocess. PEAC Protocol belongs to Cryptography and uses a remote HTTP/SSE transport. Pick PDF Verify (PDF Agent Stack) for cryptography work and PEAC Protocol 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.
PDF Verify (PDF Agent Stack) has no declared pricing — check the project's own site. PEAC Protocol 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 pdf-verify-pdf-agent-stack and peac-protocol as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PDF Verify (PDF Agent Stack) has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. PEAC Protocol has 43/100 (Fair) with 2 views, 0 installs and 14 GitHub stars.