verify_integrity

MCP tool from Pdf Verify MCP by shuji-bonji

Tamper 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 verdict

How to use it

Project documentation lists verify_integrity for the Pdf Verify MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.

FULL PDF VERIFY MCP LISTING

Other tools in Pdf Verify MCP (6)

detect_pades_level

PAdES baseline level (B-B / B-T / B-LT / B-LTA) with content-validated LTV data

evaluate_policy

Deterministic 4-value trust verdict (trustanduse / usewithcaution / humanreviewrequired / 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

identify_conformance

Declared PDF/A / PDF/UA conformance from XMP metadata

validate_clauses

Constraints mapped from ISO 32000-1/-2 clauses — the specification body itself, which the PDF/A and PDF/UA profiles do not cover

validate_conformance

PDF/A (ISO 19005) and PDF/UA (ISO 14289) validation: veraPDF when installed, built-in rule subset otherwise

verify_signatures

Cryptographic verification, trust chain evaluation against trust anchors, revocation checking (embedded OCSP/CRL or online), RFC 3161 timestamp verification