Remote MCP · Endpoint

Trikaal Vaani Jyotish MCP server

No. Trikaal Vaani Jyotish answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://mcp.trikalvaani.com/mcp

The last check completed an MCP handshake.

Registry name
com.trikalvaani/jyotish
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
777 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Vedic astrology (Jyotish): kundali, dasha, yog, dosha, muhurat, milan — Swiss Ephemeris + BPHS
Listing
From the official MCP registry (active).
Recent checks of Trikaal Vaani Jyotish
CheckedResultHandshake
7 hours agoHandshake completed777 ms
4 days agoHandshake completed783 ms
14 days agoHandshake completed747 ms
15 days agoHandshake completed782 ms
15 days agoHandshake completed765 ms
17 days agoHandshake completed750 ms
18 days agoHandshake completed743 ms
19 days agoHandshake completed731 ms
20 days agoHandshake completed758 ms
21 days agoHandshake completed757 ms
23 days agoHandshake completed754 ms
26 days agoHandshake completed752 ms
28 days agoHandshake completed753 ms

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

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