Dhamma.Gift — Pāli Canon
REMOTE · API.DHAMMA.GIFT
Search and read the Pāli Canon: Pāli root texts with Russian and English translations.
Available components
Last scanned (23 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2695 tokens (~539/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_text” rewrote its description, which is the text the model reads security
- Schema quality: 2010 → 2675 ▼ functional
- Server version: 1.2.0 → 1.3.0 functional
- New tool “compare_editions” functional
- “get_text” added an optional parameter “editions” cosmetic
- “get_text” reworded the description of “suttaId” cosmetic
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://api.dhamma.gift/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.dhamma.gift | CN=YE1,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5780aa3aae89e073362b5183fb8457fc227 |
| SANs: api.dhamma.gift | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.dhamma.gift. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| gift. | present | 45508 | 13 | Verified |
| dhamma.gift. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.dhamma.gift/mcp | Verified | 200 | |
| http (plaintext) | http://api.dhamma.gift/mcp | HTTPS enforced | 301 | https://api.dhamma.gift/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_editions ~304
Compare the Pali Canon's editions line by line: the Mahāsaṅgīti beside Buddha Jayanti (Sri Lanka), Chaṭṭha Saṅgāyana (Myanmar), Siam Rath (Thailand), the printed Mahāsaṅgīti of 2005 and the PTS editions (DN, MN, SN, AN). Give a sutta ("sn56.11"), a line ("dn22:18.1") or a range ("sn56.11:5.1-5.4"). The answer starts with a summary per edition (name, license, lines present, missing, differing), then the lines where some edition reads differently, each with the differing words. Case, punctuation and ṁ/ṃ are not counted as differences.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Every line, not only the lines where an edition differs. Default false. |
| editions | array | – | Editions to compare with the Mahāsaṅgīti. Default: all of bjt, my, th, mso, pts. |
| from | string | – | Continue from this line (the next_from of a previous answer). |
| id | string | yes | A sutta (sn56.11), a line (dn22:18.1) or a range of lines (sn56.11:5.1-5.4). |
| limit | integer | – | Lines per answer (default 60); the answer gives next_from to continue. |
No output schema declared.
No examples provided.
compare_translations ~142
One segment of the canon in the Pali root and every available translation side by side. Use a segment id from search/get_text, e.g. "mn129:21.3". Sujato (en_sujato) is excluded unless named in translators.
| Name | Type | Req | Description |
|---|---|---|---|
| langs | array | – | Limit to these languages, e.g. ["ru","en"]. Default: all. |
| segmentId | string | yes | Segment id as returned by search, e.g. mn129:21.3 or dn22:1.1. |
| translators | array | – | Explicit translator keys, e.g. ["en_sujato"] to include Sujato. |
No output schema declared.
No examples provided.
get_text ~279
Fetch a sutta by id (e.g. "dn22", "mn1", "sn56.11") — the Pali text (Mahāsaṅgīti) of every segment. Pali only by default; pass langs for translations, translators to name a translator (e.g. ["en_sujato"]), editions for the whole text of other Pali editions line by line (DN, MN, SN, AN). Same data as dhamma.gift/api/text.
| Name | Type | Req | Description |
|---|---|---|---|
| editions | array | – | Other Pali editions to add, each segment beside the Mahāsaṅgīti: bjt (Buddha Jayanti, Sri Lanka), my (Chaṭṭha Saṅgāyana, Myanmar), th (Siam Rath, Thailand), mso (Mahāsaṅgīti as printed, 2005), pts (P… |
| langs | array | – | Translation languages to include, e.g. ["ru","en"]. Default: none (Pali only). |
| suttaId | string | yes | Sutta id, e.g. dn22, mn1, sn56.11. |
| translators | array | – | Explicit translator keys, e.g. ["en_sujato"] to include Sujato. |
No output schema declared.
No examples provided.
list_structure ~105
What texts exist. Without arguments: collections (sutta/vinaya/abhidhamma/khuddaka), books by id prefix with sutta counts, and translation languages with translators. With prefix (e.g. "mn", "sn56", "an4"): the suttas under it with titles.
| Name | Type | Req | Description |
|---|---|---|---|
| prefix | string | – | Sutta id prefix such as mn, sn56, an4, dhp. Max 200 suttas are listed. |
No output schema declared.
No examples provided.
search ~566
Search the Pali Canon on dhamma.gift by keyword/substring or REGEX (min 3 letters, no semantic search). Patterns like "kata.*dukkha", "vucc.*dukkha", "katha.*dukkha" find the canon's own definitions and expositions of a term. Returns a CENSUS of every matching sutta — id, title, match count, metaphor count, reader link — Pali only, ordered so that suttas that DEFINE the term come first, then ones NAMED after it, then by how often it occurs. Set include_segments for the matched Pali lines, include_translations (+ langs) for translations. 40 suttas by default (25 by occurrence count, plus 15 for suttas named after the term and ones defining it); metadata.totalFiles reports the true count, and limit takes a number or "all".
| Name | Type | Req | Description |
|---|---|---|---|
| exact | boolean | – | Whole-word match only. Default: false. |
| include_segments | boolean | – | Also return the matched Pali segments (segment id, text, reader link). Default: false — the census alone. |
| include_translations | boolean | – | Also return translations of the matched segments (implies include_segments). Default: false. |
| langs | array | – | Translation languages to include with include_translations, e.g. ["ru","en"]. Default: none (Pali only). |
| limit | – | – | How many suttas to list: a number, or "all" for every match. Default: 40, composed of 25 by occurrence count plus 15 for suttas named after the term and defining it. Strict — the cap means the cap. m… |
| query | string | yes | Keyword, phrase, or REGEX pattern to search for (Pali or a translation word). Patterns work and are the way to find definitions: "kata.*dukkha" (Katamañca … dukkhaṁ?), "vucc.*dukkha" (idaṁ vuccati du… |
| scope | string | – | default|all|dhamma|vinaya|abhi|khudakka|or comma-separated nikaya codes (dn,mn,...). Default: default (4 nikayas + 6 KN books). |
| translators | array | – | Explicit translator keys, e.g. ["en_sujato"] to include Sujato, or ["ru_sv"]. Needed only to override the default translator choice. |
No output schema declared.
No examples provided.
How do I install the Dhamma.Gift — Pāli Canon MCP server?
Dhamma.Gift — Pāli Canon is a hosted endpoint at https://api.dhamma.gift/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.dhamma.gift
claude mcp add --transport http gift-dhamma-pali-canon 'https://api.dhamma.gift/mcp'
What is the Dhamma.Gift — Pāli Canon MCP server?
Dhamma.Gift — Pāli Canon is an MCP server listed in the public MCP registry as gift.dhamma/pali-canon. Search and read the Pāli Canon: Pāli root texts with Russian and English translations. This page covers its hosted endpoint (https://api.dhamma.gift/mcp).
Is the Dhamma.Gift — Pāli Canon MCP server safe to use?
Dhamma.Gift — Pāli Canon scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Dhamma.Gift — Pāli Canon MCP server expose?
Dhamma.Gift — Pāli Canon exposes 5 tools: search, get_text, compare_editions, compare_translations, list_structure. Their descriptions and schemas cost roughly 1,396 tokens of context every time the server is loaded.
Does the Dhamma.Gift — Pāli Canon MCP server require authentication?
No. We connected to Dhamma.Gift — Pāli Canon without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Dhamma.Gift — Pāli Canon MCP server still maintained?
Dhamma.Gift — Pāli Canon is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.