Remote MCP · Endpoint

AstroWay Forecasting MCP server

No. AstroWay Forecasting answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.astroway.info/mcp/forecast

The last check completed an MCP handshake.

Registry name
info.astroway/forecast
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
391 ms
Tools exposed
45 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
Transits, progressions, directions, returns, cosmobiology and evolutionary technique.
Listing
From the official MCP registry (active).
Recent checks of AstroWay Forecasting
CheckedResultHandshake
1 hour agoHandshake completed391 ms
2 days agoHandshake completed378 ms
5 days agoHandshake completed363 ms
7 days agoHandshake completed367 ms
9 days agoHandshake completed342 ms
11 days agoHandshake completed390 ms
13 days agoHandshake completed138 ms
16 days agoHandshake completed230 ms
18 days agoFailed - the check failed for an unclassified reason—
19 days agoHandshake completed230 ms
21 days agoHandshake completed367 ms
22 days agoFailed - the check failed for an unclassified reason—
23 days agoHandshake completed172 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 11 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 AstroWay Forecasting and makes no claim about it beyond what these checks measured.