Remote MCP · Endpoint

JotOak MCP server

No. JotOak answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://jotoak.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.iyuyoung/jotoak
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
177 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find published word searches, crosswords and mazes with matching Letter and A4 PDF files.
Listing
From the official MCP registry (active).
Recent checks of JotOak
CheckedResultHandshake
20 minutes agoHandshake completed177 ms
9 days agoHandshake completed316 ms
9 days agoHandshake completed168 ms
11 days agoHandshake completed144 ms
12 days agoHandshake completed172 ms
13 days agoHandshake completed188 ms
14 days agoHandshake completed235 ms
15 days agoHandshake completed178 ms
16 days agoHandshake completed198 ms
19 days agoHandshake completed384 ms
21 days agoHandshake completed204 ms
24 days agoHandshake completed458 ms
26 days agoHandshake completed370 ms
28 days agoHandshake completed193 ms

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

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