# Document Integrity Validator (remote · document-integrity-validator-mcp-production.up.railway.app)

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

- Trust score: 70/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `document-integrity-validator-mcp-production.up.railway.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/ojaskord-document-integrity-validator-mcp/document-integrity-validator-mcp-production.md), [page](https://verifymcp.io/servers/ojaskord-document-integrity-validator-mcp/document-integrity-validator-mcp-production)
- npm · `document-integrity-validator-mcp`: 35/100, [markdown](https://verifymcp.io/servers/ojaskord-document-integrity-validator-mcp/document-integrity-validator-mcp.md), [page](https://verifymcp.io/servers/ojaskord-document-integrity-validator-mcp/document-integrity-validator-mcp)

## Channel facts

- Endpoint: `https://document-integrity-validator-mcp-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.20`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

```json
{
  "$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

```bash
openclaw mcp add ojaskord-document-integrity-validator-mcp --url https://document-integrity-validator-mcp-production.up.railway.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ojaskord-document-integrity-validator-mcp:
    url: "https://document-integrity-validator-mcp-production.up.railway.app/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 69, 0)

- [functional] Server version: 1.0.29 → 1.0.30

### 2026-07-31 (score 69, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (2)

### `check_document` (~393 tokens)

Check Document Integrity

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.

Input parameters:

- `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.

Output parameters:

- `_disclaimer` (string)
- `_upgrade_notice` (string)
- `agent_action` (string)
- `analysis_type` (string)
- `assessed_against` (string|null): Named standard, e.g. "ICAO Document 9303" -- null for UNKNOWN_DOCUMENT_TYPE
- `calls_remaining`
- `checked_at` (string)
- `confidence` (string)
- `data_source_status` (string)
- `document_type_identified` (string|null)
- `escalation_path` (string|null)
- `flags` (array)
- `hold_reason` (string)
- `known_issuing_standard` (string|null)
- `reason` (string)
- `retry_after` (number|null)
- `verdict` (string)
- `verdict_ttl` (number)

### `check_document_package` (~219 tokens)

Check Document Package Integrity

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.

Input parameters:

- `documents` (array, required): Array of 2 to 20 related documents to assess individually and cross-check against each other. Each document must have a unique label.

Output parameters:

- `_disclaimer` (string)
- `agent_action` (string)
- `analysis_type` (string)
- `calls_remaining`
- `checked_at` (string)
- `confidence` (string)
- `cross_document_conflicts` (array)
- `data_source_status` (string)
- `documents` (array)
- `package_agent_action`
- `package_verdict`
- `verdict` (string)
- `verdict_ttl` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ojaskord-document-integrity-validator-mcp/document-integrity-validator-mcp-production#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 65
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 63
- 2026-07-26: 63

## Links

- Remote endpoint: https://document-integrity-validator-mcp-production.up.railway.app/mcp
- Repository: https://github.com/OjasKord/document-integrity-validator-mcp
- Website: https://kordagencies.com/
- Changelog RSS feed: https://verifymcp.io/servers/ojaskord-document-integrity-validator-mcp/document-integrity-validator-mcp-production/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ojaskord-document-integrity-validator-mcp/document-integrity-validator-mcp-production/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ojaskord-document-integrity-validator-mcp/document-integrity-validator-mcp-production