AI reasoning checks any document against known international standards before your agent acts on it.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
Extracted text content from the document. Provide this or document_image or both.
Base64 encoded document image. Accepts raw base64 or a data URL (data:image/jpeg;base64,...). Supported types: JPEG, PNG, GIF, WEBP.
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.
Country or issuing body, e.g. "Singapore", "ICAO", "United Kingdom". Narrows jurisdiction-specific standard selection.
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.
| Argument | Type | Description |
|---|---|---|
| document_text | string | Extracted text content from the document. Provide this or document_image or both. |
| 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_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. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"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
}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.
| Argument | Type | Description |
|---|---|---|
| documents* | array | Array of 2 to 20 related documents to assess individually and cross-check against each other. Each document must have a unique label. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"documents"
],
"properties": {
"documents": {
"type": "array",
"items": {
"type": "object",
"required": [
"label"
],
"properties": {
"label": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Agent-assigned identifier for this document in the package, e.g. \"packing_list\", \"certificate_of_origin\", \"commercial_invoice\". Used in cross-document conflict reporting."
},
"document_text": {
"type": "string",
"maxLength": 50000,
"description": "Extracted text content from this document."
},
"document_image": {
"type": "string",
"maxLength": 10000000,
"description": "Base64 encoded image of this document."
},
"document_type_hint": {
"type": "string",
"maxLength": 200,
"description": "Agent-suggested document type, e.g. \"commercial_invoice\"."
},
"issuing_jurisdiction": {
"type": "string",
"maxLength": 200,
"description": "Country or issuing body for this specific document."
}
},
"additionalProperties": false
},
"maxItems": 20,
"minItems": 2,
"description": "Array of 2 to 20 related documents to assess individually and cross-check against each other. Each document must have a unique label."
}
},
"additionalProperties": false
}