Skip to main content
Glama
Document Integrity Validator MCP

Document Integrity Validator MCP

by OjasKord

Related Servers

Alternatives to Document Integrity Validator MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Inspects 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.
      4
      72 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      The 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.
      56
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Document 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.
      1
      MIT

    TDQS

    A4.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data