Document Integrity Validator
REMOTE · DOCUMENT-INTEGRITY-VALIDATOR-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED SEP 20
AI reasoning checks any document against known international standards before your agent acts on it.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 612 tokens (~306/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Document Integrity Validator MCP server?
Document Integrity Validator is a hosted endpoint at https://document-integrity-validator-mcp-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · document-integrity-validator-mcp-production.up.railway.app
claude mcp add --transport http ojaskord-document-integrity-validator-mcp 'https://document-integrity-validator-mcp-production.up.railway.app/mcp'
{
"mcpServers": {
"ojaskord-document-integrity-validator-mcp": {
"url": "https://document-integrity-validator-mcp-production.up.railway.app/mcp"
}
}
} {
"servers": {
"ojaskord-document-integrity-validator-mcp": {
"type": "http",
"url": "https://document-integrity-validator-mcp-production.up.railway.app/mcp"
}
}
} [mcp_servers.ojaskord-document-integrity-validator-mcp] url = "https://document-integrity-validator-mcp-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ojaskord-document-integrity-validator-mcp": {
"type": "remote",
"url": "https://document-integrity-validator-mcp-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add ojaskord-document-integrity-validator-mcp --url 'https://document-integrity-validator-mcp-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
ojaskord-document-integrity-validator-mcp:
url: "https://document-integrity-validator-mcp-production.up.railway.app/mcp" {
"McpServers": {
"ojaskord-document-integrity-validator-mcp": {
"Transport": "http",
"Url": "https://document-integrity-validator-mcp-production.up.railway.app/mcp"
}
}
} assistant mcp add ojaskord-document-integrity-validator-mcp -t streamable-http -u 'https://document-integrity-validator-mcp-production.up.railway.app/mcp'
{
"mcpServers": {
"ojaskord-document-integrity-validator-mcp": {
"type": "http",
"url": "https://document-integrity-validator-mcp-production.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 8 Sept 26 0
- Server version: 1.0.33 → 1.0.35 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- Server version: 1.0.31 → 1.0.33 functional
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Aug 26 0
- Server version: 1.0.30 → 1.0.31 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- Server version: 1.0.29 → 1.0.30 functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://document-integrity-validator-mcp-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of document-integrity-validator-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://document-integrity-validator-mcp-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://document-integrity-validator-mcp-production.up.railway.app/mcp | HTTPS enforced | 301 | https://document-integrity-validator-mcp-production.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_document Check Document Integrity ~393
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.
| Name | Type | Req | Description |
|---|---|---|---|
| document_image | string | – | Base64 encoded document image. Accepts raw base64 or a data URL (data:image/jpeg;base64,...). Supported types: JPEG, PNG, GIF, WEBP. |
| document_text | string | – | Extracted text content from the document. Provide this or document_image or both. |
| document_type_hint | string | – | What the calling agent believes the document type is, e.g. "bill_of_lading", "passport", "certificate_of_origin". Optional -- the validator identifies the type independently. |
| issuing_jurisdiction | string | – | Country or issuing body, e.g. "Singapore", "ICAO", "United Kingdom". Narrows jurisdiction-specific standard selection. |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | yes | – |
| _upgrade_notice | string | – | – |
| agent_action | string | yes | – |
| analysis_type | string | yes | – |
| assessed_against | string|null | yes | Named standard, e.g. "ICAO Document 9303" -- null for UNKNOWN_DOCUMENT_TYPE |
| calls_remaining | – | yes | – |
| checked_at | string | yes | – |
| confidence | string | yes | – |
| data_source_status | string | yes | – |
| document_type_identified | string|null | yes | – |
| escalation_path | string|null | – | – |
| flags | array | yes | – |
| hold_reason | string | – | – |
| known_issuing_standard | string|null | yes | – |
| reason | string | yes | – |
| retry_after | number|null | – | – |
| verdict | string | yes | – |
| verdict_ttl | number | yes | – |
No examples provided.
check_document_package Check Document Package Integrity ~219
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.
| Name | Type | Req | Description |
|---|---|---|---|
| documents | array | yes | Array of 2 to 20 related documents to assess individually and cross-check against each other. Each document must have a unique label. |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | yes | – |
| agent_action | string | yes | – |
| analysis_type | string | yes | – |
| calls_remaining | – | yes | – |
| checked_at | string | yes | – |
| confidence | string | yes | – |
| cross_document_conflicts | array | yes | – |
| data_source_status | string | yes | – |
| documents | array | yes | – |
| package_agent_action | – | yes | – |
| package_verdict | – | yes | – |
| verdict | string | yes | – |
| verdict_ttl | number | yes | – |
No examples provided.
What is the Document Integrity Validator MCP server?
Document Integrity Validator is an MCP server listed in the public MCP registry as io.github.OjasKord/document-integrity-validator-mcp. AI reasoning checks any document against known international standards before your agent acts on it. This page covers its hosted endpoint (https://document-integrity-validator-mcp-production.up.railway.app/mcp).
Is the Document Integrity Validator MCP server safe to use?
Document Integrity Validator scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Document Integrity Validator MCP server expose?
Document Integrity Validator exposes 2 tools: check_document, check_document_package. Their descriptions and schemas cost roughly 612 tokens of context every time the server is loaded.
Does the Document Integrity Validator MCP server require authentication?
No. We connected to Document Integrity Validator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Document Integrity Validator MCP server still maintained?
Document Integrity Validator is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.