io.github.jrainsberger/orthotomeo
REMOTE · ORTHOTOMEO.APP · SCANNED SEP 24
Read-only scripture-study engine: complete-or-fail concordance over Greek NT, Hebrew OT, LXX.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1920 tokens (~160/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.jrainsberger/orthotomeo MCP server?
io.github.jrainsberger/orthotomeo is a hosted endpoint at https://orthotomeo.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · orthotomeo.app
claude mcp add --transport http jrainsberger-orthotomeo 'https://orthotomeo.app/mcp'
{
"mcpServers": {
"jrainsberger-orthotomeo": {
"url": "https://orthotomeo.app/mcp"
}
}
} {
"servers": {
"jrainsberger-orthotomeo": {
"type": "http",
"url": "https://orthotomeo.app/mcp"
}
}
} [mcp_servers.jrainsberger-orthotomeo] url = "https://orthotomeo.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jrainsberger-orthotomeo": {
"type": "remote",
"url": "https://orthotomeo.app/mcp",
"enabled": true
}
}
} openclaw mcp add jrainsberger-orthotomeo --url 'https://orthotomeo.app/mcp' --transport streamable-http
mcp_servers:
jrainsberger-orthotomeo:
url: "https://orthotomeo.app/mcp" {
"McpServers": {
"jrainsberger-orthotomeo": {
"Transport": "http",
"Url": "https://orthotomeo.app/mcp"
}
}
} assistant mcp add jrainsberger-orthotomeo -t streamable-http -u 'https://orthotomeo.app/mcp'
{
"mcpServers": {
"jrainsberger-orthotomeo": {
"type": "http",
"url": "https://orthotomeo.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://orthotomeo.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=orthotomeo.app | CN=WR3,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | RSA 2048 | SHA256-RSA | cf2ff6e194b6ec6b099a3ab6cf7770e5 |
| SANs: orthotomeo.app | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of orthotomeo.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| orthotomeo.app. | present | 1982 | 8 | Verified |
| orthotomeo.app. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; style-src 'self' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data:; object-src 'none'; base-uri 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://orthotomeo.app/mcp | Verified | 200 | |
| http (plaintext) | http://orthotomeo.app/mcp | HTTPS enforced | 302 | https://orthotomeo.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
attestation Manuscript attestation ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew) |
| chapter | integer | yes | chapter number |
| corpus | string | yes | word-tagged corpus: TAGNT, TAHOT, Swete, OSS-LXX-lemma |
| verse | integer | yes | verse number |
| word | null|integer | – | 1-based word_no within the verse; omit for every word in the verse |
| Name | Type | Req | Description |
|---|---|---|---|
| citations | null|array | yes | – |
| engine | string | yes | – |
| sources | object | – | – |
No examples provided.
cite Format citation ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| citations | array | yes | Citations previously returned by another tool call, to render as a pastable reference block |
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | yes | – |
| text | string | yes | – |
No examples provided.
concord_lemma Search concordance (lemma) ~254
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.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | 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 |
| corpus | string | yes | word-tagged corpus to search: TAGNT (Greek NT), TAHOT (Hebrew OT), Swete (LXX surface), OSS-LXX-lemma (LXX lemma) |
| query | string | yes | 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| citations | null|array | yes | – |
| engine | string | yes | – |
| sources | object | – | – |
No examples provided.
concord_phrase Search concordance (phrase) ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| corpus | string | yes | word-tagged corpus to search: TAGNT, TAHOT, Swete, OSS-LXX-lemma |
| tokens | array | yes | ordered lemma strings to find co-occurring within one verse, e.g. ["εἰς","ἄφεσις"] |
| window | integer | yes | max words allowed between consecutive tokens; 0 = strictly adjacent |
| Name | Type | Req | Description |
|---|---|---|---|
| citations | null|array | yes | – |
| engine | string | yes | – |
| sources | object | – | – |
No examples provided.
count Count occurrences ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | optional match column override: lemma, dstrong, or surface, same as concord_lemma |
| corpus | string | yes | word-tagged corpus: TAGNT, TAHOT, Swete, OSS-LXX-lemma |
| query | string | yes | a lemma, dStrong, or (with by="surface") exact inflected word, same as concord_lemma |
| Name | Type | Req | Description |
|---|---|---|---|
| by_book | object | yes | – |
| total | integer | yes | – |
No examples provided.
get_passage Get passage text ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew) |
| editions | array | yes | verse-text editions to fetch verbatim text from: KJV, ASV, WEB, BSB, Brenton |
| end_chapter | integer | yes | last chapter of the range, inclusive |
| end_verse | integer | yes | last verse of the range, inclusive |
| start_chapter | integer | yes | first chapter of the range, inclusive |
| start_verse | integer | yes | first verse of the range, inclusive |
| Name | Type | Req | Description |
|---|---|---|---|
| citations | null|array | yes | – |
| engine | string | yes | – |
| sources | object | – | – |
No examples provided.
get_verse Get verse text ~129
Returns verbatim verse text with provenance for one canonical reference, one Citation per requested edition (KJV, ASV, WEB, BSB, Brenton).
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew) |
| chapter | integer | yes | chapter number |
| editions | array | yes | verse-text editions to fetch verbatim text from: KJV, ASV, WEB, BSB, Brenton |
| verse | integer | yes | verse number |
| Name | Type | Req | Description |
|---|---|---|---|
| citations | null|array | yes | – |
| engine | string | yes | – |
| sources | object | – | – |
No examples provided.
interlinear Interlinear reading view ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew) |
| chapter | integer | yes | chapter number |
| corpus | string | yes | word-tagged corpus: TAGNT, TAHOT, Swete, OSS-LXX-lemma |
| verse | integer | yes | verse number |
| word | null|integer | – | 1-based word_no within the verse; omit for every word in the verse |
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | yes | – |
| sources | object | – | – |
| words | null|array | yes | – |
No examples provided.
lemmatize List lemmas ~113
Returns the ordered lemma list for a verse (words with no lemma are omitted, not fabricated).
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew) |
| chapter | integer | yes | chapter number |
| corpus | string | yes | word-tagged corpus: TAGNT, TAHOT, Swete, OSS-LXX-lemma |
| verse | integer | yes | verse number |
| Name | Type | Req | Description |
|---|---|---|---|
| citations | null|array | yes | – |
| engine | string | yes | – |
| sources | object | – | – |
No examples provided.
lexicon_lookup Lexicon lookup ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dstrong | string | yes | a disambiguated Strong's number, e.g. G0859, H7225G |
| Name | Type | Req | Description |
|---|---|---|---|
| definition | null|string | – | – |
| dstrong | string | yes | – |
| gloss | string | yes | – |
| language | string | yes | – |
| lemma | string | yes | – |
| translit | string | yes | – |
No examples provided.
parse Parse morphology ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew) |
| chapter | integer | yes | chapter number |
| corpus | string | yes | word-tagged corpus: TAGNT, TAHOT, Swete, OSS-LXX-lemma |
| verse | integer | yes | verse number |
| word | null|integer | – | 1-based word_no within the verse; omit for every word in the verse |
| Name | Type | Req | Description |
|---|---|---|---|
| citations | null|array | yes | – |
| engine | string | yes | – |
| sources | object | – | – |
No examples provided.
resolve_ref Resolve reference ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | USFM book code (e.g. GEN, PSA, MAT, REV) or the full English book name, any case (e.g. Genesis, matthew) |
| chapter | integer | yes | chapter number |
| verse | integer | yes | verse number |
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | null|array | yes | – |
| caveats | null|array | yes | – |
| ref | object | yes | – |
No examples provided.
What is the io.github.jrainsberger/orthotomeo MCP server?
io.github.jrainsberger/orthotomeo is an MCP server listed in the public MCP registry as io.github.jrainsberger/orthotomeo. Read-only scripture-study engine: complete-or-fail concordance over Greek NT, Hebrew OT, LXX. This page covers its hosted endpoint (https://orthotomeo.app/mcp).
Is the io.github.jrainsberger/orthotomeo MCP server safe to use?
io.github.jrainsberger/orthotomeo scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.jrainsberger/orthotomeo MCP server expose?
io.github.jrainsberger/orthotomeo exposes 12 tools: attestation, cite, concord_lemma, concord_phrase, count, and 7 more. Their descriptions and schemas cost roughly 1,920 tokens of context every time the server is loaded.
Does the io.github.jrainsberger/orthotomeo MCP server require authentication?
No. We connected to io.github.jrainsberger/orthotomeo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.jrainsberger/orthotomeo MCP server still maintained?
io.github.jrainsberger/orthotomeo is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.