Local Markdown library of the papers an evidence review cites: metadata, abstract and full text
Its author marked it deprecated in the MCP Registry
Nothing to run from here
Tripitaka is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
MCP server for the full Pāli Canon — search, cite, compare translations. Offered as Dhamma Dāna.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http tripitaka-mcp https://mcp.tripitaka-mcp.com/mcp
# 2 — ask your agent for something these tools do
# search_by_keyword, survey_corpus, get_sutta and 11 more
Tripitaka costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DSAll 1 server
dhamma-seeker1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http tripitaka-mcp https://mcp.tripitaka-mcp.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Keyword search across the Pāli Tipiṭaka (trigram word-similarity). Searches the configured enabled language(s) on the server. Filterable by pitaka and translation edition. 💡 Hints for the AI client: The system's canonical reference is Romanised Pāli (from SuttaCentral). If the user asks in a disabled or unsupported language, translate the keyword to Romanised Pāli (preferred) or English
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | yes | The word/phrase to search for. |
| language | string | no | Search language — must be in the server's ENABLED_LANGUAGES (default: "pali"). Disabled languages return an error. |
| edition | no | Thai translation edition — "dhiranandi", "jayasaro", "mbu", "royal" or None. Only used when language="thai" and Thai is enabled on the server. | |
| pitaka | no | Filter by pitaka — "vinaya", "sutta", "abhidhamma" or None (all). ✅ v1.1+: all three pitakas at parity with SuttaCentral bilara — see list_structure for live counts. | |
| limit | integer | no | Maximum results (default: 10, max: 50). |
Exhaustively survey the WHOLE Tipiṭaka for a term — guaranteed complete. Use this (not search_by_keyword) when the question is about coverage or counting rather than "show me the best passages": - "How many times does Kusinārā appear in the canon?" - "Every place ānāpānassati is mentioned — don't miss any" - "Which pitakas/how many suttas mention this term?" Unlike search_by_keyword (ran
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | yes | Term to survey (Romanised Pāli preferred; diacritics optional — matching folds ā→a, ṁ→m, etc.). |
| language | string | no | "pali" (default) or "english". Thai is not indexed yet. |
| pitaka | no | Restrict to "vinaya" / "sutta" / "abhidhamma", or None for all. | |
| match_scope | string | no | "word" (default) matches the exact word/phrase only. "stem" also matches inflections + compounds via prefix (kusinārā → kusinārāyaṁ, kusināravagga …) — higher recall, may ov |
| mode | string | no | "fast" (default) = lexical only — quick, no server-side ML, works offline. "thorough" = also run the semantic layer (hosted only; this is the heavier part). The lexical guarantee holds in BOTH. |
| page_size | integer | no | Lexical results per page (default 20, max 100). Counts/forms cover the WHOLE corpus regardless of this. |
| cursor | integer | no | Offset into the full lexical result set for pagination. |
| sem_threshold | number | no | Max cosine distance for semantic hits (default 0.7; lower = stricter). Only used when mode="thorough". |
| sem_limit | integer | no | Max semantic hits (default 50, max 200). capped flags when reached. Only used when mode="thorough". |
Fetch a sutta's content — OR its table of contents (mode="outline"). ⚡ Decide which mode BEFORE calling — don't fetch the whole sutta and parse it yourself: - The user wants the structure / outline / table of contents, or asks "how many sections/parts" / "what's in it" → call get_sutta(sutta_id, mode="outline"). It returns the section list (titles + segment counts + ids), NO
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sutta_id | string | yes | Sutta ID, e.g. "mn1", "dn22", "sn56.11", "dhp1-20". |
| language | string | no | Which language to return — "pali", "thai", "english", or "all" (default: "pali"). Thai is currently disabled on the server, so Thai fields return null. |
| edition | no | Thai translation edition — "dhiranandi", "jayasaro", "mbu", "royal", or None. If None, uses text_thai from bilara-data. ⚠️ The DB has no Thai editions loaded yet, so most values retur | |
| mode | string | no | "full" (default, returns segment text) or "outline" (table of contents only — section keys/titles/counts, no segment text). |
| around | no | A segment_id to center on (e.g. "dn22:18.1"). Returns the window segments before and after it. Ignored if None. | |
| window | integer | no | Segments before AND after around (default 10, clamped 0–200). |
| segment_range | no | Inclusive slice "<startId>..<endId>" (e.g. "dn16:2.1.0..dn16:2.2.8"). Omit the end id to read to the sutta's end. Uses the .. separator. | |
| offset | integer | no | 0-based ordinal start for paging (default 0). |
| limit | no | Max segments to return from offset (default None = to end, clamped 1–2000). |
Semantic search — match by meaning, not exact words. Uses vector similarity (cosine distance) over text_pali embedded with a multilingual MiniLM model. 🤔 In most cases you should use search_hybrid instead — it combines this semantic search with keyword search and ranks better. Use this tool only when you need: - Pure semantic results (no keyword influence) - Fine-grained threshold tun
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Query text (English works best, then Pāli, Thai is weakest). |
| language | string | no | Output language — "pali", "thai", "english", or "all" (Thai disabled → null). |
| limit | integer | no | Maximum results (default: 5, max: 20). |
| threshold | number | no | Maximum cosine distance (smaller = stricter match). Default 0.7; lower to 0.5 for tighter matches, raise to 0.9 for broader. |
Hybrid search — combines keyword + semantic search via RRF. Uses Reciprocal Rank Fusion (RRF) to merge exact-word results with meaning-based results. This is the recommended tool for "discourses about X" / concept queries, because the semantic side catches suttas that discuss a concept using different vocabulary (e.g. some mindfulness-of-breathing suttas use assasati/passasati/dīghaṁ instea
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Query text (Thai, Pāli, or English — English works best). |
| language | string | no | Output language — "pali", "thai", "english", or "all". |
| limit | integer | no | Maximum results (default: 5, max: 20). |
Show the structure of all three pitakas with coverage statistics. 💡 Use this tool when: - The user asks for an overview of the Tipiṭaka (what's in it / which collections). - You need to check coverage before promising a search will find something — segment_count > 0 is the active-loaded signal. - Verifying scope when compiling an artifact. 📊 **Current state (v1.1+, at parity with Sut
No parameter schema on file.
Build a proper citation string for a sutta. 💡 Use this tool when: - The user wants a citation for academic work, an article, or a reference. - You need to know the canonical location of a sutta (pitaka / nikāya). - You want a ready-to-use formatted citation string. 🔗 vs get_sutta: this tool returns metadata + citation only, no segments. Pair it with get_sutta when you want both the con
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sutta_id | string | yes | Sutta ID, e.g. "mn1", "dn22", "sn56.11". |
List the translation editions available, with coverage stats. 💡 Use this tool when: - Before calling compare_translations or get_sutta(edition=...), so you know which edition values are valid and worth comparing. - The user asks which editions are loaded in the DB. 🔍 Filtering: Filtered by the server's TRIPITAKA_ENABLED_LANGUAGES — when Thai is disabled the list is empty. Only
No parameter schema on file.
Compare every available translation for a single segment. 💡 Use this tool when: - The user asks about the meaning/translation of a single Pāli line and wants to see multiple translators side-by-side. - Checking how different translators interpret the same line — technical terms like dukkha, anattā, nibbāna carry nuance that varies across translations. - Academic work that needs t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| segment_id | string | yes | Segment ID, e.g. "mn26:8.2", "dn22:17.1", "mn62:5.3". |
Look up the dictionary meaning of a Pāli word, with sutta context. Serves as a Pāli Dictionary Bridge — pairs the "definition" with the "context where the Buddha actually used the word". 📖 About the dictionary sources: This tool draws from multiple primary dictionaries, including "พจนานุกรมพุทธศาสน์ ฉบับประมวลศัพท์" (Buddhist Dictionary — Concept-Glossary edition) by Somdet Phra Buddhaghosa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| word | string | yes | Word to look up (e.g. "dukkha", "กฐิน"). |
| language | string | no | Dictionary language (e.g. "en", "thai", or "all" as default). |
| limit_context | integer | no | Number of sutta-context examples to include (1-5). |
Verify, check, or confirm a Buddha quote — does the canon really say it? Fact-check a quotation attributed to the Buddha. Catches fake, misquoted, misattributed and misremembered passages, and finds the true reading. Paste a line that has been quoted or half-remembered — Pāli or English — and this says whether the canon really contains it, cites where, and if not, shows the closest thing that is
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The passage as quoted. Diacritics optional, folded internally. One line works best; the canon is segmented line by line, so a quote spanning several segments may only match in part. |
| limit | integer | no | How many near matches to return when it is not exact (1–10). |
Find how the suttas and Vinaya define a Pāli term in their own words. The canon defines its own terms with fixed formulas — "Katamañca … dukkhaṁ?" (what is X?) … "ayaṁ vuccati … dukkhaṁ" (this is called X), "X adhivacana" (X is a designation for …), or the Vinaya "X nāma". This tool locates those definitional passages and returns them cited, so the assistant can present the doctrinal esse
| Parameter | Type | Required | Notes |
|---|---|---|---|
| term | string | yes | Pāli term in its base/dictionary form (e.g. "dukkha", "viññāṇa", "samādhi"). Diacritics optional — folded internally. |
| limit | integer | no | Max definitional passages to return (1–15, default 5). |
| include_similes | boolean | no | Include indirect definitions by simile/metaphor (seyyathāpi …, "is a designation for …"). Default True. |
Strip Pāli inflectional suffixes to find the root form (basic stem). 💡 Use this tool when: - You find an inflected Pāli word (e.g. dukkhassa, bhikkhūnaṁ) and get_word_definition doesn't find it directly — Pāli inflects nouns across 7 cases × 2 numbers, ~16 forms per root. - You want to see possible stems before another get_word_definition lookup. 🔄 Recommended workflow: `
| Parameter | Type | Required | Notes |
|---|---|---|---|
| word | string | yes | An inflected Pāli word (e.g. "dukkhassa", "bhikkhūnaṁ", "sīlavā"). |
Open an interactive sutta viewer inside the chat — Pāli + English, plus an optional third row in the user's own language translated BY YOU. Renders each segment as: Pāli on top (canonical), the bilara-data English below it (verification anchor), and — when you supply translations — your translation in the user's language, clearly badged as AI-generated. Prefer this over dumping raw segments whe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sutta_id | string | yes | — |
| around | no | — | |
| offset | integer | no | — |
| window | integer | no | — |
| translations | no | — | |
| translation_language | no | — | |
| translation_disclaimer | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Tripitaka or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.3.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestaa67d183a9cf58f522f6e174dd1c836678fad76236cb38812121889ee49bac5f
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_by_keyword | no tags | |
| survey_corpus | no tags | |
| get_sutta | untrusted-input | untrusted-input: keyword "fetch" |
| search_semantic | no tags | |
| search_hybrid | no tags | |
| list_structure | no tags | |
| get_reference | no tags | |
| list_editions | no tags | |
| compare_translations | no tags | |
| get_word_definition | no tags | |
| verify_quote | no tags | |
| define_from_suttas | no tags | |
| parse_pali_word | no tags | |
| open_sutta_viewer | untrusted-input | untrusted-input: keyword "fetch" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestaa67d183a9cf58f5
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.3.0.
1.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Tripitaka can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.