Remote MCP · Endpoint

Nonobench MCP server

No. Nonobench answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.nonobench.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.mauricekleine/nonobench
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
383 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
An open-source benchmark of how well LLMs solve nonogram puzzles, from 5x5 to 20x20.
Listing
From the official MCP registry (active).
Recent checks of Nonobench
CheckedResultHandshake
1 hour agoHandshake completed383 ms
8 days agoHandshake completed402 ms
9 days agoHandshake completed239 ms
11 days agoHandshake completed227 ms
12 days agoHandshake completed480 ms
12 days agoHandshake completed226 ms
14 days agoHandshake completed286 ms
14 days agoHandshake completed247 ms
16 days agoHandshake completed593 ms
19 days agoHandshake completed301 ms
21 days agoHandshake completed271 ms
24 days agoHandshake completed223 ms
26 days agoHandshake completed213 ms
28 days agoHandshake completed195 ms

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

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