MCP.Market

Document Integrity Validator MCP server

online · 100% uptime
by OjasKord·io.github.OjasKord/document-integrity-validator-mcp·v1.0.20
No reviews yet

AI reasoning checks any document against known international standards before your agent acts on it.

A88/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars68 downloads/wk

Reviews

Write one

Nobody has reviewed Document Integrity Validator yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Document Integrity Validator tools (2)

write = sends, deletes, buys or posts
  • check_documentFree

    Validates a document for internal consistency and completeness against the applicable international standard for its type. Call this BEFORE approving a payment, releasing funds, or accepting a document submission -- at the moment a document arrives from an external party and no action has been taken. Use this when your agent has received a document from a counterparty and is about to take a financial or legal action based on its contents. Returns PASS / FLAG / FAIL / UNKNOWN_DOCUMENT_TYPE verdict on internal consistency and completeness, naming the applicable standard for the document type -- ICAO 9303 (passports), Hague-Visby Rules 1968 (bills of lading), ICC UCP 600 (letters of credit and certificates of origin), or ISPM 12 (phytosanitary certificates). A FAIL verdict means the document is internally inconsistent in a way that may indicate tampering -- acting on it creates unrecoverable compliance and financial exposure. Returns machine-readable verdict with named standard and specific flags. When you have 2-20 related documents (e.g. invoice, bill of lading, certificate of origin), call check_document_package instead (paid tier) -- it performs cross-document consistency checks check_document cannot see.

  • check_document_packageFree

    Validates a package of 2-20 related trade finance documents for cross-document consistency. Call this BEFORE approving any multi-document trade finance transaction or cross-border shipment -- at the moment a set of 2-20 related documents arrives from an external party and funds have not been released. Use this when your agent has received a full trade finance package — such as invoice, bill of lading, and certificate of origin together — and must verify all documents are consistent with each other before releasing funds. Returns PASS/FLAG/FAIL verdict per document with mismatch details. Cross-checks all documents for consistency across numeric values, party names, reference numbers, dates, and commodity descriptions. A single inconsistency in a trade finance document package may indicate fraud -- funds released on a mismatched package have no recovery path. Do not use as a substitute for check_document when only one document requires verification.

Public scan report

scanner v0.1.10 · 2026-11-08 · same rubric, same numbers if you re-run it

no findings
  • Code scan12 source files scanned25/25
  • Live reliabilityremote reachable in 255ms20/20
  • Tool poisoning2 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 62 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Document Integrity Validator compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 80% of 4,456 AI and agents servers
Tools
2
the typical AI and agents server has 7
Tools that change things
0%
typical: 3%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote AI and agents server answers 100%
Response time
208 ms
faster than 59% of 2,337 AI and agents servers
Downloads a week
68
more than 45% of 1,712 AI and agents servers with a package

What its tools let an agent do: 2 read

Install Document Integrity Validator in Claude Code, Cursor or VS Code

claude mcp add --transport http document-integrity-validator-mcp https://document-integrity-validator-mcp-production.up.railway.app/mcp
Add to Cursor

What the publisher says

From the Document Integrity Validator repository's README, as published. We do not edit it. Read it on GitHub

Document Integrity Validator MCP

Before your agent accepts, processes, or acts on any document received from an external party -- verify it is internally consistent and matches the known standard for its type. One call. Any document. Machine-readable verdict.

What it does

Checks any document for internal consistency, completeness, and anomalies against the known international standard for that document type. Accepts base64 image or extracted text. Returns a structured verdict with a machine-readable agent_action field.

Supported standards include: ICAO Document 9303 (passports), Hague-Visby Rules 1968 (bills of lading), UCP 600 (trade finance documents), ISPM 12/IPPC/FAO (phytosanitary certificates), Vienna Convention on Road Traffic 1968 (driving licences), and more.

Returns UNKNOWNDOCUMENTTYPE rather than guessing on unfamiliar documents -- refusal is correct behaviour, not a failure.

AI-powered reasoning -- NOT a database lookup.

Tools

check_document (Free tier: 10 calls/month)

Checks a single document against its international standard.

Input:

  • document_text (string, optional) -- extracted text from the document
  • document_image (string, optional) -- base64 encoded image (raw base64 or data URL)
  • documenttypehint (string, optional) -- agent belief about document type
  • issuing_jurisdiction (string, optional) -- country or issuing body

At least one of documenttext or documentimage is required.

Response:

{
  "agent_action": "PROCEED",
  "verdict": "PASS",
  "confidence": "HIGH",
  "document_type_identified": "Bill of Lading",
  "assessed_against": "Hague-Visby Rules 1968",
  "known_issuing_standard": "IMO",
  "flags": [],
  "reason": "Document is internally consistent and compliant with Hague-Visby Rules 1968.",
  "analysis_type": "AI-powered reasoning -- NOT a database lookup",
  "checked_at": "2026-05-06T10:00:00.000Z",
  "_disclaimer": "..."
}

agentaction values:**

  • PROCEED -- document passed
  • VERIFY_MANUALLY -- flags found, agent should flag for human review
  • HOLD -- document failed, do not proceed
  • REFERTOHUMAN -- document type unknown, refer for manual assessment

checkdocumentpackage (Paid tier only)

Checks 2-20 related documents individually then cross-checks all for consistency conflicts.

Input:

  • documents (array, min 2, max 20) -- each item has: label (required), documenttext, documentimage, documenttypehint, issuing_jurisdiction

Cross-checks performed: weights/quantities/amounts, party names, reference numbers, dates, commodity descriptions, port references.

Pricing

Overage: $0.05 per call above monthly cap.

Subscribe at kordagencies.com.

Harness Integration

Claude Code / Claude Desktop (.mcp.json)

{
  "mcpServers": {
    "document-integrity-validator": {
      "type": "http",
      "url": "https://document-integrity-validator-mcp-production.up.railway.app/mcp"
    }
  }
}

LangChain / LangGraph (Python)

from langchain_mcp_adapters.client import MultiServerMCPClient
client = MultiServerMCPClient({
    "document-integrity-validator": {
        "url": "https://document-integrity-validator-mcp-production.up.railway.app/mcp",
        "transport": "http"
    }
})
tools = await client.get_tools()

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Document Integrity Validator: common questions

Is Document Integrity Validator MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Document Integrity Validator safety report
How do I install Document Integrity Validator?
It runs remotely at document-integrity-validator-mcp-production.up.railway.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Document Integrity Validator need an API key?
Yes. The registry entry asks for ANTHROPIC_API_KEY.
Is Document Integrity Validator maintained?
The last commit was 69 days ago (2026-09-07). The latest release is v1.0.20.
Is Document Integrity Validator up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Document Integrity Validator?
Servers from other publishers that do the same job: agent-custody MCP server, Doc Bridge MCP server and Decionis MCP server.
How does Document Integrity Validator compare with other AI and agents MCP servers?
safety score 88/100 (higher than 80% of 4,456 AI and agents servers); tools 2 (the typical AI and agents server has 7); tools that change things 0% (typical: 3%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Document Integrity Validator

Same job from other publishers: the closest match first, then the best rated.

  • agent-custody
    MCP gateway that checks each agent tool call against a signed grant and policy, and signs a receipt
    A
  • Doc Bridge
    Resolve documentation ownership, edit roots, checks, and human handoffs before an agent edits code.
    A
  • Decionis
    Authorize consequential AI agent actions before execution
    A
  • haiku.rag
    Local-first agentic RAG with citations - hybrid search, reranking, multimodal document retrieval
    A
  • IWE (iwe.md)
    Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
    A

More from OjasKord →