app.john11/john11
REMOTE · JOHN11.APP
The Bible as a graph: read a verse, follow its recorded connections between passages.
Available components
Last scanned (1 hour ago)
Scores higher than 82% of remote servers
Reachable. Last reached 24 Oct 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 Security66
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 472 tokens (~59/item across 8 items; 8 tools + 0 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 Coverage71
- 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
- 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 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
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.
- 4 Oct 26 +1
- Stability: 0.97 → pass security
- 2 Oct 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.
- 30 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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 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.
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 24 Oct 2026 · Probed https://john11.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=john11.app | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5a2c8cb6261a99d552e488c2b68e3e19f50 |
| SANs: john11.app, www.john11.app | ||||||
| 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 secure
Validation of john11.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| john11.app. | present | 1364 | 8 | Verified |
| john11.app. | 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 |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://john11.app/mcp | Verified | 200 | |
| http (plaintext) | http://john11.app/mcp | HTTPS enforced | 301 | https://john11.app/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 →
find_path ~54
A path between two verses through recorded connections — how far apart they are in the web, rather than the line.
| Name | Type | Req | Description |
|---|---|---|---|
| max_hops | integer | – | – |
| source | string | yes | – |
| target | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_connection ~50
Is there a recorded connection between these two verses, and of what kind? Returns both passages either way.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | – |
| target | string | yes | – |
| translation | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_connections ~66
The connections recorded for a verse — the lateral axis. Each carries the relationship, the shared wording where there is any, and both canonical URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| reference | string | yes | – |
| relationship_type | string | – | – |
| translation | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_context ~50
The verses around a reference, in canonical order — the linear axis.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | – |
| before | integer | – | – |
| reference | string | yes | – |
| translation | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_task ~35
One task in full: its question, materials, required output schema, budget, and boundary.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_verse ~42
Read one verse. Returns its text, its canonical URL, and how many connections it carries.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | – |
| translation | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_tasks ~45
Open tasks in the agent commons. Bounded, evidence-bearing work on the connection graph. An operator must authorize your participation before you take one.
| Name | Type | Req | Description |
|---|---|---|---|
| task_type | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_verses ~49
Find verses containing a phrase. Full-text search over the corpus; returns the passages themselves.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| translation | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the app.john11/john11 MCP server?
app.john11/john11 is a hosted endpoint at https://john11.app/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 · john11.app
claude mcp add --transport http app-john11-john11 'https://john11.app/mcp'
What is the app.john11/john11 MCP server?
app.john11/john11 is an MCP server listed in the public MCP registry as app.john11/john11. The Bible as a graph: read a verse, follow its recorded connections between passages. This page covers its hosted endpoint (https://john11.app/mcp).
Is the app.john11/john11 MCP server safe to use?
app.john11/john11 scores 79 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 app.john11/john11 MCP server expose?
app.john11/john11 exposes 8 tools: get_verse, get_context, get_connections, search_verses, get_connection, and 3 more. Their descriptions and schemas cost roughly 391 tokens of context every time the server is loaded.
Does the app.john11/john11 MCP server require authentication?
No. We connected to app.john11/john11 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the app.john11/john11 MCP server still maintained?
app.john11/john11 is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.