Remote MCP · Endpoint

Mystic Timing: birth time readings MCP server

No. Mystic Timing: birth time readings answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://mystictiming-mcp.yaletongxue.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
com.mystictiming/bazi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
124 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
What your birth date and time say about you: personality, love, timing. Readings in 20 languages.
Listing
From the official MCP registry (active).
Recent checks of Mystic Timing: birth time readings
CheckedResultHandshake
39 minutes agoHandshake completed124 ms
3 days agoHandshake completed115 ms
13 days agoHandshake completed201 ms
13 days agoHandshake completed159 ms
15 days agoHandshake completed88 ms
16 days agoHandshake completed96 ms
17 days agoHandshake completed87 ms
18 days agoHandshake completed110 ms
18 days agoHandshake completed131 ms
20 days agoHandshake completed92 ms
22 days agoHandshake completed156 ms
25 days agoHandshake completed137 ms
27 days agoHandshake completed91 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.

Listing data comes from the official MCP registry. Glide is not affiliated with Mystic Timing: birth time readings and makes no claim about it beyond what these checks measured.