Remote MCP · Endpoint
ClusterHack MCP server
No. ClusterHack answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://clusterhack.dev/mcp/
The last check completed an MCP handshake.
- Registry name
- dev.clusterhack/clusterhack
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 333 ms
- Tools exposed
- 60 tools
- Uptime, last 30 days
- 94.7% from 19 checks
- Described by its publisher as
- Run hackathons end to end: events, teams, submissions, judging and winners.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 333 ms |
| 12 hours ago | Handshake completed | 363 ms |
| 1 day ago | Handshake completed | 335 ms |
| 2 days ago | Handshake completed | 337 ms |
| 4 days ago | Handshake completed | 336 ms |
| 4 days ago | Handshake completed | 329 ms |
| 5 days ago | Handshake completed | 329 ms |
| 6 days ago | Handshake completed | 336 ms |
| 8 days ago | Handshake completed | 337 ms |
| 11 days ago | Failed - the connection was refused or dropped | — |
| 13 days ago | Handshake completed | 339 ms |
| 16 days ago | Handshake completed | 339 ms |
| 18 days ago | Handshake completed | 695 ms |
| 20 days ago | Handshake completed | 478 ms |
| 22 days ago | Handshake completed | 340 ms |
| 24 days ago | Handshake completed | 342 ms |
| 26 days ago | Handshake completed | 336 ms |
| 27 days ago | Handshake completed | 357 ms |
| 29 days ago | Handshake completed | 344 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 31.
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 ClusterHack and makes no claim about it beyond what these checks measured.