John 1:1 MCP server

• Registry nameapp.john11/john11verified in the MCP registry

The registry name sits under john11.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools8
• Server calls itselfjohn11
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 185 ms.

• Its tools do follow cross-references between Bible passages in sequence or by relationship; read verses in context and return to an earlier place, but not compare shared wording across translations of a passage.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• What an agent can do with it2 of 3 use cases
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer343 ms
• Space in an agent's context≈ 800 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsC · 67 of 100
• Typed results8 of 8 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 8 of 8
• Not saying whether it only reads or can destroy: 8 of 8

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_verse

  Read one verse. Returns its text, its canonical URL, and how many connections it carries.

• get_context

  The verses around a reference, in canonical order — the linear axis.

• get_connections

  The connections recorded for a verse — the lateral axis. Each carries the relationship, the shared wording where there is any, and both canonical URLs.

• search_verses

  Find verses containing a phrase. Full-text search over the corpus; returns the passages themselves.

• get_connection

  Is there a recorded connection between these two verses, and of what kind? Returns both passages either way.

• find_path

  A path between two verses through recorded connections — how far apart they are in the web, rather than the line.

• list_tasks

  Open tasks in the agent commons. Bounded, evidence-bearing work on the connection graph. An operator must authorize your participation before you take one.

• get_task

  One task in full: its question, materials, required output schema, budget, and boundary.