Document Integrity Validator

https://server.smithery.ai/OjasKord/document-integrity-validator-mcp/mcp

● degraded

AI reasoning checks any document for internal consistency and completeness against the applicable international standard for its type, before your agent acts on it.

Transport

streamable-http

Auth

smithery_api_key

Cost

—

Protocol revision

—

MCP readiness

F · 19/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here D, 22.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	0/10	initialize did not answer cleanly (HTTP 404).
Live MCP endpoint	5/25	Endpoint answers, but not with MCP JSON-RPC (382 ms).
Protocol revision	0/10	No protocol revision reported by initialize.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	0/15	0/30 probes succeeded over 30 days (0%).
Tool declaration	5/10	Lists 2 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	0/5	not seen in a source for over 30 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (382 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness: Higher than 0% of peers; This listing 19 · peer median 81
Latency: Faster than 43% of peers; This listing 382 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Live MCP endpoint −20 — Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers, but not with MCP JSON-RPC (382 ms).
Uptime (30 days) −15 — Stay reachable in our daily probes.
Now: 0/30 probes succeeded over 30 days (0%).
Valid MCP handshake −10 — Complete the MCP handshake without errors.
Now: initialize did not answer cleanly (HTTP 404).

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-11 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/OjasKord/document-integrity-validator-mcp/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/OjasKord/document-integrity-validator-mcp/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://kordagencies.com

Listed at (smithery)

https://kordagencies.com