mcp-registry/app.john11/john11 · v1.0.0
As of 2026-10-24 01:06 UTC, the John11 MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 27 outages in 90 days, with a median recovery of 7 minutes.
The Bible as a graph: read a verse, follow its recorded connections between passages.
Claude Code
claude mcp add --transport http john11-mcp-server https://john11.app/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"john11-mcp-server": {
"type": "http",
"url": "https://john11.app/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
21 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 →
Handshake + tools/list takes ~1,833 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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.john11%2Fjohn11/fixes
{
"name": "find_path",
"description": "A path between two verses through recorded connections — how far apart they are in the web, rather than the line.",
"inputSchema": {
"type": "object",
"title": "find_pathArguments",
"required": [
"source",
"target"
],
"properties": {
"source": {
"type": "string",
"title": "Source"
},
"target": {
"type": "string",
"title": "Target"
},
"max_hops": {
"type": "integer",
"title": "Max Hops",
"default": 4
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_connection",
"description": "Is there a recorded connection between these two verses, and of what kind? Returns both passages either way.",
"inputSchema": {
"type": "object",
"title": "get_connectionArguments",
"required": [
"source",
"target"
],
"properties": {
"source": {
"type": "string",
"title": "Source"
},
"target": {
"type": "string",
"title": "Target"
},
"translation": {
"type": "string",
"title": "Translation",
"default": "BSB"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_connections",
"description": "The connections recorded for a verse — the lateral axis. Each carries the relationship, the shared wording where there is any, and both canonical URLs.",
"inputSchema": {
"type": "object",
"title": "get_connectionsArguments",
"required": [
"reference"
],
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 10
},
"reference": {
"type": "string",
"title": "Reference"
},
"translation": {
"type": "string",
"title": "Translation",
"default": "BSB"
},
"relationship_type": {
"type": "string",
"title": "Relationship Type",
"default": ""
}
}
},
"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.john11/john11"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.john11/john11"}) over MCP.
get_connections ~155 tokensget_context ~123 tokensget_connection ~117 tokenssearch_verses ~114 tokensfind_path ~113 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.john11%2Fjohn11?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.john11%2Fjohn11?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.john11%2Fjohn11.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.john11%2Fjohn11.svg :target: https://glimind.com/server/mcp-registry%2Fapp.john11%2Fjohn11?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:b75cd3fb057d51d2…, first seen 2026-10-17, included at leaf 2914 of 55,663. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable retrieval servers · most reliable productivity 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-24 01:06 UTC, the John11 MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 27 outages in 90 days, with a median recovery of 7 minutes.
John11 MCP server advertises 8 tools, including find_path, get_connection, get_connections, get_context, get_task.
Point your MCP client at this streamable-http endpoint: https://john11.app/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.