Remote MCP · Endpoint

com.hyperping/hyperping MCP server

No. com.hyperping/hyperping answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.hyperping.io/v1/mcp

The last check completed an MCP handshake.

Registry name
com.hyperping/hyperping
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
200 ms
Tools exposed
69 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Uptime, API and server monitoring with outages, reporting, on-call and status pages.
Listing
From the official MCP registry (active).
Recent checks of com.hyperping/hyperping
CheckedResultHandshake
1 hour agoHandshake completed200 ms
18 hours agoHandshake completed160 ms
2 days agoHandshake completed203 ms
3 days agoHandshake completed303 ms
4 days agoHandshake completed227 ms
5 days agoHandshake completed163 ms
6 days agoHandshake completed206 ms
7 days agoHandshake completed240 ms
10 days agoHandshake completed157 ms
13 days agoHandshake completed175 ms
15 days agoHandshake completed212 ms
17 days agoHandshake completed207 ms
19 days agoHandshake completed138 ms
21 days agoHandshake completed153 ms
23 days agoHandshake completed157 ms
25 days agoHandshake completed161 ms
27 days agoHandshake completed183 ms
28 days agoHandshake completed172 ms
29 days agoHandshake completed362 ms

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

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