Remote MCP · Endpoint

Gita & Mahabharata MCP server

No. Gita & Mahabharata answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://dharma-mcp.iag.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.theindianappguy/gita-mahabharata-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
190 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Full Bhagavad Gita (Sanskrit + English) and Ganguli's Mahabharata: search verses and passages.
Listing
From the official MCP registry (active).
Recent checks of Gita & Mahabharata
CheckedResultHandshake
1 hour agoHandshake completed190 ms
8 days agoHandshake completed337 ms
9 days agoHandshake completed211 ms
11 days agoHandshake completed175 ms
12 days agoHandshake completed305 ms
13 days agoHandshake completed266 ms
14 days agoHandshake completed194 ms
14 days agoHandshake completed425 ms
16 days agoHandshake completed582 ms
19 days agoHandshake completed169 ms
21 days agoHandshake completed349 ms
24 days agoHandshake completed204 ms
26 days agoHandshake completed196 ms
28 days agoHandshake completed208 ms

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

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