Saba Bible MCP
NPM · SABA-BIBLE-MCP
Install Saba's open Bible library, search it, and read scripture.
Available components
Last scanned (22 hours ago)
Scores higher than 49% of npm servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 53 of 176 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 44 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1112 tokens (~123/item across 9 items; 9 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Nov 26 −1
- Stability: pass → 0.93 functional
- 14 Nov 26 0
- Stability: 0.97 → pass security
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Analysed npm/saba-bible-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-f88m-g3jw-g9cj | CVE-2026-114113 | high | yes | |
| GHSA-rgj7-g3m4-5g8c | CVE-2026-114112 | high | yes | |
| GHSA-wq5f-xc86-pv6w | CVE-2026-114111 | high | yes | |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 176 packages
| Packages resolved | 176 |
|---|---|
| Deprecated | 1 |
| Stale | 53 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_index ~48
Check whether topic search is downloaded and usable. Use this when someone asks if search is set up. Not downloaded is a normal answer, not an error -- then install ["search-en-ult"].
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
download_ipns ~74
Download a copyrighted Bible (ESV, NIV, and the like) from the address the user gave. Ask for that address if they didn't give one -- don't invent it.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The address the user provided, such as ipns/…/file.zip or a content.saba.bible path |
No output schema declared.
No examples provided.
install ~101
Download free Bibles, notes, and the ULT search index onto this computer. Call this before the first read or search. Leave ids off, or pass ["all"], to get everything that is free. Does not download ESV, NIV, or other copyrighted Bibles -- those need download_ipns and an address from the user.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | Ids from list_resources. Leave off or pass ["all"] for everything free, including search |
No output schema declared.
No examples provided.
list_resources ~79
Show what's available (Bibles, notes, dictionaries, grammars, books, stories, reading plans, and search) and whether each is already downloaded. Use this to pick an id. You can read Bibles and verse notes; dictionaries, grammars, books, and stories are listed only. To see if search is ready, call check_index.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read ~147
Read Bible verses as plain text. Each line starts with the reference (JHN 11:35 Jesus wept). Say which Bible. Don't use this for commentary -- that is read_commentary. If a reading plan gave only a chapter, start at verse 1.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | Bible book, like John or JHN |
| chapter | integer | yes | Starting chapter |
| end | object | – | Last verse to include, same book. Leave off to read just the starting verse |
| resource | string | yes | Which Bible, like en_ult. Not a commentary id |
| verse | integer | yes | Starting verse. Use 1 if you only know the chapter |
No output schema declared.
No examples provided.
read_commentary ~163
Read notes on a verse -- Translation Notes, Matthew Henry, Calvin, and similar. Use this for "what does Matthew Henry say" or "notes on John 3:16". Returns matching notes, or none if there are not any. For the Bible text itself, use read.
| Name | Type | Req | Description |
|---|---|---|---|
| book | string | yes | Bible book, like John or JHN |
| chapter | integer | yes | Starting chapter |
| end | object | – | Last verse to include, same book. Leave off to read just the starting verse |
| resource | string | yes | Which notes, like en_tn (Translation Notes) or en_mhc (Matthew Henry). Not a Bible id |
| verse | integer | yes | Starting verse. Use 1 if you only know the chapter |
No output schema declared.
No examples provided.
reading_plan ~117
Today's reading from a plan like M'Cheyne: which passages, not the Bible text. Then call read on a Bible for each passage. If a passage is a whole chapter, read from verse 1.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | – | Plan day number. Leave off for today |
| resource | string | yes | Which plan, like plan/mcheyne |
| startDate | string | – | The day they started, YYYY-MM-DD. Leave off to reuse the saved date, or January 1 of this year if none is saved |
No output schema declared.
No examples provided.
search_lexical ~122
Find verses that contain these exact words. Use this for a quote or a specific phrase, like "Jesus wept". Defaults to ULT if it is downloaded, otherwise the first downloaded Bible. Works even when topic search is not set up.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many verses to return, 1-50. Default 20 |
| query | string | yes | Exact words to find, like Jesus wept |
| resource | string | – | Which Bible, like en_ult. Leave off to use ULT or the first downloaded Bible |
No output schema declared.
No examples provided.
search_vector ~120
Find verses about a topic or idea in the Literal Text (ULT). BM25 keyword + Granite vectors, fused with RRF. Use this for "verses about hope" or "spirit hover". For an exact substring, search_lexical. If search is not downloaded this errors; then install ["search-en-ult"] or use search_lexical.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many verses to return, 1-50. Default 20 |
| query | string | yes | Topic or question, like God comforting those who mourn |
No output schema declared.
No examples provided.
How do I install the Saba Bible MCP server?
Saba Bible MCP runs locally as an npm package, launched with npx -y saba-bible-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · saba-bible-mcp
claude mcp add jra-zachpennington-saba -- npx -y saba-bible-mcp
What is the Saba Bible MCP server?
Saba Bible MCP is listed in the public MCP registry as io.github.JRA-zachpennington/saba. Install Saba's open Bible library, search it, and read scripture. This page covers its npm package (saba-bible-mcp).
Is the Saba Bible MCP server safe to use?
Saba Bible MCP scores 74 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. 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 Saba Bible MCP server expose?
Saba Bible MCP exposes 9 tools: list_resources, install, download_ipns, check_index, search_vector, and 4 more. Their descriptions and schemas cost roughly 971 tokens of context every time the server is loaded.
Is the Saba Bible MCP server still maintained?
Saba Bible MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Saba Bible MCP server under?
Saba Bible MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Saba Bible MCP server?
VerifyMCP ran 15 checks on Saba Bible MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Saba Bible MCP: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.