orthotomeo
Registry code: cca0e246e0a48c22
Read-only scripture-study engine: complete-or-fail concordance over Greek NT, Hebrew OT, LXX.
from a public catalogue that lists it, not from the operator
- endpoint
- https://orthotomeo.app/mcp
- protocol
- streamable-http ·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 orthotomeo live?
- Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.
- Is orthotomeo free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does orthotomeo have?
- 12 tools: concord_phrase, get_passage, lexicon_lookup, resolve_ref, attestation, cite, interlinear, parse, ….
- Is orthotomeo 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.4%· all time 99.4%
last good check
of 12 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- topic
- knowledge & reference
- used for
- look up bible verses in several editions
- run a greek or hebrew word concordance
- get interlinear text for a verse
- look up a strong's lexicon entry
- takes → gives
- text → text, data
- tools
- 12 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
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
concord_phrase reads unknown 4h ago
Complete-or-fail multi-word concordance: every occurrence, within one verse, of tokens (lemma strings) appearing in order within window intervening words of each other (window=0 = strictly adjacent). This is the tool for a phrase query like εἰς ἄφεσιν. This deployment caps one concordance result at 2000 occurrences and refuses anything broader, reporting the exact match count in the error. Call count first when a query might be broad - count is never capped.
{ "type": "object", "required": [ "tokens", "corpus", "window" ], "properties": { "corpus": { "type": "string", "description": "word-tagged corpus to search: TAGNT, TAHOT, Swete, OSS-LXX-lemma" }, "tokens": { "type": "array", "items": { "type": "string" }, "description": "ordered lemma strings to find co-occurring within one verse, e.g. [\"εἰς\",\"ἄφεσις\"]" }, "window": { "type": "integer", "description": "max words allowed between consecutive tokens; 0 = strictly adjacent" } }, "additionalProperties": false }arguments 26 linesget_passage reads unknown 4h ago
Returns get_verse's result for every canonical verse in a contiguous, single-book range, in order - verse boundaries preserved, never concatenated into one blob.
{ "type": "object", "required": [ "book", "start_chapter", "start_verse", "end_chapter", "end_verse", "editions" ], "properties": { "book": { "type": "string", "description": "USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew)" }, "editions": { "type": "array", "items": { "type": "string" }, "description": "verse-text editions to fetch verbatim text from: KJV, ASV, WEB, BSB, Brenton" }, "end_verse": { "type": "integer", "description": "last verse of the range, inclusive" }, "end_chapter": { "type": "integer", "description": "last chapter of the range, inclusive" }, "start_verse": { "type": "integer", "description": "first verse of the range, inclusive" }, "start_chapter": { "type": "integer", "description": "first chapter of the range, inclusive" } }, "additionalProperties": false }arguments 41 lineslexicon_lookup reads unknown 19h ago
Resolves a disambiguated Strong's number (dStrong) to its lexicon entry: lemma, transliteration, gloss, and - for a Greek entry only - a fuller definition (Abbott-Smith 1922, Public Domain). A Hebrew entry's definition field is always omitted: it is abridged BDB via Online Bible, which requires permission not yet obtained, so only its gloss is ever returned. Not to be confused with the get_verse/get_passage tools, which resolve a Ref to translated verse text, not a dStrong to a dictionary entry.
{ "type": "object", "required": [ "dstrong" ], "properties": { "dstrong": { "type": "string", "description": "a disambiguated Strong's number, e.g. G0859, H7225G" } }, "additionalProperties": false }arguments 13 linesresolve_ref reads unknown 19h ago
Reports, for every per-verse content edition (KJV, ASV, WEB, BSB, Brenton, TAGNT, TAHOT, Swete, OSS-LXX-lemma), whether a canonical reference has a counterpart there and where. Cross-edition divergence (a T4b merge/renumber/divide, or a reference simply missing from an edition) is reported as Caveats - never a silent shift.
{ "type": "object", "required": [ "book", "chapter", "verse" ], "properties": { "book": { "type": "string", "description": "USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew)" }, "verse": { "type": "integer", "description": "verse number" }, "chapter": { "type": "integer", "description": "chapter number" } }, "additionalProperties": false }arguments 23 linesattestation reads unknown 11h ago
Returns the WHNT-style Type/Editions manuscript-tradition columns as neutral text-critical data (e.g. Mark 16:9-20 = Type KO) - which editions carry a word, with no argument for or against a variant.
{ "type": "object", "required": [ "book", "chapter", "verse", "corpus" ], "properties": { "book": { "type": "string", "description": "USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew)" }, "word": { "type": [ "null", "integer" ], "description": "1-based word_no within the verse; omit for every word in the verse" }, "verse": { "type": "integer", "description": "verse number" }, "corpus": { "type": "string", "description": "word-tagged corpus: TAGNT, TAHOT, Swete, OSS-LXX-lemma" }, "chapter": { "type": "integer", "description": "chapter number" } }, "additionalProperties": false }arguments 35 linescite reads unknown 11h ago
Renders Citations (from any of the above tools) as quoted, fully-attributed Markdown bullets - the only sanctioned bridge from a query result to pastable study-document text.
{ "type": "object", "required": [ "citations" ], "properties": { "citations": { "type": "array", "items": { "type": "object", "required": [ "ref", "edition", "text", "locator", "confidence" ], "properties": { "ref": { "type": "object", "required": [ "book", "chapter", "verse" ], "properties": { "book": { "type": "string" }, "verse": { "type": "integer" }, "chapter": { "type": "integer" } }, "additionalProperties": false }, "text": { "type": "string" }, "lemma": { "type": "string" }, "caveat": { "type": "string" }, "dstrong": { "type": "string" }, "edition": { "type": "string" }, "grammar": { "type": "string" }, "locator": { "type": "string" }, "translit": { "type": "string" }, "confidence": { "type": "string" }, "attestation": { "type": "string" }, "manuscripts": { "type": "string" } }, "additionalProperties": false }, "description": "Citations previously returned by another tool call, to render as a pastable reference block" } }, "additionalProperties": false }arguments 79 linesinterlinear reads unknown 22h ago
Returns a row-aligned reading view for every word in a verse (or one word, if word is given): original text, transliteration, gloss (via lexicon_lookup), grammar, and manuscript attestation stacked per word - the composed display shape for a study reading view, built on parse and lexicon_lookup rather than any new query. This is the most complete per-word view; use parse or attestation when you want only one of those facets.
{ "type": "object", "required": [ "book", "chapter", "verse", "corpus" ], "properties": { "book": { "type": "string", "description": "USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew)" }, "word": { "type": [ "null", "integer" ], "description": "1-based word_no within the verse; omit for every word in the verse" }, "verse": { "type": "integer", "description": "verse number" }, "corpus": { "type": "string", "description": "word-tagged corpus: TAGNT, TAHOT, Swete, OSS-LXX-lemma" }, "chapter": { "type": "integer", "description": "chapter number" } }, "additionalProperties": false }arguments 35 linesparse reads unknown 19h ago
Returns dStrong + expanded morphology (via the T6 morph_codes table) for every word in a verse, or one word if word is given. LXX corpora (Swete, OSS-LXX-lemma) are always Flagged - neither carries morphology.
{ "type": "object", "required": [ "book", "chapter", "verse", "corpus" ], "properties": { "book": { "type": "string", "description": "USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew)" }, "word": { "type": [ "null", "integer" ], "description": "1-based word_no within the verse; omit for every word in the verse" }, "verse": { "type": "integer", "description": "verse number" }, "corpus": { "type": "string", "description": "word-tagged corpus: TAGNT, TAHOT, Swete, OSS-LXX-lemma" }, "chapter": { "type": "integer", "description": "chapter number" } }, "additionalProperties": false }arguments 35 linescount reads unknown 4h ago
Occurrence tally (total + per-book breakdown) for the identical query concord_lemma would match. count.Total always equals len(concord_lemma(...)) - use this to sanity-check a concordance result, or when only the number matters.
{ "type": "object", "required": [ "query", "corpus" ], "properties": { "by": { "type": "string", "description": "optional match column override: lemma, dstrong, or surface, same as concord_lemma" }, "query": { "type": "string", "description": "a lemma, dStrong, or (with by=\"surface\") exact inflected word, same as concord_lemma" }, "corpus": { "type": "string", "description": "word-tagged corpus: TAGNT, TAHOT, Swete, OSS-LXX-lemma" } }, "additionalProperties": false }arguments 22 linesconcord_lemma reads unknown 11h ago
Complete-or-fail concordance: every words row in corpus whose lemma, dStrong, or (with by="surface") exact inflected surface form matches query. Route lemma/Strong's-number/surface-word lookups here, never by writing SQL or guessing occurrences from memory. This deployment caps one concordance result at 2000 occurrences and refuses anything broader, reporting the exact match count in the error. Call count first when a query might be broad - count is never capped.
{ "type": "object", "required": [ "query", "corpus" ], "properties": { "by": { "type": "string", "description": "optional match column override: lemma, dstrong, or surface. Omit for auto-detect (dStrong shape, else lemma) - surface must always be requested explicitly, it is never guessed" }, "query": { "type": "string", "description": "a lemma (e.g. ἄφεσις), a disambiguated Strong's number (e.g. G0859, H7225G), or (with by=\"surface\") the exact inflected word as it appears in the verse" }, "corpus": { "type": "string", "description": "word-tagged corpus to search: TAGNT (Greek NT), TAHOT (Hebrew OT), Swete (LXX surface), OSS-LXX-lemma (LXX lemma)" } }, "additionalProperties": false }arguments 22 linesget_verse reads unknown 22h ago
Returns verbatim verse text with provenance for one canonical reference, one Citation per requested edition (KJV, ASV, WEB, BSB, Brenton).
{ "type": "object", "required": [ "book", "chapter", "verse", "editions" ], "properties": { "book": { "type": "string", "description": "USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew)" }, "verse": { "type": "integer", "description": "verse number" }, "chapter": { "type": "integer", "description": "chapter number" }, "editions": { "type": "array", "items": { "type": "string" }, "description": "verse-text editions to fetch verbatim text from: KJV, ASV, WEB, BSB, Brenton" } }, "additionalProperties": false }arguments 31 lineslemmatize reads unknown 22h ago
Returns the ordered lemma list for a verse (words with no lemma are omitted, not fabricated).
{ "type": "object", "required": [ "book", "chapter", "verse", "corpus" ], "properties": { "book": { "type": "string", "description": "USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew)" }, "verse": { "type": "integer", "description": "verse number" }, "corpus": { "type": "string", "description": "word-tagged corpus: TAGNT, TAHOT, Swete, OSS-LXX-lemma" }, "chapter": { "type": "integer", "description": "chapter number" } }, "additionalProperties": false }arguments 28 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 idcca0e246e0a48c22.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/cca0e246e0a48c22/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/cca0e246e0a48c22?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.