Remote MCP · Endpoint

AstroWay Core astrology MCP server

No. AstroWay Core astrology answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://mcp.astroway.info/mcp/core

The last check completed an MCP handshake.

Registry name
info.astroway/core
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
462 ms
Tools exposed
105 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
Natal charts, planets, houses, aspects, dignities, rendering and the calendar.
Listing
From the official MCP registry (active).
Recent checks of AstroWay Core astrology
CheckedResultHandshake
53 minutes agoHandshake completed462 ms
2 days agoHandshake completed357 ms
5 days agoHandshake completed344 ms
7 days agoHandshake completed138 ms
9 days agoHandshake completed365 ms
11 days agoHandshake completed364 ms
13 days agoHandshake completed355 ms
15 days agoHandshake completed365 ms
17 days agoFailed - the check failed for an unclassified reason—
19 days agoHandshake completed421 ms
20 days agoHandshake completed160 ms
21 days agoFailed - the check failed for an unclassified reason—
23 days agoHandshake completed362 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 Core astrology and makes no claim about it beyond what these checks measured.