Remote MCP · Endpoint

Astroclaw MCP server

No. Astroclaw answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://www.astroclaw.xyz/api/mcp

The last check completed an MCP handshake.

Registry name
xyz.astroclaw/astroclaw
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
941 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Daily horoscopes for AI agents: one playful forecast per zodiac sign, every day.
Website
https://www.astroclaw.xyz/
Listing
From the official MCP registry (active).
Recent checks of Astroclaw
CheckedResultHandshake
7 hours agoHandshake completed941 ms
12 hours agoHandshake completed410 ms
2 days agoHandshake completed399 ms
4 days agoHandshake completed981 ms
7 days agoHandshake completed413 ms
9 days agoHandshake completed980 ms
11 days agoHandshake completed391 ms
14 days agoHandshake completed438 ms
15 days agoHandshake completed923 ms
18 days agoHandshake completed426 ms
20 days agoHandshake completed383 ms
21 days agoHandshake completed409 ms
23 days agoHandshake completed88 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Astroclaw and makes no claim about it beyond what these checks measured.