Remote MCP · Endpoint

AstroWay Tarot MCP server

No. AstroWay Tarot answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://mcp.astroway.info/mcp/tarot

The last check completed an MCP handshake.

Registry name
info.astroway/tarot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
378 ms
Tools exposed
89 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Rider-Waite-Smith, Marseille and Lenormand: spreads, draws, card pictures and spread readings.
Listing
From the official MCP registry (active).
Recent checks of AstroWay Tarot
CheckedResultHandshake
44 minutes agoHandshake completed378 ms
3 days agoHandshake completed117 ms
12 days agoHandshake completed140 ms
13 days agoFailed - the check failed for an unclassified reason—
14 days agoHandshake completed138 ms
15 days agoHandshake completed199 ms
16 days agoHandshake completed382 ms
17 days agoHandshake completed353 ms
18 days agoHandshake completed349 ms
20 days agoHandshake completed163 ms
22 days agoHandshake completed127 ms
25 days agoHandshake completed200 ms
27 days agoHandshake completed166 ms

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

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 Tarot and makes no claim about it beyond what these checks measured.