Bereishes
REMOTE · BEREISHES.COM
Search and read classical Jewish texts: Tanach, Talmud, Midrash, halacha, and commentaries.
Available components
Last scanned (7 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 756 tokens (~189/item across 4 items; 4 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 Management10
- Stability observed for 3 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 74
First indexed and scored.
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 5 Nov 2026 · Probed https://bereishes.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bereishes.com | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7eeb8fd9cdfe597813dd56519d8c1fc2 |
| SANs: bereishes.com, *.bereishes.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bereishes.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| bereishes.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://us.i.posthog.com https://us-assets.i.posthog.com https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' https: data:; connect-src 'self' https://www.sefaria.org https://sefaria.org https://generativelanguage.googleapis.com https://us.i.posthog.com https://us-assets.i.posthog.com; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bereishes.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://bereishes.com/api/mcp | HTTPS enforced | 301 | https://bereishes.com/api/mcp |
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 →
fetch_commentary Read commentary on a passage ~107
Returns the commentary on a verse or passage (Rashi, Ramban, Ibn Ezra, Sforno and others), in each commentator's own words, with links. Can be limited to named commentators.
| Name | Type | Req | Description |
|---|---|---|---|
| commentators | array | – | Optional list of commentator names to filter by, e.g. ['Rashi','Ramban']. If omitted, returns all commentary. |
| limit | integer | – | Max commentary entries (default 8). |
| ref | string | yes | Canonical ref. |
No output schema declared.
No examples provided.
fetch_text Read Bereishes texts ~140
Returns the full Hebrew and English text of one canonical ref, or of up to 10 refs, with links. A range such as 'Shabbat 21b:5-11' works. Text is cut at about 3000 characters per language for one ref (1500 when several are read) and marked [TRUNCATED].
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | – | Canonical ref, e.g. 'Genesis 1:1' or 'Shulchan Arukh, Orach Chayim 75:1'. |
| refs | array | – | Several canonical refs to read in one call (max 10). Use instead of `ref`. |
No output schema declared.
No examples provided.
resolve_ref Resolve a reference ~59
Turns a natural-language reference ('Rambam Teshuvah 2', 'Hilchot Shabbat ch. 5') into the library's canonical ref, or returns suggested completions.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Natural-language ref or phrase. |
No output schema declared.
No examples provided.
semantic_search Search the Bereishes library ~170
Searches the library by meaning. Returns ranked passage snippets (the ref and its first ~180 characters) with links. Snippets are short excerpts, not full passages. Optional hebrew_terms rank passages that contain those Hebrew words higher.
| Name | Type | Req | Description |
|---|---|---|---|
| hebrew_terms | array | – | The key Jewish terms of the query in Hebrew script, e.g. ["בריאת העולם", "תכלית"] for "why did God create the world". Passages that contain these words rank higher. |
| limit | integer | – | Max results (default 8, max 15). |
| query | string | yes | Natural-language search query. |
| ref_prefix | string | – | Optional: restrict results to a ref prefix — a section ('Genesis 1') or a book title ('Tanya', 'Mishnah Berurah'). |
No output schema declared.
No examples provided.
How do I install the Bereishes MCP server?
Bereishes is a hosted endpoint at https://bereishes.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bereishes.com
claude mcp add --transport http com-bereishes-bereishes 'https://bereishes.com/api/mcp'
What is the Bereishes MCP server?
Bereishes is an MCP server listed in the public MCP registry as com.bereishes/bereishes. Search and read classical Jewish texts: Tanach, Talmud, Midrash, halacha, and commentaries. This page covers its hosted endpoint (https://bereishes.com/api/mcp).
Is the Bereishes MCP server safe to use?
Bereishes scores 76 out of 100 on VerifyMCP. 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 Bereishes MCP server expose?
Bereishes exposes 4 tools: semantic_search, fetch_text, fetch_commentary, resolve_ref. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.
Does the Bereishes MCP server require authentication?
No. We connected to Bereishes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Bereishes MCP server still maintained?
Bereishes is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.