Remote MCP · Endpoint

AstralHoro MCP server

No. AstralHoro answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://astralhoro.com/mcp

The last check completed an MCP handshake.

Registry name
com.astralhoro/astralhoro
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
528 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Tropical natal charts, transits, and Sun, Moon, and rising from a birth date and place.
Listing
From the official MCP registry (active).
Recent checks of AstralHoro
CheckedResultHandshake
34 minutes agoHandshake completed528 ms
9 days agoHandshake completed424 ms
10 days agoHandshake completed489 ms
11 days agoHandshake completed378 ms
12 days agoHandshake completed406 ms
14 days agoHandshake completed562 ms
14 days agoHandshake completed313 ms
15 days agoHandshake completed437 ms
17 days agoHandshake completed723 ms
19 days agoHandshake completed447 ms
21 days agoHandshake completed442 ms
24 days agoHandshake completed843 ms
26 days agoHandshake completed919 ms
28 days agoHandshake completed367 ms

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