Server Everything vs PDF Verify (PDF Agent Stack)
A side-by-side look at the Server Everything 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 Server Everything for other tools and integrations 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 Server Everything when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
create_entities, create_relations, add_observations.
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 | Other Tools and Integrations | Cryptography |
| Quality signal | 73/100 · Great | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 91,405 | 0 |
| Directory activity | 9 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 9 | 7 |
| Full listing | View Server Everything | View PDF Verify (PDF Agent Stack) |
Tools & capabilities
Server Everything tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
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.
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
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
Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. PDF Verify (PDF Agent Stack) belongs to Cryptography and uses a local stdio subprocess. Pick Server Everything for other tools and integrations 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.
Server Everything is listed as free. Auth: no auth required. 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 modelcontextprotocol-server-everything 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, Server Everything has a quality signal of 73/100 (Great) with 9 views, 0 installs and 91,405 GitHub stars. PDF Verify (PDF Agent Stack) has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.