mcp-registry/app.fojin/fojin-mcp · v0.4.0
As of 2026-10-26 19:28 UTC, the Fojin MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 12 outages in 90 days, with a median recovery of 3 minutes.
Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.
Point your MCP client at this streamable-http endpoint: https://mcp.fojin.ai/mcp
17 parameter(s) across 8 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.fojin%2Ffojin-mcp/fixes
{
"name": "get_parallels",
"description": "Cross-canon parallel passages aligned to a fascicle.\n\n fojin's alignment moat: given a Chinese fascicle, returns the aligned\n Pali/Tibetan/Sanskrit parallels so you can compare how a passage is\n rendered across traditions.\n\n A fascicle returns parallels for the *whole* juan — often hundreds. To\n narrow them to one passage, match the passage against `source_chunks[].text`\n and keep the parallels whose `aligns_source_chunk` equals that chunk_index.\n\n `urn` is filled for parall",
"inputSchema": {
"type": "object",
"title": "get_parallelsArguments",
"required": [
"text_id",
"juan_num"
],
"properties": {
"text_id": {
"type": "integer",
"title": "Text Id"
},
"juan_num": {
"type": "integer",
"title": "Juan Num"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "lookup_dictionary",
"description": "Look up a Buddhist term across fojin's dictionaries (748K+ entries).",
"inputSchema": {
"type": "object",
"title": "lookup_dictionaryArguments",
"required": [
"term"
],
"properties": {
"term": {
"type": "string",
"title": "Term"
},
"limit": {
"type": "integer",
"title": "Limit",
"default": 10
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "lookup_entity",
"description": "Search fojin's knowledge graph for entities — people, places, works,\n doctrinal terms — matching `query`.",
"inputSchema": {
"type": "object",
"title": "lookup_entityArguments",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 10
},
"query": {
"type": "string",
"title": "Query"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.fojin/fojin-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.fojin/fojin-mcp"}) over MCP.
verify_quote ~239 tokensget_parallels ~212 tokenscommentaries ~207 tokenssearch_corpus ~174 tokensread_passage ~128 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fapp.fojin%2Ffojin-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.fojin%2Ffojin-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.fojin%2Ffojin-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.fojin%2Ffojin-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fapp.fojin%2Ffojin-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:73116d11e85fad96…, first seen 2026-10-17, included at leaf 3582 of 75,023. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable data servers · most reliable retrieval servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 19:28 UTC, the Fojin MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 12 outages in 90 days, with a median recovery of 3 minutes.
Fojin MCP server advertises 8 tools, including commentaries, get_parallels, lookup_dictionary, lookup_entity, read_passage.
Point your MCP client at this streamable-http endpoint: https://mcp.fojin.ai/mcp
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.