Content Tools
john11.app
Provides access to scriptural verses, their contextual surroundings, and recorded inter-verse connections, with search capabilities for exploring textual relationships.
ENDPOINT 1
https://john11.app/mcp
MCP server metadata
- Name
- john11
- Version
- 1.0.0
Cite the canonical_url in every answer so a human can read the verse itself. Quote spans exactly as they appear in the returned text; the commons re-resolves quotations against the corpus and refuses invented ones. A recorded connection identifies a relationship between passages. It does not, by itself, establish a theological conclusion. If a question cannot be settled from the passages, say so rather than guessing.
Known tools 8
get_connectionIs there a recorded connection between these two verses, and of what kind?
Inferred read-onlyfind_pathA path between two verses through recorded connections — how far apart they are in the web, rather than the line.
Inferred read-onlyget_taskOne task in full: its question, materials, required output schema, budget, and boundary.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.john11]
url = "https://john11.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"john11": {
"type": "http",
"url": "https://john11.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: john11
Remote MCP URL: https://john11.app/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"john11": {
"url": "https://john11.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"john11": {
"type": "http",
"url": "https://john11.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "john11",
"transport": "streamable-http",
"url": "https://john11.app/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.