fojin — Buddhist Canon Tools
REMOTE · MCP.FOJIN.AI · SCANNED SEP 28
Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.
Available components
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 Security46
- 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 8 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1137 tokens (~142/item across 8 items; 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the fojin — Buddhist Canon Tools MCP server?
fojin — Buddhist Canon Tools is a hosted endpoint at https://mcp.fojin.ai/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 · mcp.fojin.ai
claude mcp add --transport http app-fojin-fojin-mcp 'https://mcp.fojin.ai/mcp'
{
"mcpServers": {
"app-fojin-fojin-mcp": {
"url": "https://mcp.fojin.ai/mcp"
}
}
} {
"servers": {
"app-fojin-fojin-mcp": {
"type": "http",
"url": "https://mcp.fojin.ai/mcp"
}
}
} [mcp_servers.app-fojin-fojin-mcp] url = "https://mcp.fojin.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-fojin-fojin-mcp": {
"type": "remote",
"url": "https://mcp.fojin.ai/mcp",
"enabled": true
}
}
} openclaw mcp add app-fojin-fojin-mcp --url 'https://mcp.fojin.ai/mcp' --transport streamable-http
mcp_servers:
app-fojin-fojin-mcp:
url: "https://mcp.fojin.ai/mcp" {
"McpServers": {
"app-fojin-fojin-mcp": {
"Transport": "http",
"Url": "https://mcp.fojin.ai/mcp"
}
}
} assistant mcp add app-fojin-fojin-mcp -t streamable-http -u 'https://mcp.fojin.ai/mcp'
{
"mcpServers": {
"app-fojin-fojin-mcp": {
"type": "http",
"url": "https://mcp.fojin.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Aug 26 0
- Tool “get_parallels” rewrote its description, which is the text the model reads security
- Schema quality: 129 → 142 ▼ functional
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 28 Sept 2026 · Probed https://mcp.fojin.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fojin.ai | CN=YE2,O=Let's Encrypt,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6184212134d325bcc073b0bd188656d408e |
| SANs: *.fojin.ai, fojin.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 mcp.fojin.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| fojin.ai. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.fojin.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.fojin.ai/mcp | Inconclusive | 406 |
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 →
commentaries ~232
What the historical commentators said about a passage of Buddhist scripture. Give a line of a sūtra and get back the classical commentaries that gloss it — each with the commentator's own words, the work it comes from, a quality tier, and a resolvable citation. This is the layer no other tool exposes for the Chinese canon: CBETA marks up almost none of it, and the alignment behind this was derived text by text. Two things to read carefully rather than skim. `total` is how many commentators the passage actually has — `truncated` says the list you got is a sample. And coverage is partial: roughly half of what a commentator wrote is not aligned, so an absent commentator means "not in the data", never "he said nothing". When nothing matches, `available_sutras` tells you which sūtras have data at all — do not read a miss as silence from the tradition.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| quote | string | yes | – |
No output schema declared.
No examples provided.
get_parallels ~194
Cross-canon parallel passages aligned to a fascicle. fojin's alignment moat: given a Chinese fascicle, returns the aligned Pali/Tibetan/Sanskrit parallels so you can compare how a passage is rendered across traditions. A fascicle returns parallels for the *whole* juan — often hundreds. To narrow them to one passage, match the passage against `source_chunks[].text` and keep the parallels whose `aligns_source_chunk` equals that chunk_index. `urn` is filled for parallels that are fojin works; rows with `source="mitra-parallel"` are inline Skt/Tib sentences with no fojin work to cite, so they carry `original_preview` instead and stay `urn: null`.
| Name | Type | Req | Description |
|---|---|---|---|
| juan_num | integer | yes | – |
| text_id | integer | yes | – |
No output schema declared.
No examples provided.
lookup_dictionary ~39
Look up a Buddhist term across fojin's dictionaries (748K+ entries).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| term | string | yes | – |
No output schema declared.
No examples provided.
lookup_entity ~47
Search fojin's knowledge graph for entities — people, places, works, doctrinal terms — matching `query`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
read_passage ~82
Read the full content of one fascicle (卷) of a text, with its `urn`. Use the `text_id`/`juan_num` from a search_corpus hit. Returns the actual canonical text — quote from this, not from memory.
| Name | Type | Req | Description |
|---|---|---|---|
| juan_num | integer | yes | – |
| text_id | integer | yes | – |
No output schema declared.
No examples provided.
resolve_urn ~62
Resolve a fojin URN (e.g. fojin:cbeta/T0001.1) to a reader URL and confirm it exists in the corpus. Use to verify or dereference a citation.
| Name | Type | Req | Description |
|---|---|---|---|
| urn | string | yes | – |
No output schema declared.
No examples provided.
search_corpus ~107
Semantic search across fojin's Buddhist corpus (10K+ texts, 30+ langs). Returns the most relevant passages, each with a `urn`, title, snippet and similarity score. `lang` optionally filters by language code (lzh=Classical Chinese, pi=Pali, sa=Sanskrit, bo=Tibetan, en=English).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | – | – | – |
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
verify_quote ~264
Verify that a Buddhist-canon quote exists VERBATIM in the corpus. Call this before presenting any quoted scripture to a reader: LLMs routinely invent plausible-looking quotes. Returns `verbatim` (bool), where it was found (`matches`, each with a resolvable `urn`), or the closest near-miss window when it wasn't. `cite` optionally narrows the search — a CBETA id ("T0374") or fojin URN ("fojin:cbeta/T0374.13") — and `cite_matched` reports honestly whether the quote is where you claimed (a hit in a different fascicle does NOT confirm your citation). Quote must be ≥4 CJK chars after normalisation; Classical Chinese only. Short quotes are answered but say less: a four-character phrase recurs across the canon, so read `cite_matched` rather than `verbatim`, and check `matches_capped` before treating the list as complete. Each match carries an absolute `reader_url` — cite that, not a reconstructed third-party link.
| Name | Type | Req | Description |
|---|---|---|---|
| cite | – | – | – |
| juan | – | – | – |
| quote | string | yes | – |
No output schema declared.
No examples provided.
What is the fojin — Buddhist Canon Tools MCP server?
fojin — Buddhist Canon Tools is an MCP server listed in the public MCP registry as app.fojin/fojin-mcp. Buddhist canon tools: search, passages, cross-canon parallels, dictionaries, all URN-cited. This page covers its hosted endpoint (https://mcp.fojin.ai/mcp).
Is the fojin — Buddhist Canon Tools MCP server safe to use?
fojin — Buddhist Canon Tools scores 70 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 fojin — Buddhist Canon Tools MCP server expose?
fojin — Buddhist Canon Tools exposes 8 tools: search_corpus, read_passage, get_parallels, lookup_dictionary, lookup_entity, and 3 more. Their descriptions and schemas cost roughly 1,027 tokens of context every time the server is loaded.
Does the fojin — Buddhist Canon Tools MCP server require authentication?
No. We connected to fojin — Buddhist Canon Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the fojin — Buddhist Canon Tools MCP server still maintained?
fojin — Buddhist Canon Tools is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.