Remote MCP · Endpoint

io.github.benheb/anecast MCP server

No. io.github.benheb/anecast answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.anecast.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.benheb/anecast
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
150 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Forecasts for any US point, with context: alerts, what changed overnight, why, and history.
Listing
From the official MCP registry (active).
Recent checks of io.github.benheb/anecast
CheckedResultHandshake
1 hour agoHandshake completed150 ms
1 day agoHandshake completed320 ms
3 days agoHandshake completed276 ms
5 days agoHandshake completed281 ms
8 days agoHandshake completed270 ms
10 days agoHandshake completed276 ms
12 days agoHandshake completed359 ms
14 days agoHandshake completed327 ms
16 days agoHandshake completed287 ms
18 days agoHandshake completed285 ms
20 days agoHandshake completed303 ms
22 days agoHandshake completed400 ms
23 days agoHandshake completed288 ms

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

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 io.github.benheb/anecast and makes no claim about it beyond what these checks measured.