Document Integrity Validator
v1.0.20AI reasoning checks any document against known international standards before your agent acts on it.
Endpoint health
online- Last checked
- 11/20/2026, 4:17:24 AM
- Latency
- 106 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.OjasKord%2Fdocument-integrity-validator-mcp
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.OjasKord/document-integrity-validator-mcp": {
"url": "https://document-integrity-validator-mcp-production.up.railway.app/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
2 shown · authentication unknown
Check Document Integrity
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.
Schema valid · SHA-256 fd152bed0bae…
View input schema
{ "type": "object", "properties": { "document_text": { "type": "string", "maxLength": 50000, "description": "Extracted text content from the document. Provide this or document_image or both." }, "document_image": { "type": "string", "maxLength": 10000000, "description": "Base64 encoded document image. Accepts raw base64 or a data URL (data:image/jpeg;base64,...). Supported types: JPEG, PNG, GIF, WEBP." }, "document_type_hint": { "type": "string", "maxLength": 200, "description": "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": { "type": "string", "maxLength": 200, "description": "Country or issuing body, e.g. \"Singapore\", \"ICAO\", \"United Kingdom\". Narrows jurisdiction-specific standard selection." } }, "additionalProperties": false, "$schema": "http://json-schema.org/draft-07/schema#" }
Connections
streamable-http
https://document-integrity-validator-mcp-production.up.railway.app/mcp