Remote MCP · Endpoint

Sumbloom MCP server

No. Sumbloom answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://sumbloom.cybermax-tools.workers.dev/mcp?via=mcp-registry

The last check completed an MCP handshake.

Registry name
dev.workers.cybermax-tools.cybermax/sumbloom
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
120 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Number puzzle API + MCP: solver-checked puzzles as JSON/SVG, daily puzzle. $5/mo; 50 free/day.
Listing
From the official MCP registry (active).
Recent checks of Sumbloom
CheckedResultHandshake
2 hours agoHandshake completed120 ms
2 days agoHandshake completed140 ms
4 days agoHandshake completed106 ms
6 days agoHandshake completed157 ms
8 days agoHandshake completed121 ms
10 days agoHandshake completed527 ms
12 days agoHandshake completed56 ms
13 days agoHandshake completed181 ms
14 days agoHandshake completed345 ms
16 days agoHandshake completed95 ms
18 days agoHandshake completed95 ms
20 days agoHandshake completed90 ms
21 days agoHandshake completed98 ms
23 days agoHandshake completed57 ms
24 days agoHandshake completed93 ms

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