Remote MCP · Endpoint

JSON to TOON MCP server

No. JSON to TOON answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://json2toon.co/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.karta9821/json2toon
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
997 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Convert JSON to TOON (about 43% fewer LLM tokens) and TOON back to JSON. Free, no auth.
Website
https://json2toon.co/mcp
Listing
From the official MCP registry (active).
Recent checks of JSON to TOON
CheckedResultHandshake
1 hour agoHandshake completed997 ms
2 days agoHandshake completed73 ms
5 days agoHandshake completed55 ms
7 days agoHandshake completed1.17 s
9 days agoHandshake completed1.07 s
11 days agoHandshake completed2.02 s
13 days agoHandshake completed953 ms
15 days agoHandshake completed2.24 s
17 days agoHandshake completed744 ms
19 days agoHandshake completed204 ms
20 days agoHandshake completed107 ms
21 days agoHandshake completed110 ms
23 days agoHandshake completed4.40 s

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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