Remote MCP · Endpoint

黑123 Hackathons MCP server

No. 黑123 Hackathons answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://hack123.henryht.sh/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.onehumanbeing/hack123
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
106 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only search of hackathons, team-up posts and projects on 黑123 (hack123.henryht.sh), zh/en.
Listing
From the official MCP registry (active).
Recent checks of 黑123 Hackathons
CheckedResultHandshake
34 minutes agoHandshake completed106 ms
9 days agoHandshake completed82 ms
10 days agoHandshake completed55 ms
11 days agoHandshake completed119 ms
12 days agoHandshake completed125 ms
14 days agoHandshake completed72 ms
14 days agoHandshake completed85 ms
15 days agoHandshake completed106 ms
17 days agoHandshake completed92 ms
19 days agoHandshake completed101 ms
21 days agoHandshake completed103 ms
24 days agoHandshake completed85 ms
26 days agoHandshake completed66 ms
28 days agoHandshake completed144 ms

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

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