Log inSubmit server
PDF Verify (PDF Agent Stack) logo

PDF Verify (PDF Agent Stack)

Checks PDF signatures, revisions, PAdES structure, PDF/A and PDF/UA rules, ISO clauses, and policy-based trust.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install PDF Verify (PDF Agent Stack)

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "pdf-verify-pdf-agent-stack": {
      "command": "npx",
      "args": [
        "-y",
        "@shuji-bonji/pdf-verify-mcp@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

PDF Verify (PDF Agent Stack) is an MCP server for examining local PDF authenticity, integrity, and conformance. Its tools verify CMS signatures, certificate trust, revocation, timestamps, incremental revisions, DocMDP permissions, PAdES structure, PDF/A and PDF/UA rules, and selected ISO 32000 clauses. It can delegate conformance checks to veraPDF or use built-in rule subsets, and it offers deterministic policy verdicts for document intake workflows. Reach for it when cryptographic verification or standards-based PDF checks matter more than structural inspection alone.

Use cases

  • Verify signed contracts against an organizational CA
  • Inspect changes made after a PDF signature
  • Validate PDF/A files before archival submission
  • Audit PAdES long-term validation evidence
  • Evaluate incoming documents with a fixed trust policy

Key features

  • Cryptographic signature and timestamp verification
  • Certificate trust and OCSP/CRL revocation checks
  • Incremental revision and DocMDP analysis
  • PAdES, PDF/A, and PDF/UA assessment
  • ISO 32000 clause constraint checks
  • Deterministic profile-based trust verdicts

Tools7

What PDF Verify (PDF Agent Stack) lets your agent do. Expand a tool for its parameters.

Verified live~8.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 37d

What it can do

From the 7 tools this server returned when we ran it; 7 declare their own safety hints.

Handles credentials · 3Makes network requests · 2Read-only tools · 7
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age113 days
Maintainers1

Observed 2026-11-03 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @shuji-bonji/pdf-verify-mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads2.2kPackage downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Tools exposed7Callable tools this server registers over MCP.

How PDF Verify (PDF Agent Stack) works

What PDF Verify (PDF Agent Stack) does

PDF Verify (PDF Agent Stack) evaluates local PDF files for authenticity, post-signing changes, declared and checked conformance, and policy-based trust. Its coverage includes digital signatures, certificate paths, OCSP and CRL status, RFC 3161 timestamps, incremental revisions, DocMDP certification permissions, PAdES baseline structure, PDF/A and PDF/UA, and selected clauses from ISO 32000-1 and ISO 32000-2.

The server complements structural PDF analysis: it determines whether signatures and conformance checks support a particular conclusion, while structural or page-location analysis belongs to related PDF tools.

How it works

All tools accept an absolute local file_path and can return Markdown or JSON. Reports begin with a scope object describing how much of the file was read, whether the cross-reference chain was complete, whether reconstruction was required, and whether an encrypted file could be opened. This scope must be considered before interpreting an empty list or a clean result.

verify_signatures recomputes signed byte-range digests, checks CMS or PKCS#7 signatures, evaluates timestamp signatures, builds certificate paths, and checks revocation. Trust identity requires supplied trust anchors. Revocation can use embedded evidence or online OCSP and CRL queries. Validation time comes from a verified signature or document timestamp, falling back to the current time.

verify_integrity describes revisions and object-level changes after signing. It compares later changes with DocMDP permissions, but an incremental update is not automatically evidence of tampering. An indeterminate assessment means the available file data was insufficient to decide; it is not a pass.

Setup and configuration

Trust anchors can be passed to individual calls or supplied through PDF_VERIFY_TRUST_ANCHORS, which points to a certificate directory. check_revocation supports none, embedded, and online; online mode may query OCSP and CRL endpoints. revocation_freshness controls how old validation evidence may be, and trusted_ocsp_responders supplies locally trusted responder certificates.

For conformance validation, PDF_VERIFY_VERAPDF can identify a veraPDF executable. The auto engine uses veraPDF when available and otherwise runs the native subset. Selecting verapdf fails if the executable is unavailable rather than silently switching engines. Passwords can be provided for encrypted PDFs.

Tools and capabilities

  • verify_signatures: Verify signature bytes, certificate trust, timestamps, and revocation.
  • verify_integrity: Inspect revisions, post-signing changes, DocMDP permissions, and object diffs.
  • detect_pades_level: Identify structural B-B, B-T, B-LT, or B-LTA evidence.
  • identify_conformance: Read declared PDF/A and PDF/UA metadata from XMP.
  • validate_conformance: Check PDF/A and PDF/UA with veraPDF or native rules.
  • validate_clauses: Evaluate bundled font, metadata, and annotation constraints mapped to ISO 32000 clauses.
  • evaluate_policy: Produce a fixed-rule verdict using general, contract, financial, legal, medical, or government profiles.

PAdES results describe matching structure rather than formal conformance. Native PDF/A and PDF/UA results cover a rule subset; PDF/UA accessibility meaning, such as whether alternative text is meaningful, still needs human review. evaluate_policy also reports selected active-content and pending-redaction observations.

Limitations and notes

Lists are bounded and report truncation in JSON. Signature, PAdES, and revision lists are capped at 32 entries; validation results and clause results are capped at 200. evaluate_policy evaluates every signature but may cap the signatures included in its facts summary. Markdown output can be cut at 50,000 characters.

A clean result only covers the portion of the file that the report’s scope reached. Rebuilt cross-reference tables, incomplete revision chains, skipped rules, missing external facts, and native-engine limits can all narrow the conclusion. identify_conformance reads declarations; it does not establish actual PDF/A or PDF/UA compliance.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about PDF Verify (PDF Agent Stack)

PDF Verify (PDF Agent Stack) is an MCP server that connects agent workflows to local PDF files and provides tools for signature verification, integrity analysis, PAdES detection, PDF/A and PDF/UA validation, ISO clause checks, and deterministic policy evaluation. It can use trust anchors, embedded or online revocation data, and veraPDF.

Installation details are not included here. The server is distributed as the npm package @shuji-bonji/pdf-verify-mcp, and its license is MIT.

Call verify_signatures with an absolute local file_path. Add trust_anchors to evaluate signer identity, choose embedded or online revocation with check_revocation, and select markdown or json output with response_format.

Yes, it can run a built-in PDF/A rule subset when veraPDF is unavailable or when engine is set to native. The native result is not certification: a null compliant value means no violation was found in the checked subset, not that the PDF fully conforms.

Yes, verify_integrity examines incremental revisions, bytes added after signed ranges, DocMDP permissions, and object-level changes. Its findings identify changes to review; they do not automatically prove tampering, and incomplete revision chains can make the assessment indeterminate.

Related MCP servers

All in Cryptography All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPDF Verify (PDF Agent Stack) AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pdf-verify-pdf-agent-stack?style=directory)](https://allmcps.com/mcp/pdf-verify-pdf-agent-stack)
HTML Embed
<a href="https://allmcps.com/mcp/pdf-verify-pdf-agent-stack"><img src="https://allmcps.com/api/badge/pdf-verify-pdf-agent-stack?style=directory" alt="PDF Verify (PDF Agent Stack) on AllMCPs" /></a>