Complete versioned GetBible API server for the Model Context Protocol
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"getbible-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# GetBible MCP <!-- mcp-name: net.getbible/mcp --> [](https://github.com/getbible/mcp/actions/workflows/test.yml) [](https://pypi.org/project/getbible-mcp/) [](LICENSE) **Project and API documentation:** [getBible.net](https://getBible.net) · **MCP usage guide:** [getBible.net/mcp](https://getBible.net/mcp). Read-only Model Context Protocol access to all nine GetBible API contracts over both standard MCP transports: - **Streamable HTTP** at the official endpoint [https://mcp.getbible.net/](https://mcp.getbible.net/), or another host's MCP URL - **stdio** for developers who install the package and let an AI client launch it locally Both transports expose exactly the same tools, resources, prompts, validation, and scripture-cache integrity rules. Scripture tools default to upstream v3; select `api_version: "v2"` explicitly for upstream v2. Dictionary, commentary and bookmark operations use v1. ## Connect to the official endpoint **GetBible's official MCP endpoint is [https://mcp.getbible.net/](https://mcp.getbible.net/).** Add that exact URL to your AI application's remote MCP connections and select **Streamable HTTP**. The domain root is the protocol endpoint; do not append `/mcp` or an API version. The [MCP usage page](https://getBible.net/mcp) explains how to connect and use the service. One connection provides Bible retrieval, reference lookup, full-text search, dictionaries, commentaries and public bookmarks across all supported API versions. Your client can discover tools, read the complete API contracts and use the integration-planning prompt. All operations are read-only; select upstream versions through tool arguments. Public access is free and needs no account or token. It uses the same default anonymous traffic limits as GetBible se…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.