Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Bible research: 59 translations, Hebrew/Greek Strong's, morphology, cross-refs, 13 dictionaries
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://darash-api.publifye.com/mcp在终端中运行这条命令
claude mcp add --transport http darash https://darash-api.publifye.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"darash": {
"url": "https://darash-api.publifye.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"darash": {
"type": "http",
"url": "https://darash-api.publifye.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://darash-api.publifye.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 publifye.pro 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.3)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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) |
{ "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](../../docs/connect.md).
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.
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.
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](tools/text.md) | Which verse, chapter or book does the text actually contain, and how do translations differ? | 11 |
| [Hebrew and Greek](tools/original-language.md) | What is this word, grammatically and lexically — voice, person, stem, lemma, and what the lexicons say? | 9 |
| [Study and cross-reference](tools/study.md) | What else does Scripture say about this, and which words move together? | 6 |
| [Dictionaries](tools/dictionaries.md) | What do the reference works say, and which work is it? | 4 |
| [Search](tools/search.md) | Find it by wording, by meaning, or by how rare it is. | 4 |
| [Session, figures and health](tools/session.md) | How do I check the service, send feedback, and manage the figures I have stored? | 8 |
Machine-readable: [tools.json](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.md](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.
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.
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](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.
Published, each also in Norwegian, Spanish, Chinese and Korean: