Document Integrity Validator MCP Server

by ojaskord Your server? Claim it

answering

Document Integrity Validator is answering right now. Last checked 8 min ago. 65 installs a week from npm. It exposes 2 tools. Last commit 7 Sep 2026.

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

Installs per day peak 58 · avg 13 · +63% w/w

a month agotoday

Uptime history 91 days of history · worst day 99%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

356 ms

Response time

average over 24h

Installs / week

npm and PyPI

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 19 August 2026. No other catalogue keeps this.

7 Sep a tool changed version2 times that day

24 Aug a tool changed version

19 Aug a tool changed version

and 1 more, back to 19 August 2026

Nothing serious here today

Today is the operative word: we check Document Integrity Validator every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://document-integrity-validator-mcp-production.up.railway.app/mcp

~/.codex/config.toml

[mcp_servers.document-integrity-validator-mcp]
url = "https://document-integrity-validator-mcp-production.up.railway.app/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

document

check_document

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_package

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.

Endpoints

URL	Transport	State	Latency	Checked
https://document-integrity-validator-mcp-production.up.railway.app/mcp	streamable-http	answering	342 ms	8 min ago

Alternatives to Document Integrity Validator

same job, measured the same way

Review Assist MCP

by uditk2

Turns an AI coding agent session into a reviewable Intent Document, validated against the diff.

245 installs/wk local only

HiddenContent

by hiddencontent

Check a document for hidden text before your agent reads it. PDF, Office, RTF, HTML.

186 installs/wk answering

Backrow

by backrow

Turn any recording or document into notes, flashcards and quizzes your agent can read and act on

answering

Visimark

by michal-niedzwiedzki

MCP server for VisiMark, a document integrity layer for Markdown: checks numbers against formulas.

119 installs/wk local only

Ivisa

by ivisa-www

Check visa requirements and travel documents for international travel destinations.

1 tools answering

Intenttext MCP

by intenttext

Parse, validate, query, and render IntentText (.it) documents for AI agents

48 installs/wk local only

Doc Bridge

by agentskit-io

Resolve documentation ownership, edit roots, checks, and human handoffs before an agent edits code.

8 315 installs/wk local only

Doc Extract MCP

by koraynar

Document tooling for AI agents: PDF/text reading, chunking, schema-validated JSON output.

local only

Document Integrity Validator — questions

Answers built from our own checks of this server.

What can Document Integrity Validator do?

It exposes 2 tools, read directly from the server on our last check. Among them: check_document, check_document_package. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Document Integrity Validator working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 356 ms. The bar chart above shows every period we have measured.

How do I connect Document Integrity Validator?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Document Integrity Validator need an API key?

No. Document Integrity Validator completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Document Integrity Validator?

It answers our handshake in 356 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Document Integrity Validator?

The npm package document-integrity-validator-mcp was installed 65 times in the last week. Week over week that is +63%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Document Integrity Validator open source?

The code is open source: it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at document-integrity-validator-mcp-production.up.railway.app, which runs on its operator's own terms.