World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Read-only scripture-study engine: complete-or-fail concordance over Greek NT, Hebrew OT, LXX.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 3/12 | Full marks for a release or code change within 30 days |
| Still answering | 8/8 | The cloud endpoint answered at the last check |
| Usage score | 11/100 |
Quality: Passed 5/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Orthotomeo. Follow https://mcp.popnx.com/i/jrainsberger-orthotomeo.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 5/5 checks · What you ask goes through the maker’s server (orthotomeo.app) · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Orthotomeohttps://orthotomeo.app/mcpClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsOrthotomeo
Use Orthotomeo and tell me what you can do for me, then show me one thing✓ If Claude says it is using Orthotomeo or shows a Orthotomeo tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Orthotomeohttps://orthotomeo.app/mcpStart a new chat and pick Orthotomeo from your plugins before typing
Use Orthotomeo and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Orthotomeo or shows a Orthotomeo tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user orthotomeo https://orthotomeo.app/mcpYou should see Orthotomeo listed as connected
Use Orthotomeo and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Orthotomeo or shows a Orthotomeo tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use Orthotomeo and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Orthotomeo or shows a Orthotomeo tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use Orthotomeo and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Orthotomeo or shows a Orthotomeo tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://orthotomeo.app/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user orthotomeo https://orthotomeo.app/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"orthotomeo": {
"url": "https://orthotomeo.app/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"orthotomeo": {
"type": "http",
"url": "https://orthotomeo.app/mcp"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Tool names and descriptions exactly as the server reported them on Nov 16, 2026. The maker wrote them, not us; we show them as plain text.
attestationReturns 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.
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.
concord_lemmaComplete-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 o
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 = strictly adjacent). This is the tool for a phrase query like εἰς ἄφεσιν. This deployment caps one co
countOccurrence 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.
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.
get_verseReturns verbatim verse text with provenance for one canonical reference, one Citation per requested edition (KJV, ASV, WEB, BSB, Brenton).
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 attestation stacked per word - the composed display shape for a study reading view, built on parse and
lemmatizeReturns the ordered lemma list for a verse (words with no lemma are omitted, not fabricated).
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, Public Domain). A Hebrew entry's definition field is always omitted: it is abridged BDB via Online Bible,
parseReturns 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.
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. Cross-edition divergence (a T4b merge/renumber/divide, or a reference simply missing from an edition) i
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account jrainsberger, which owns the repo
Code last changed 4 months ago
Uses MIT
Responded in 309 ms (HTTP 200)
No sign-in needed
Read 12 tool descriptions and found no hidden instructions to the AI
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/jrainsberger-orthotomeo)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 4 months ago, and the latest version (0.1.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Orthotomeo | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
ὀρθοτομέω — "to cut straight," from 2 Timothy 2:15: *"Be diligent to present yourself approved to God, a worker who does not need to be ashamed, cutting straight the word of truth."*
orthotomeo is a read-only scripture-study engine. It imports a multi-edition biblical corpus (Greek New Testament, Hebrew Old Testament, Septuagint, and public-domain English translations) into a derived SQLite database, then serves verbatim, provenance-tagged lookups and complete-or-fail concordance over it - through an MCP server, a CLI, or as a Go library.
*A personal project by Justin Rainsberger - not affiliated with, sponsored by, or representing any employer.*
Three texts shape the engine's design, not just its name:
Practically, this means: the engine owns evidence, the LLM traces usage, you own the conclusions. The engine never interprets, never argues a position, and never quotes original-language text it didn't get from its own database. Given a query, it either returns the complete, provenance-tagged result set, or it raises an error - it does not silently truncate, guess, or paraphrase. The LLM fans that out into patterns across occurrences; it never gets the last word on what they mean.
cmd/build) - a regenerable artifact, not checked in. The corpus files are the source of truth; the DB is just an index over them.cmd/orthotomeo-mcp) for use from an LLM chat client, a CLI (cmd/orthotomeo) for terminal use, an HTTP API + local web UI (httpapi, served by cmd/orthotomeo-web), a desktop launcher (cmd/orthotomeo-desktop) that starts the web server and opens a browser to it, and the engine package itself if you want to embed it directly in Go.See docs/PLAN.md for the full design (read its cross-cutting invariants first) and docs/erd-v1.svg for the data model. docs/STATUS.md has the detailed ticket-by-ticket build log.
Paired with an LLM, this small local reference engine stops being something you flip through by hand: ask a follow-up in plain language, and the model fans that into the right tool calls and finds patterns across the results - the cross-referencing a printed concordance leaves entirely to you. The engine still owns the text; the LLM adds the conversational follow-through, never the text itself. See the worked example below.
*(Evaluating the project rather than installing it? Skip ahead to the worked example and come back to this later.)*
This repo does not ship the corpus. The source files are external inputs you supply yourself - each is separately licensed, and cmd/build refuses to run without both roots explicitly given (no default path). What you need:
| Edition | What it is | Format | License / attribution |
|---|---|---|---|
| TAGNT | Translators Amalgamated Greek New Testament | tab-delimited TSV, one row per Greek word (lemma, disambiguated Strong's, morphology, manuscript attestation) | CC BY 4.0, STEPBible.org / Tyndale House Cambridge |
| TAHOT | Translators Amalgamated Hebrew Old Testament | same TSV shape, Hebrew/Aramaic | CC BY 4.0, STEPBible.org / Tyndale House Cambridge |
| TEGMC / TEHMC | Greek/Hebrew morphology-code expansion tables | plain TSV | CC BY 4.0, STEPBible.org / Tyndale House Cambridge |
| TBESG / TBESH | Brief lexicon of Extended Strong's (Greek/Hebrew) | plain TSV | CC BY 4.0 (Hebrew definitions require checking terms before use - see sources/sources.json) |
| Swete | Swete's 1909-1930 Cambridge Septuagint, Greek surface text | CSV | Public Domain, via archive.org |
| OSS-LXX-lemma | Open Scriptures LXX lemma index | JS files, one per book, {key, lemma} per word | CC BY 4.0, Open Scriptures |
| KJV / ASV | King James (1769) / American Standard (1901) | single JSON file, books[].chapters[].verses[] | Public Domain |
| WEB | World English Bible (2024) | USFM, one file per book, Strong's numbers inline | Public Domain, eBible.org |
| BSB | Berean Standard Bible - a modern, literal translation from the critical text | USFM, one file per book | Public Domain (released 2023-04-30), Bible Hub / Berean Bible |
| Brenton | Brenton's 1851 English Septuagint | HTML, one file per chapter | Public Domain |
| OpenBible-xref | Cross-references (from the Treasury of Scripture Knowledge) | TSV | CC BY 4.0, OpenBible.info |
The authoritative list - exact source_file glob, format, license, and attribution for every source - is checked in at sources/sources.json; treat that file as ground truth over this table.
Each edition keeps its own versification and canon (the LXX numbers Psalms differently and includes deuterocanonical books; the five text traditions disagree on where some verses start). The engine never assumes a 1:1 mapping across editions - see PLAN.md's cross-cutting invariant #4.
Directory layout `cmd/build` expects, split across two roots:
| Root | Contains |
|---|---|
--reference | STEPBible-Data/ (TAGNT, TAHOT, lexicons, morphology codes), LXX-Swete-1930/ |
--corpus | bible-text/ (KJV, ASV, WEB, BSB, Brenton, OSS-LXX-lemma), cross_references.txt |
The exact path under each root is not configurable per run - it's fixed, per source, in sources/sources.json's source_file field, the one place this mapping lives (no loader hard-codes a path itself; corpus.Locate is the only path-aware code in the whole importer, and it just joins root + source_file and globs). --corpus and --reference are tried in that order per source, so a tree can live under either root - but the path segments below whichever root resolves it are literal, not patterns (only the filename portion is a glob, where shown below):
| Source | Path under its root |
|---|---|
| KJV | bible-text/KJV/KJV.json |
| ASV | bible-text/ASV/ASV.json |
| WEB | bible-text/WEB/*.usfm |
| BSB | bible-text/BSB/*.usfm |
| Brenton | bible-text/LXX/eng-Brenton_html/*.htm |
| OSS-LXX-lemma | bible-text/LXX/GreekResources-master/LxxLemmas/*.js |
| TAGNT | STEPBible-Data/Translators Amalgamated OT+NT/TAGNT*.txt |
| TAHOT | STEPBible-Data/Translators Amalgamated OT+NT/TAHOT*.txt |
| TBESG / TBESH | STEPBible-Data/Lexicons/TBESG*.txt / TBESH*.txt |
| TEGMC / TEHMC | STEPBible-Data/Morphology codes/TEGMC*.txt / TEHMC*.txt |
| TVTMS | STEPBible-Data/Versification/TVTMS*.txt |
| Swete | LXX-Swete-1930/*.csv |
| OpenBible-xref | cross_references.txt |
Placing files anywhere else fails fast with corpus tree missing: under [...], naming exactly what it looked for. To use a different layout, edit the source_file value in sources/sources.json - that's the only change needed, since every loader reads it from there rather than assuming a path.
STEPBible-Data is published by STEPBible.org / Tyndale House Cambridge; the Swete CSV is the archive.org digitization of the 1930 Cambridge edition; the public-domain English translations and Open Scriptures lemma files are available from their respective publishers (eBible.org, Open Scriptures). None of these are fetched automatically yet - sources/sources.json's fetch_url field is a placeholder for that, not yet built.
Every parse/attestation/interlinear result carries two fields worth knowing how to read: attestation (the Type code, e.g. "NKO") and manuscripts (the specific published editions, e.g. "NA28+NA27+Tyn+SBL+WH+Treg+TR+Byz"). Both are reported as neutral text-critical data, per this project's own discipline (see Design principles) - never an argument for or against a reading.
This legend is TAGNT (Greek NT) specific - straight from TAGNT's own source