Remote MCP · Endpoint

Dokyumi Document Extraction MCP server

No. Dokyumi Document Extraction answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://dokyumi.com/mcp

The last check completed an MCP handshake.

Registry name
com.dokyumi/document-extraction
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.04 s
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Save schemas, preflight processing charges, extract approved documents and export owned results.
Listing
From the official MCP registry (active).
Recent checks of Dokyumi Document Extraction
CheckedResultHandshake
18 minutes agoHandshake completed1.04 s
10 days agoHandshake completed1.07 s
10 days agoHandshake completed1.73 s
11 days agoHandshake completed1.21 s
12 days agoHandshake completed905 ms
14 days agoHandshake completed2.30 s
14 days agoHandshake completed1.77 s
15 days agoHandshake completed1.37 s
17 days agoHandshake completed1.03 s
19 days agoHandshake completed1.49 s
21 days agoHandshake completed1.31 s
24 days agoHandshake completed915 ms
26 days agoHandshake completed859 ms
28 days agoHandshake completed1.14 s

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 24.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Dokyumi Document Extraction and makes no claim about it beyond what these checks measured.