Document Integrity Validator MCP
Related Servers
Alternatives to Document Integrity Validator MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables coding agents to call a check that flags invented specifics, copied passages, and rule breaks in drafts against an approved, versioned standard. Returns actionable tool results so agents can identify and rewrite offending spans.-
- AlicenseAqualityBmaintenanceInspects documents for tampering, ineffective redactions, and text aimed at language models before they enter an agent's context, and compares documents to confirm whether they are unchanged.472 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to obtain an independent review of their drafts, returning a pass/fail verdict with specific issues and suggested fixes, plus a signed receipt. Payments are made per check over x402, with no account or API key needed.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to check a drafted answer against supplied sources or a document before stating or acting on it, returning claim-level support status, contradictions, omissions, and a verdict.MIT

Qinisoofficial
AlicenseAqualityBmaintenanceThe deterministic fact-verification layer for AI agents. Validates the structured facts an agent emits — IBANs, payment cards, VAT and national tax IDs, crypto and bank addresses, domains, emails, phone numbers, securities and academic identifiers, plus dates, currencies and holidays — against checksums and curated authoritative data, not guesses.561Apache 2.0- AlicenseNot gradedqualityBmaintenanceDocument verification for AI agents: forensic authenticity signals for PDFs and images, field extraction, Australian identity checks, adverse-media and sanctions screening, AU/NZ government tender search, AI-text detection, and citation verification. Hosted with a free anonymous tier; the repo ships a Dockerfile that bridges to the live endpoint.1MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: check_document validates a single document's internal consistency, while check_document_package validates cross-document consistency for 2-20 related documents. Their descriptions explicitly state when to use each, leaving no ambiguity about which to select.
Both tool names follow the same verb_noun pattern: 'check_document' and 'check_document_package'. The second name is a logical extension of the first, making the relationship and function predictable.
With only two tools, the server is borderline minimal, but this is appropriate for a narrow domain focused on document validation. The two tools cover the two core scenarios (single document and package), with no unnecessary bloat.
The server covers the primary validation workflows: single-document internal consistency and multi-document cross-consistency. Minor gaps exist, such as not exposing a way to list supported standards or validate against a user-specified standard, but these are not critical for the core use case.