Remote MCP · Endpoint

JSONlify MCP server

No. JSONlify answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.jsonlify.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.irmasemma/jsonlify
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.21 s
Tools exposed
Not measured yet
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Validate and convert JSONL fine-tuning data across 11 AI providers. 13 tools.
Listing
From the official MCP registry (active).
Recent checks of JSONlify
CheckedResultHandshake
1 hour agoHandshake completed1.21 s
2 days agoHandshake completed79 ms
4 days agoHandshake completed64 ms
5 days agoHandshake completed67 ms
7 days agoHandshake completed123 ms
8 days agoHandshake completed108 ms
9 days agoHandshake completed122 ms
12 days agoHandshake completed78 ms
13 days agoHandshake completed72 ms
15 days agoHandshake completed155 ms
17 days agoHandshake completed1.04 s
18 days agoHandshake completed78 ms
19 days agoHandshake completed102 ms
20 days agoHandshake completed59 ms
20 days agoHandshake completed128 ms
21 days agoHandshake completed94 ms
23 days agoHandshake completed78 ms

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

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