Remote MCP · Endpoint

Hesperan MCP server

No. Hesperan answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes 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
314 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 16 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).
Recent checks of Hesperan
CheckedResultHandshake
53 minutes agoHandshake completed314 ms
2 days agoHandshake completed284 ms
4 days agoHandshake completed317 ms
5 days agoHandshake completed302 ms
7 days agoHandshake completed364 ms
8 days agoHandshake completed287 ms
9 days agoHandshake completed290 ms
12 days agoHandshake completed287 ms
13 days agoHandshake completed288 ms
15 days agoHandshake completed289 ms
17 days agoHandshake completed291 ms
18 days agoHandshake completed287 ms
19 days agoHandshake completed340 ms
20 days agoHandshake completed306 ms
21 days agoHandshake completed290 ms
21 days agoHandshake completed288 ms

The last 16 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 Hesperan and makes no claim about it beyond what these checks measured.