Remote MCP · Endpoint

Dhamma.Gift — Pāli Canon MCP server

No. Dhamma.Gift — Pāli Canon answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://api.dhamma.gift/mcp

The last check completed an MCP handshake.

Registry name
gift.dhamma/pali-canon
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
331 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search and read the Pāli Canon: Pāli root texts with Russian and English translations.
Listing
From the official MCP registry (active).
Recent checks of Dhamma.Gift — Pāli Canon
CheckedResultHandshake
2 days agoHandshake completed331 ms
3 days agoHandshake completed339 ms
3 days agoHandshake completed323 ms
5 days agoHandshake completed292 ms
6 days agoHandshake completed356 ms
7 days agoHandshake completed294 ms
8 days agoHandshake completed403 ms
9 days agoHandshake completed291 ms
11 days agoHandshake completed292 ms
13 days agoHandshake completed290 ms
16 days agoHandshake completed295 ms
18 days agoHandshake completed291 ms
21 days agoHandshake completed295 ms
22 days agoHandshake completed307 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 Dhamma.Gift — Pāli Canon and makes no claim about it beyond what these checks measured.