Remote MCP · Endpoint
JsonMend MCP server
No. JsonMend answered an MCP handshake 1 day ago.
UpLast checked 1 day ago
Server URL
https://jsonmend.mike-tusa.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.workers.mike-tusa.jsonmend/jsonmend
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 64 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 1 check from 1 check
- Described by its publisher as
- Repair broken JSON from LLM output and validate it against a JSON Schema.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 day ago | Handshake completed | 64 ms |
The last 1 check. Full history is kept for 30 days; the all-time counter stands at 1 responding of 1.
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 JsonMend and makes no claim about it beyond what these checks measured.