Remote MCP · Endpoint
Hesperan MCP server
No. Hesperan answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.hesperan.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.hesperan/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 575 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 94.7% from 19 checks
- Described by its publisher as
- Calibrated decisions for agents: choice, yes/no and score questions answered with probabilities.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 575 ms |
| 1 day ago | Handshake completed | 294 ms |
| 2 days ago | Handshake completed | 292 ms |
| 3 days ago | Handshake completed | 310 ms |
| 4 days ago | Handshake completed | 299 ms |
| 5 days ago | Handshake completed | 327 ms |
| 6 days ago | Handshake completed | 290 ms |
| 8 days ago | Handshake completed | 291 ms |
| 11 days ago | Failed - the connection was refused or dropped | — |
| 13 days ago | Handshake completed | 293 ms |
| 15 days ago | Handshake completed | 306 ms |
| 18 days ago | Handshake completed | 420 ms |
| 20 days ago | Handshake completed | 314 ms |
| 22 days ago | Handshake completed | 284 ms |
| 24 days ago | Handshake completed | 317 ms |
| 26 days ago | Handshake completed | 302 ms |
| 27 days ago | Handshake completed | 364 ms |
| 29 days ago | Handshake completed | 287 ms |
| 29 days ago | Handshake completed | 290 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 27 responding of 28.
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 Hesperan and makes no claim about it beyond what these checks measured.