Remote MCP · Endpoint
Hypertune MCP by usefulapi MCP server
No. Hypertune MCP by usefulapi answered an MCP handshake 1 day ago.
UpLast checked 1 day ago
Server URL
https://hypertune.usefulapi.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.usefulapi/hypertune
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 135 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 41.2% from 17 checks
- Described by its publisher as
- Evaluate and inspect your Hypertune feature flags from your AI assistant.
- Repository
- https://github.com/m190/usefulapi-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 day ago | Handshake completed | 135 ms |
| 3 days ago | Handshake completed | 156 ms |
| 5 days ago | Handshake completed | 156 ms |
| 7 days ago | Handshake completed | 195 ms |
| 9 days ago | Handshake completed | 218 ms |
| 10 days ago | Failed - the check failed for an unclassified reason | — |
| 11 days ago | Failed - the check failed for an unclassified reason | — |
| 14 days ago | Failed - the check failed for an unclassified reason | — |
| 15 days ago | Failed - the check failed for an unclassified reason | — |
| 17 days ago | Handshake completed | 233 ms |
| 18 days ago | Failed - the check failed for an unclassified reason | — |
| 19 days ago | Failed - the check failed for an unclassified reason | — |
| 21 days ago | Failed - the check failed for an unclassified reason | — |
| 22 days ago | Failed - the check failed for an unclassified reason | — |
| 22 days ago | Failed - the check failed for an unclassified reason | — |
| 23 days ago | Handshake completed | 176 ms |
| 24 days ago | Failed - the check failed for an unclassified reason | — |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 7 responding of 17.
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 Hypertune MCP by usefulapi and makes no claim about it beyond what these checks measured.