orthotomeo MCP server
io.github.jrainsberger/orthotomeojrainsbergerstreamable-httpv0.1.0Scanned
Read-only scripture-study engine: complete-or-fail concordance over Greek NT, Hebrew OT, LXX.
12 tools: 3 change things and 9 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the orthotomeo MCP server can do
The orthotomeo MCP server is published by the GitHub account jrainsberger. It has 12 tools. It can create or change data (3 tools: cite, concord_lemma and concord_phrase), but cannot delete data. 9 tools only read.
1 tool reads private data (parse); 2 tools bring in text other people can write (get_verse and resolve_ref).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Changes things 3Claude Code: ask
citeRenders 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
concord_lemmaComplete-or-fail concordance: every words row in corpus whose lemma, dStrong, or (with by="surface") exact inflected surface form matches query.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
concord_phraseComplete-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 = …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
Only reads 9Show 9 read-only tools
attestationReturns the WHNT-style Type/Editions manuscript-tradition columns as neutral text-critical data (e.g.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
countOccurrence tally (total + per-book breakdown) for the identical query concord_lemma would match.No findings
Why it is in this group
- The name "count" says "count": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
get_passageReturns get_verse's result for every canonical verse in a contiguous, single-book range, in order - verse boundaries preserved, never concatenated into one blob.No findings
Why it is in this group
- The name "get_passage" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
get_verseReturns verbatim verse text with provenance for one canonical reference, one Citation per requested edition (KJV, ASV, WEB, BSB, Brenton).Reads text others writeNo findings
Why it is in this group
- The name "get_verse" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "return" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it Returns verbatim verse text with provenance for one canonical reference, one Citation per requested edition (KJV, ASV, WEB, BSB, Brenton).
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
interlinearReturns 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 at…No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
lemmatizeReturns the ordered lemma list for a verse (words with no lemma are omitted, not fabricated).No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Returns the ordered lemma list for a verse (words with no lemma are omitted, not fabricated).
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
lexicon_lookupResolves 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, Publi…No findings
Why it is in this group
- The name "lexicon_lookup" says "lookup": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
parseReturns dStrong + expanded morphology (via the T6 morph_codes table) for every word in a verse, or one word if word is given.Reads private dataNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "table": it reads databases.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
resolve_refReports, 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.Reads text others writeNo findings
Why it is in this group
- The name "resolve_ref" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "web": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:06 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://orthotomeo.app/mcp: tools/list returned 12 tools to an anonymous client, including cite (write), concord_lemma (write), concord_phrase (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http orthotomeo https://orthotomeo.app/mcpclaude mcp add --transport http orthotomeo https://orthotomeo.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__orthotomeo__attestation",
"mcp__orthotomeo__count",
"mcp__orthotomeo__get_passage",
"mcp__orthotomeo__get_verse",
"mcp__orthotomeo__interlinear",
"mcp__orthotomeo__lemmatize",
"mcp__orthotomeo__lexicon_lookup",
"mcp__orthotomeo__parse",
"mcp__orthotomeo__resolve_ref"
],
"ask": [
"mcp__orthotomeo__cite",
"mcp__orthotomeo__concord_lemma",
"mcp__orthotomeo__concord_phrase"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as orthotomeo. Review it before you use it.
Capability tags behind 3 rules
- mcp__orthotomeo__get_verse untrusted-input
- mcp__orthotomeo__parse private-data
- mcp__orthotomeo__resolve_ref untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.jrainsberger/orthotomeo/verify?hash=3fa5a9a3cc97fc3a9498bd9abc16aa05bc44edadee33bab3076ac2167e92e8ec" | jq -e '.changed == false'Pinned hash 3fa5a9a3cc97, from Nov 19, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.jrainsberger/orthotomeo/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.jrainsberger/orthotomeo)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:37 UTC.
orthotomeo MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the orthotomeo MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the orthotomeo MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the orthotomeo MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the orthotomeo MCP server have?
- 12 tools: 3 write, 9 read. cite, concord_lemma, concord_phrase, attestation, count, get_passage, get_verse, interlinear and 4 more.
Does the orthotomeo MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the orthotomeo MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the orthotomeo MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.