PDF Verify (PDF Agent Stack) vs Hindsight

A side-by-side look at the PDF Verify (PDF Agent Stack) and Hindsight MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

PDF Verify (PDF Agent Stack) logoPDF Verify (PDF Agent Stack)Cryptography · Local subprocess (stdio)Verify PDF signatures, detect tampering, and identify PDF/A and PAdES conformance levels.52GoodAuth: not declaredHindsight logoHindsightKnowledge & Memory · Local subprocess (stdio)Hindsight: Agent Memory That Works Like Human Memory - Built for AI Agents to manage Long Term Memory57GoodAuth: api key required

Verdict: choose PDF Verify (PDF Agent Stack) for cryptography work as a local process; choose Hindsight for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

PDF Verify (PDF Agent Stack) logoChoose 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.
Explore PDF Verify (PDF Agent Stack)

Hindsight logoChoose Hindsight when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: HINDSIGHT_API_LLM_API_KEY.
Explore Hindsight

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPDF Verify (PDF Agent Stack) logoPDF Verify (PDF Agent Stack)Hindsight logoHindsight
CategoryCryptographyKnowledge & Memory
Quality signal52/100 · Good57/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsPDF_VERIFY_TRUST_ANCHORSPDF_VERIFY_VERAPDFHINDSIGHT_API_LLM_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars051,891
Directory activity 0 views 0 installs 0 upvotes 13 views 0 installs 0 upvotes
Tools7Not listed

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 verification
  • verify_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 data
  • identify_conformanceDeclared PDF/A / PDF/UA conformance from XMP metadata
  • validate_conformancePDF/A (ISO 19005) and PDF/UA (ISO 14289) validation: veraPDF when installed, built-in rule subset otherwise
  • validate_clausesConstraints mapped from ISO 32000-1/-2 clauses — the specification body itself, which the PDF/A and PDF/UA profiles do not cover
  • evaluate_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

Hindsight 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 (Claude Desktop / Cursor)
{
  "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"
      }
    }
  }
}

Hindsight

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vectorize-io-hindsight": {
      "command": "npx",
      "args": [
        "-y",
        "@vectorize-io/hindsight-coding-agents"
      ],
      "env": {
        "HINDSIGHT_API_LLM_API_KEY": "YOUR_HINDSIGHT_API_LLM_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

PDF Verify (PDF Agent Stack) is categorized under Cryptography and uses a local stdio subprocess. Hindsight belongs to Knowledge & Memory and uses a local stdio subprocess. Pick PDF Verify (PDF Agent Stack) for cryptography work and Hindsight for knowledge & memory.

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. Hindsight is listed as free. Auth: api key required. 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 vectorize-io-hindsight 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. Hindsight has 57/100 (Good) with 13 views, 0 installs and 51,891 GitHub stars.