Darash MCP server
Commit Oct 11, 2026Provides an AI assistant with structured Hebrew and Greek biblical text, morphology, Strong's numbers, and extensive lexicon data.
Also known as Publifye/mcp
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.3
- Last commit
- Oct 11, 2026
- License
- CC-BY-4.0
What is Darash MCP?
Darash provides an AI assistant with structured Hebrew and Greek biblical text, morphology, Strong's numbers, and extensive lexicon data.
Summary generated from the project's README
About Darash MCP server
Darash provides AI assistants with structured biblical data for deep linguistic study. It offers access to Hebrew and Greek texts, including the Leningrad Codex and the Byzantine Majority, alongside morphological parsing that identifies the specific voice, person, and stem of a verb. This allows users to move beyond English translations to understand the original grammatical intent of the scripture.
The server operates as a hosted service over HTTPS using streamable HTTP, requiring either OAuth 2.1 with PKCE or an API key for connection. It includes 34 capability tools that cover reading text, original language analysis, cross-references, and dictionary searches. Users can access extensive lexicon data from sources like BDB, LSJ, and Abbott-Smith, with detailed provenance information for every entry.
Developers can use this with any MCP client such as Claude or Cursor. For institutions requiring complete privacy, a self-contained 205 MB binary is available for offline use. This version includes specialized research tools like ELS and Torah-code that are not available in the hosted plans.
What you can do with it
- 1Analyze original verb grammarAsk the AI to determine the specific voice, person, and stem of a Greek verb to avoid translation bias.
- 2Verify lemma presenceConfirm if a specific Strong's number or lemma is actually present within a specific verse.
- 3Consult historical lexiconsRetrieve definitions and linguistic insights from specific 19th-century dictionaries.
- 4Perform linguistic searchesFind specific biblical passages based on word rarity, meaning, or exact wording.
Written from the project's README. Every use case is checked against a quote from it.
How to install Darash MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Darash MCP in Claude Code
$ claude mcp add --transport http darash https://darash-api.publifye.com/mcpInstall Darash MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"darash": {
"url": "https://darash-api.publifye.com/mcp"
}
}
}Install Darash MCP in VS Code
.vscode/mcp.json
{
"servers": {
"darash": {
"type": "http",
"url": "https://darash-api.publifye.com/mcp"
}
}
}Install Darash MCP in VS Code CLI
$ code --add-mcp '{"name":"darash","type":"http","url":"https://darash-api.publifye.com/mcp"}'Install Darash MCP in Codex
$ codex mcp add darash --url https://darash-api.publifye.com/mcpInstall Darash MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.darash] url = "https://darash-api.publifye.com/mcp"
Install Darash MCP in Gemini CLI
$ gemini mcp add -s user --transport http darash https://darash-api.publifye.com/mcpInstall Darash MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"darash": {
"url": "https://darash-api.publifye.com/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablepublifye/mcp is public and reachablegithub.com/publifye/mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)CC-BY-4.0 is not OSI-approvedspdx.org/licenses/CC-BY-4.0.html ↗Finding
- Commit or release in the last yearLast commit or release 2026-10-11github.com/publifye/mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubDarash — Bible research MCP server for Claude, Cursor and any MCP client
Darash gives an AI assistant the Hebrew and Greek text of Scripture as structured data: which stem a verb is in, which Strong's numbers actually occur in a verse, what a named 19th-century lexicon says about a lemma, and which printed edition that lexicon came from. It runs as a hosted MCP server over HTTPS — there is nothing to install.
| Endpoint | https://darash-api.publifye.com/mcp |
| Transport | Streamable HTTP |
| Auth | OAuth 2.1 + PKCE (S256), DCR open · or X-API-Key |
| Registry | pro.publifye/darash (server.json) |
| Product site | https://darash.publifye.com |
| What it solves | https://publifye.com/darash |
| Capability tools | 34 (full schemas) |
Connect
{ "mcpServers": { "darash": { "type": "http", "url": "https://darash-api.publifye.com/mcp" } } }
The OAuth flow runs in the browser on first use. Full detail, including the API-key route and the discovery chain: ../../docs/connect.md.
The corpus
Measured on the live service, 2026-09-13, via get_health:
| Translations | 59, across 36 languages |
| Verses indexed | 2,142,531 |
| Cross-references | 446,544 |
| Hebrew lexicon entries | 8,674 |
| Greek lexicon entries | 5,523 |
| Dictionary entries | 217,352, across 13 dictionaries |
| Morphologically parsed verses | 31,167 |
| Koren Torah letters | 304,805 |
Included among the 59: the Leningrad Codex (wlc) and the Byzantine Majority Greek text.
Strong's is augmented with the full Abbott-Smith, LSJ and BDB.
Why a translation is not enough
A Greek verb in the active voice can be rendered perfectly naturally in the passive in English. An argument about who is acting on whom, built on that English passive, is an argument about the translator rather than about the text.
get_morphology returns the voice, person and stem the text actually carries. strongs_in_verse
proves a lemma is genuinely in a verse rather than merely adjacent to it in a concordance. That
distinction is the whole reason this server exists.
What the tools do
Every tool is documented with its exact description, annotations and input schema —
42 in all (34 capability, 8 session and figure tools), generated from the service's own tools/list, never written by hand.
| Area | The question it answers | Tools |
|---|---|---|
| Reading the text | Which verse, chapter or book does the text actually contain, and how do translations differ? | 11 |
| Hebrew and Greek | What is this word, grammatically and lexically — voice, person, stem, lemma, and what the lexicons say? | 9 |
| Study and cross-reference | What else does Scripture say about this, and which words move together? | 6 |
| Dictionaries | What do the reference works say, and which work is it? | 4 |
| Search | Find it by wording, by meaning, or by how rare it is. | 4 |
| Session, figures and health | How do I check the service, send feedback, and manage the figures I have stored? | 8 |
Machine-readable: tools.json carries all 42 callable tools (34 capability, 8 session/cache) with full JSON Schema, plus every excluded bucket listed by name so the count is auditable.
Provenance — read this before you trust a gloss
PROVENANCE.md records, for every dictionary and both Strong's lexicons: the printed work, the edition, how the text reached us, the licence, and what is not established.
One dictionary is marked verified — collated against the printed edition it claims to be. The
rest are marked conventional, meaning the title and author are as distributed and have not been
collated. Most vendors in this space ship the same public-domain texts and do not draw that
distinction. We draw it because a reader deciding how much weight a gloss can carry needs it.
The file also carries a corrections section. In September 2026 we found that a dictionary served
under the key thayer was not Thayer; it was archived with a digest and replaced with a
transcription of the 1889 Corrected Edition read from page images — 716 body pages, two independent
passes collated at 98.91% agreement over 856,793 tokens, with ambiguous headwords refusing to
resolve rather than guessing. The provenance work is what found the error. That is the argument
for publishing it.
Self-hosting
Darash also ships as a single self-contained binary of roughly 205 MB, carrying CLI, HTTP API and MCP server together, running fully offline with no network call at any point. For institutions whose material cannot leave the building, that is usually the only workable shape. Licensed by quote — see the product site.
The ELS / Torah-code research tools are part of the self-hosted Engine only. They are not in the hosted plans, are not listed in tools.json, and are enforced server-side rather than merely hidden.
Plans
Three ways in — a personal key for any MCP client, an always-on agent, and a self-hosted or managed licence by quote. There is a free trial. Current plans and prices are on https://darash.publifye.com, which is the only place they are authoritative; they are deliberately not duplicated here, because a price in a repository is a price that goes stale.
Written about this work
Published, each also in Norwegian, Spanish, Chinese and Korean:
- Thayer's Greek Lexicon, rebuilt from the 1889 page scans — 716 pages, four transcription routes, five rounds of adversarial review, and why every open digital Thayer we could find is lossy.
- Darash vs Logos, Accordance and Blue Letter Bible (2026) — an honest comparison — including where the big platforms win.
- Deuteronomy 4:29 says "seek" twice. The Hebrew does not. — a worked example, including the searches that prove nothing.
- Why do AI models hallucinate — and does grounding them in real sources fix it?
- Best Bible study tools in order: what to use first, and when Hebrew and Greek pay off
- Bibelen Anno 2026 — a Norwegian translation built with AI, eight verse gates and a human veto
Darash MCP questions
How do I add Darash MCP to Claude Code?
Run claude mcp add --transport http darash https://darash-api.publifye.com/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Darash MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I connect to the Darash MCP server?
You can connect via a hosted HTTP endpoint using the provided JSON configuration for your MCP client.
Does Darash require installation?
No, it runs as a hosted MCP server over HTTPS, so there is nothing to install.
Can I run Darash offline?
Yes, Darash is available as a self-contained binary that runs fully offline for institutions requiring local data.
What kind of authentication does it use?
The server supports OAuth 2.1 with PKCE or X-API-Key authentication.