bibelstudium-mcp
https://mcp.bibelstudium-mcp.de
Registry code: 277f86f0016f1348
bibelstudium-mcp server, version 0.6.32. Quote scripture only from the bible_* tools, never from memory. When asked which server or MCP version is running, report this version.
- endpoint
- https://mcp.bibelstudium-mcp.de/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is bibelstudium-mcp live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is bibelstudium-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does bibelstudium-mcp have?
- 7 tools: bible_crossrefs, bible_lookup, bible_original, bible_search, bible_compare, bible_concordance, bible_server_info.
- Is bibelstudium-mcp safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.7%· all time 99.7%
last good check
of 7 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- look up bible verses in german
- search the german bible text
- study original greek and hebrew words
- find cross references for a verse
- takes → gives
- text → text, data
- tools
- 7 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
bible_server_info reads open 18h ago
Report this server's own release version and which Bible data it has loaded, including each edition's licence, required attribution and how many verses it may quote verbatim per call. Use when asked which version runs, when collecting facts for a bug report, and before planning a longer quotation. Returns no scripture — use bible_lookup for verse text.
{ "type": "object", "properties": {} }arguments 4 linesbible_crossrefs reads unknown 5h ago
Find cross-references (related/parallel passages) for one Bible verse, ranked by relevance votes, with the German text of the targets (in editions that cap verbatim quoting, the later targets carry `stelle` and `votes` only). Use this to find where a theme, quote or promise recurs elsewhere in Scripture. Where the UBS Parallel Passage Database lists the verse, `parallelen` adds the closed set of parallel places (synoptic pericopes, Kings/Chronicles doublets, OT quotations in the NT, recurring formulas) that the vote ranking often buries. Data: Treasury of Scripture Knowledge (expanded), OpenBible.info, CC-BY; UBS Parallel Passage Database, CC BY-SA 4.0.
{ "type": "object", "required": [ "book", "chapter", "verse" ], "properties": { "book": { "type": "string", "description": "Book name in German (e.g. \"Jesaja\", \"1. Mose\", \"Römer\")" }, "limit": { "type": "number", "default": 10, "description": "Maximum number of references to return (default 10, max 30)" }, "verse": { "type": "number", "description": "Single verse number" }, "chapter": { "type": "number", "description": "Chapter number" }, "translation": { "type": "string", "default": "SLT", "description": "Translation for the quoted target texts: \"LUT\" (Luther 1912), \"SCH\" (Schlachter 1951), \"ELB\" (Elberfelder 1871), \"MB\" (Menge 1939), \"SLT\" (Schlachter 2000). Default: \"SLT\" (Schlachter 2000). Aliases like \"luther\", \"schlachter\" accepted. Only editions this instance actually loaded can be requested; bible_server_info lists them." } } }arguments 32 linesbible_lookup reads unknown 5h ago
Look up Bible verses by reference. Returns exact text from a licensed German translation (see the `translation` argument for this instance's default). Use this for ALL Bible quotes — never quote from memory. When the edition carries footnotes for the requested verses, the field 'fussnoten' holds them verbatim: these are the publisher's own notes, not this server's, and they typically record an alternative rendering the edition weighed. Also call it when a book or reference looks unfamiliar, misspelled or made up, and before answering whether a book exists or belongs to the canon: the error names the nearest known book and states which canon this database covers. Do not answer such questions from memory either — a reference that seems wrong is a reason to call this tool, not to skip it.
{ "type": "object", "required": [ "book", "chapter" ], "properties": { "book": { "type": "string", "description": "Book name in German (e.g. \"Jesaja\", \"1. Mose\", \"Römer\", \"Ps\", \"Mt\")" }, "verses": { "type": "string", "description": "Verse(s): single \"4\", range \"16-17\", list \"1,3,5\", or combined \"1-3,7\". Omit for the whole chapter. Some editions cap how many verses one call may quote; the response then says so in `hinweis` and `gekuerzt`, and `reference` names what it contains." }, "chapter": { "type": "number", "description": "Chapter number" }, "translation": { "type": "string", "default": "SLT", "description": "Translation: \"LUT\" (Luther 1912), \"SCH\" (Schlachter 1951), \"ELB\" (Elberfelder 1871), \"MB\" (Menge 1939), \"SLT\" (Schlachter 2000). Default: \"SLT\" (Schlachter 2000). Aliases like \"luther\", \"schlachter\" accepted. Only editions this instance actually loaded can be requested; bible_server_info lists them." } } }arguments 26 linesbible_original reads unknown 5h ago
Return one Bible verse word-by-word in the ORIGINAL language with lemma, Strong's number and full morphology. Use this to verify what the original text says — e.g. whether a noun is singular or plural — instead of inferring it from a translation. Covers the whole Bible: the OT (book 1–39) is served from the Hebrew/Aramaic Westminster Leningrad Codex; the NT (40–66) from a Greek text type chosen via `texttyp` — "byzantine" (Majority Text, default), "sblgnt" (critical), or "tr" (Textus Receptus, the only one with the Comma Johanneum). Edition and text type are labelled in the output.
{ "type": "object", "required": [ "book", "chapter", "verse" ], "properties": { "book": { "type": "string", "description": "Book name in German (e.g. \"1. Mose\", \"Jesaja\", \"Römer\", \"Galater\")" }, "verse": { "type": "number", "description": "Single verse number" }, "chapter": { "type": "number", "description": "Chapter number" }, "texttyp": { "type": "string", "default": "byzantine", "description": "NT text edition: \"byzantine\" (Majority Text, default), \"sblgnt\" (critical SBL), or \"tr\" (Textus Receptus). Ignored for the OT (always Hebrew WLC). Compare byzantine vs. tr to see TR-only readings such as the Comma Johanneum (1Joh 5,7)." } } }arguments 27 linesbible_search reads unknown 1h ago
Full-text search over the German Bible text. Finds verses containing ALL given words (exact word forms; umlauts/accents are folded, so 'fuhrt' matches "führt"). Quote phrases ("Gnade um Gnade"); a trailing * makes a prefix search (lieb* finds liebe/lieben/liebet …). Use this to locate a passage when the wording is known but the reference is not. Optionally restrict to one book.
{ "type": "object", "required": [ "query" ], "properties": { "book": { "type": "string", "description": "Optional: restrict to one book (German name, e.g. \"Psalmen\", \"Röm\")" }, "limit": { "type": "number", "default": 10, "description": "Maximum verses to return (default 10, max 50); the total count is always exact" }, "query": { "type": "string", "description": "Words or \"phrases\" to search for, e.g. 'Hirte mangeln' or '\"Gnade um Gnade\"'" }, "translation": { "type": "string", "default": "SLT", "description": "Translation to search: \"LUT\" (Luther 1912), \"SCH\" (Schlachter 1951), \"ELB\" (Elberfelder 1871), \"MB\" (Menge 1939), \"SLT\" (Schlachter 2000). Default: \"SLT\" (Schlachter 2000). Aliases like \"luther\", \"schlachter\" accepted. Only editions this instance actually loaded can be requested; bible_server_info lists them." } } }arguments 26 linesbible_compare reads unknown 18h ago
Compare one NT verse word-by-word across the Greek editions (byzantine Majority Text, tr Textus Receptus, sblgnt critical text) and list the textual differences. Accentuation/case are ignored (byzantine/tr are stored unaccented), so reported differences are real variants or spelling variants (e.g. movable Ny). Additionally reports per-word attestation across eight editions (NA27/28, Tyndale House, SBL, Westcott-Hort, Tregelles, TR, Byzantine; STEPBible TAGNT). Use for questions about textual variants (e.g. the Comma Johanneum, 1Jn 5:7). OT verses have only one edition (WLC) and cannot be compared.
{ "type": "object", "required": [ "book", "chapter", "verse" ], "properties": { "book": { "type": "string", "description": "NT book name in German (e.g. \"Römer\", \"1Joh\")" }, "verse": { "type": "number", "description": "Single verse number" }, "chapter": { "type": "number", "description": "Chapter number" } } }arguments 22 linesbible_concordance reads unknown 18h ago
Concordance / word study: find ALL occurrences of an original-language word across the Bible. Search by Strong's number (preferred; "G26" = Greek/NT, "H7225" = Hebrew/OT) or by exact lemma as returned by bible_original (e.g. "ἀγάπη", "רֵאשִׁית"). Returns total count, per-book distribution, an occurrence list with the inflected surface forms, and English lexicon data (gloss, Strong's definition; for Greek also the full Abbott-Smith entry). NT edition selectable via texttyp (default byzantine).
{ "type": "object", "required": [], "properties": { "lemma": { "type": "string", "description": "Exact Greek or Hebrew lemma (alternative to strong; script determines testament)" }, "limit": { "type": "number", "default": 50, "description": "Maximum occurrences to list (default 50, max 200); counts are always exact" }, "strong": { "type": "string", "description": "Strong's number with testament prefix, e.g. \"G26\" or \"H7225\"" }, "texttyp": { "type": "string", "default": "byzantine", "description": "NT text edition: \"byzantine\" (default), \"sblgnt\", or \"tr\". Ignored for Hebrew." } } }arguments 24 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id277f86f0016f1348.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/277f86f0016f1348/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/277f86f0016f1348?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.