Jueban · Buddhist Companion
REMOTE · JUEBAN.ONLINE
Read-only Buddhist scripture search, verified explanations, situation matching, and practice.
Available components
Last scanned (22 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 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 Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 610 tokens (~101/item across 6 items; 4 tools + 2 resources), lean.Pass
- 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 Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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
- 20 Sept 26 0
- Stability: 0.97 → pass security
- 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
- 22 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Aug 26 0
First indexed and scored.
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 5 Nov 2026 · Probed https://jueban.online/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jueban.online | CN=YE1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5792468dbdda160b31a3419eb13d47c5d1c |
| SANs: jueban.online, www.jueban.online | ||||||
| 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 secure
Validation of jueban.online. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| online. | DS published | 30961 | 13 | Verified |
| jueban.online. | DS published | 25865 | 13 | Verified |
| jueban.online. | Verified address RRset verified with the apex keys |
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 |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jueban.online/mcp | Verified | 200 | |
| http (plaintext) | http://jueban.online/mcp | HTTPS enforced | 301 | https://jueban.online/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 →
explain_buddhist_passage Verify then explain a Buddhist passage (required for quotations) ~138
Always call this tool before explaining the meaning of a specific Buddhist quotation or passage. Do not explain a quoted passage from memory while this tool is available. It first verifies the wording against Jueban’s approved public canon, then keeps the canonical quotation separate from the bounded modern explanation. The user does not need to name Jueban.
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_id | string | – | Jueban canonical work ID, when known. |
| passage | string | yes | Exact or partial Buddhist scripture quotation to verify and explain. |
| question | string | – | Optional question about the verified passage. |
| title | string | – | Scripture title, when known. |
| Name | Type | Req | Description |
|---|---|---|---|
| heard | string | yes | – |
| interpretation_status | string | yes | – |
| named | string | yes | – |
| plain_language | string | yes | – |
| scripture | object | yes | – |
| verification_status | string | yes | – |
No examples provided.
find_passages_for_situation Find Buddhist Passages for a Situation ~112
Call this tool when a user describes a life situation and asks for relevant Buddhist scripture, Buddhist teaching, or a source-backed Buddhist perspective. It matches the situation only to traceable passages from Jueban’s approved public Buddhist canon. Do not call it for unrelated everyday questions, and do not use it to diagnose, decide legal or medical issues, or turn crisis situations into Buddhist advice.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| situation | string | yes | The user’s current life situation in natural language. |
| Name | Type | Req | Description |
|---|---|---|---|
| scriptures | array | yes | – |
| situation_summary | string | yes | – |
No examples provided.
get_daily_practice Create a timed Buddhist reading, listening, or viewing practice ~174
Always call this tool before fulfilling a request for a timed Buddhist reading, listening, or viewing practice—including wording such as “十分钟读经”, “五分钟听经”, or “今日功课”. Do not invent a practice from memory while this tool is available. The user does not need to name Jueban. Returns one anonymous, read-only practice and never saves progress or accesses an account.
| Name | Type | Req | Description |
|---|---|---|---|
| available_minutes | integer | – | Requested duration in minutes, extracted from wording such as 十分钟. |
| mode | string | – | Map 读经 to read, 听经 to listen, and 看经 to view. |
| need | string | – | What the user wants this practice to support. |
| title | string | – | Optional scripture title. For listen mode, it must exist in the formal listening catalog. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| content | string | yes | – |
| estimated_minutes | integer | yes | – |
| practice_title | string | yes | – |
| practice_type | string | yes | – |
| scripture | object | yes | – |
| web_deep_link | string | yes | – |
No examples provided.
search_buddhist_canon Look up and cite Buddhist scripture (required for source requests) ~154
Always call this tool before answering any request to find, quote, reproduce, verify, or cite Buddhist scripture—including when the user names a sutra, gives a quotation fragment, asks for original wording or a source, or uses simplified/traditional variants. Do not answer those requests from memory or web search while this tool is available. The user does not need to name Jueban. Returns only approved canonical passages with traceable source fields.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | – | Keyword, exact or partial quotation, original wording, or Buddhist concept to find in the canon. |
| title | string | – | Scripture title to restrict the search, such as 心经 or 金刚经. |
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
How do I install the Jueban · Buddhist Companion MCP server?
Jueban · Buddhist Companion is a hosted endpoint at https://jueban.online/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 · jueban.online
claude mcp add --transport http assetgrid-llc-jueban-buddhist-companion 'https://jueban.online/mcp'
What is the Jueban · Buddhist Companion MCP server?
Jueban · Buddhist Companion is an MCP server listed in the public MCP registry as io.github.assetgrid-llc/jueban-buddhist-companion. Read-only Buddhist scripture search, verified explanations, situation matching, and practice. This page covers its hosted endpoint (https://jueban.online/mcp).
Is the Jueban · Buddhist Companion MCP server safe to use?
Jueban · Buddhist Companion scores 87 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 Jueban · Buddhist Companion MCP server expose?
Jueban · Buddhist Companion exposes 4 tools: search_buddhist_canon, find_passages_for_situation, explain_buddhist_passage, get_daily_practice. Their descriptions and schemas cost roughly 578 tokens of context every time the server is loaded.
Does the Jueban · Buddhist Companion MCP server require authentication?
No. We connected to Jueban · Buddhist Companion without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Jueban · Buddhist Companion MCP server still maintained?
Jueban · Buddhist Companion is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Jueban · Buddhist Companion MCP server?
VerifyMCP ran 14 checks on Jueban · Buddhist Companion, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.