Remote MCP · Endpoint

Docs-to-JSON MCP server

No. Docs-to-JSON answered an MCP handshake 23 minutes ago.

UpLast checked 23 minutes ago

Server URL

https://document-to-json-mcp.mcpize.run/mcp

The last check completed an MCP handshake.

Registry name
io.github.Alex-Dev-Web-C-DE/document-to-json-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
305 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Convert documents to structured JSON (invoices, receipts, contracts) in 2 seconds
Listing
From the official MCP registry (active).
Recent checks of Docs-to-JSON
CheckedResultHandshake
23 minutes agoHandshake completed305 ms
9 days agoHandshake completed263 ms
10 days agoHandshake completed480 ms
11 days agoHandshake completed465 ms
12 days agoHandshake completed201 ms
14 days agoHandshake completed461 ms
14 days agoHandshake completed245 ms
15 days agoHandshake completed440 ms
17 days agoHandshake completed332 ms
19 days agoHandshake completed553 ms
21 days agoHandshake completed344 ms
24 days agoHandshake completed443 ms
26 days agoHandshake completed718 ms
28 days agoHandshake completed624 ms

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

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 Docs-to-JSON and makes no claim about it beyond what these checks measured.