Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

HebrewCore by baba Hebrew

REMOTE · HC.ITSBABA.COM · SCANNED OCT 1

Hebrew translation that keeps prices, names and dates exact, RTL display, nikud, clinical Hebrew.

Available components

60 Trust /100
Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5021 tokens (~313/item across 16 items; 16 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 Management20
  • Stability observed for 6 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
  • 99% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety88
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "strip_nikud" implies "remove" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the HebrewCore by baba Hebrew MCP server?

HebrewCore by baba Hebrew is a hosted endpoint at https://hc.itsbaba.com/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 · hc.itsbaba.com

# add to Claude Code
claude mcp add --transport http com-itsbaba-hebrewcore 'https://hc.itsbaba.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-itsbaba-hebrewcore": {
      "url": "https://hc.itsbaba.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-itsbaba-hebrewcore": {
      "type": "http",
      "url": "https://hc.itsbaba.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-itsbaba-hebrewcore]
url = "https://hc.itsbaba.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-itsbaba-hebrewcore": {
      "type": "remote",
      "url": "https://hc.itsbaba.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-itsbaba-hebrewcore --url 'https://hc.itsbaba.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-itsbaba-hebrewcore:
    url: "https://hc.itsbaba.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-itsbaba-hebrewcore": {
      "Transport": "http",
      "Url": "https://hc.itsbaba.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-itsbaba-hebrewcore -t streamable-http -u 'https://hc.itsbaba.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-itsbaba-hebrewcore": {
      "type": "http",
      "url": "https://hc.itsbaba.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 1 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “clinical_query” rewrote its description, which is the text the model reads security
    • Tool “clinical_translate” rewrote its description, which is the text the model reads security
    • Tool “clinical_verify” rewrote its description, which is the text the model reads security
  • 26 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 25 Sept 26 57

    First indexed and scored.

Diagnostics

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 1 Oct 2026 · Probed https://hc.itsbaba.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=itsbaba.com CN=WE1,O=Google Trust Services,C=US 21 Aug 2026 19 Nov 2026 ECDSA 256 ECDSA-SHA256 2f3496c769a66fb9131feef0315622d1
SANs: itsbaba.com, hc.itsbaba.com, *.hc.itsbaba.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 hc.itsbaba.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
itsbaba.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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://hc.itsbaba.com/mcp Verified 200
http (plaintext) http://hc.itsbaba.com/mcp Inconclusive 405
MCP tools · 16 exposed · ~4,587 tokens

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 →

Tool Tokens
add_nikud ~123

Add full nikud (vowel points) to Hebrew text, for learners, vocalized display and text-to-speech, where unvocalized Hebrew is ambiguous. English terms and numbers pass through unchanged. The result is verified: `verified: true` means removing the points gives back the input; when false, `nikud` is the input unchanged. Up to 10,000 characters. Uses the monthly character quota.

NameTypeReqDescription
textstringyesHebrew text to vocalize, up to 10,000 characters. English terms and numbers pass through.
NameTypeReqDescription
nikudstring–The vocalized text, or the input unchanged when `verified` is false.
textstring–The input.
verifiedboolean–True when removing the points gives back exactly the input. When false, `nikud` is the input unchanged: send it to speech unvocalized or retry.

No examples provided.

add_terms ~119

Add protected terms to the account, or update existing ones (matched by exact term text). Every later protected translation on the account (translate, translate_batch and the clinical tools) keeps these terms exactly as written, or uses `translations.he` / `.en` / `.ru` for that target language when set. Sending a term that already exists replaces its translations and note. Up to 2,000 terms per account, each up to 200 characters. Changes apply to new requests within 30 seconds. Free.

NameTypeReqDescription
termsarrayyes–
NameTypeReqDescription
countinteger––
termsarray––

No examples provided.

analyze_direction ~216

Resolve the right-to-left / left-to-right structure of mixed Hebrew text: base direction, whether it mixes directions, dominant language and script, and the runs to render, where every left-to-right unit (a Latin term, a price, a range such as 10–20%, a date, a model number) stays whole. Send one `text`, or `fields` (a map of name → string, up to 100) to analyze a whole record at once. `base`: `auto` (default), `ltr` or `rtl`. Deterministic and free: no model, no character quota.

NameTypeReqDescription
basestring–Paragraph direction to resolve against. `auto` (default) uses the first strong letter.
fieldsobject–A map of field name → string, up to 100 fields and 20,000 characters in total. Send this or `text`.
textstring–A single string, up to 20,000 characters. Send this or `fields`.
NameTypeReqDescription
analysis–––
fieldsobject–Present when the request sent `fields`: one analysis per field name.

No examples provided.

clinical_query ~156

Turn a Hebrew clinical question (up to 2,000 characters) into an English query for a record search or an English model. English terms, numbers and dates are kept exactly, and Hebrew spellings of drug names are mapped back to English, preferring the patient's own terms in `known_terms` and the account terms. Counts 3× toward the monthly character quota.

NameTypeReqDescription
glossaryobject–English term → Hebrew rendering, used to map the Hebrew back to English.
known_termsarray–English terms from the patient's record, used to map Hebrew spellings back. Up to 500. Account terms are added automatically.
textstringyesThe Hebrew question, up to 2,000 characters.
NameTypeReqDescription
querystring–English query for your record search.
termsarray–Hebrew spellings that were mapped back to English terms.
usageobject––

No examples provided.

clinical_translate ~537

Translate a complete English clinical text (a discharge summary, patient instructions, a visit note, a model's answer) into Israeli medical Hebrew for a clinician or a patient. Drug names, doses, lab values, units, ICD-10 codes, clinical abbreviations, identifiers and every number are kept exactly; every sentence is checked for numbers, negation and laterality and reviewed for meaning. A sentence that fails is retried, then returned in English with status `fallback`: unverified Hebrew is never returned. Treat fallback sentences as untranslated. `audience`: `clinician` (default, keeps BID/PO shorthand) or `patient` (plain words). Pass the patient's medication and problem lists as `protected_terms`, names as `redact_terms` (hidden from the model), `reader_gender` and `patient_gender` when known, and `date_order` (US records are MDY). Counts 3× toward the monthly character quota.

NameTypeReqDescription
audiencestring–Who reads the Hebrew. `clinician` (default) keeps shorthand such as BID and PO; `patient` writes dosing shorthand (BID, PRN) as plain words.
bidistring–`isolate` wraps English values in Unicode isolates so "5 mg" never renders as "mg 5". `none` returns plain text.
date_orderstring–How to read ambiguous numeric dates in the source. US records are MDY.
date_stylestring–`hebrew` writes "4 במרץ 2026"; `iso` writes 2026-03-04; `keep` leaves unambiguous dates as written (an ambiguous one is still rewritten). A two-digit year is kept as written.
glossaryobject–English term → required Hebrew rendering. Up to 500 entries.
patient_genderstring–Gender of the patient in third-person references. Inferred from he/she when omitted.
protected_termsarray–Kept verbatim. Pass the patient's medication and problem lists from the record. Up to 500, each up to 200 characters. Added to the account terms list for this request.
reader_genderstring–Gender of the reader, the person the text calls "you". Omit when unknown.
redact_termsarray–Kept verbatim and never shown to the model (patient and staff names). Up to 200.
textstringyesEnglish text, 1 to 20,000 characters. Markdown lists, headings and tables keep their structure. Counts toward the monthly character quota.
NameTypeReqDescription
idstring–Request identifier.
segmentsarray–One entry per sentence, in order.
statsobject––
textstring–The whole Hebrew document: every segment joined with its prefix and suffix.
usageobject––

No examples provided.

clinical_verify ~245

Check Hebrew that was produced some other way (for example by your own model) against its English clinical source: every drug, dose, lab value, code and number must appear exactly, no number may be added, dates must be unambiguous, and negation and laterality must survive. `verification: "strict"` adds an independent model review for meaning changes; `standard` (default) is deterministic. Returns pass or fail with every issue. Counts 3× toward the monthly character quota.

NameTypeReqDescription
date_orderstring–How to read ambiguous numeric dates in the source.
glossaryobject–English term → required Hebrew rendering.
protected_termsarray–Terms that must appear verbatim. Up to 500.
redact_termsarray–Names replaced before the reviewer sees the text. Up to 200.
sourcestringyesThe English source, up to 20,000 characters.
translationstringyesThe Hebrew to check, up to 40,000 characters.
verificationstring–`standard` (default) runs the deterministic checks. `strict` adds an independent model review for meaning changes.
NameTypeReqDescription
issuesarray–Every problem found.
passboolean–True when no issue has severity `error`.
usageobject––

No examples provided.

delete_term ~54

Permanently delete one account term by its id (from list_terms or add_terms). Protected translations stop using it within 30 seconds. Free.

NameTypeReqDescription
idstringyesThe term id, from list_terms or add_terms.
NameTypeReqDescription
deletedboolean––

No examples provided.

detect_language ~130

Detect the dominant language, script and direction of a string, with one segment per language. Built for short, code-switched input (chat messages, search queries, voice transcripts): a brand or acronym such as "PayPal" or "API" inside a Hebrew or Russian sentence does not change the dominant language. Use it to pick `source_lang` or the reply language before translating. Latin script is tagged `en`. Deterministic and free: no character quota.

NameTypeReqDescription
textstringyesText to classify, up to 20,000 characters. Built for short, code-switched input.
NameTypeReqDescription
confidencenumber–Share of letters in the dominant language, 0 to 1.
dirstring–Base direction of the dominant language.
langstring–Dominant language (BCP 47). Latin script is tagged `en`.
languagesarray–Every language found, largest share first.
scriptstring–Dominant ISO 15924 script.
segmentsarray–Same-script stretches in order, e.g. ru · en ("CBC") · ru. Latin script is tagged en.

No examples provided.

health ~29

Check that the HebrewCore API is up and its database reachable. Needs no API key and uses no quota.

Input schema present but exposes no named parameters.

NameTypeReqDescription
dbstring–`ok`, or `error` when the database check failed.
statusstring–`ok` when the API is serving.
versionstring–API version.

No examples provided.

list_languages ~55

List every language HebrewCore translates to and from, with its code (use it as `source_lang` / `target_lang`), English and native name, and writing direction. Protected translation covers Hebrew, English and Russian. Free.

Input schema present but exposes no named parameters.

NameTypeReqDescription
languagesarray–Every supported language.

No examples provided.

list_terms ~60

List the account's protected terms: drug, product and brand names that every protected translation on the account keeps exactly as written (or renders with the term's per-language translation when one is set). Returns each term's id, which delete_term needs. Free.

Input schema present but exposes no named parameters.

NameTypeReqDescription
limitinteger––
termsarray––

No examples provided.

strip_nikud ~92

Remove nikud, dagesh and cantillation marks from Hebrew text, keeping punctuation such as the maqaf. Use it to normalize text for search keys, comparison and de-duplication, or to get display text back from vocalized text. Deterministic and free: no character quota.

NameTypeReqDescription
textstringyesHebrew text with nikud or cantillation, up to 20,000 characters.
NameTypeReqDescription
strippedstring–The text without nikud, dagesh or cantillation. Punctuation such as the maqaf is kept.
textstring–The input.

No examples provided.

translate ~1,302

Translate one text between Hebrew, English, Russian and the other languages from list_languages. Use it for product, support, interface, finance, legal and general clinical text. Returns the translation with its direction metadata. Protected translation: set `protect: true`, a `domain` (`general`, `clinical`, `finance`, `legal`) or any protection field, and prices, quantities, numbers, dates, codes, identifiers, product names, interface variables ({name}, %s) and `protected_terms` are kept exactly as written, and every sentence is verified; a sentence that cannot be verified comes back in the source language (status `fallback`) instead of a wrong value. `finance` also protects IBANs, card and account numbers and checks credit/debit direction; `legal` keeps clause references, citations and defined terms and checks shall/may modality; `clinical` protects drugs, doses and lab values. Gender: `listener_gender` is the reader ("you"), `speaker_gender` the speaker ("I", e.g. an assistant). `glossary` maps source terms to required renderings; `redact_terms` keeps names exact and hidden from the model. `message_format: "icu"` translates an ICU MessageFormat string and rewrites plural branches for Hebrew and Russian. `quality`: `fast`, `balanced` (default) or `smartest`. Uses the monthly character quota. For many short strings use translate_batch; for full English clinical documents into Hebrew use clinical_translate.

NameTypeReqDescription
audiencestring–Clinical domain register. `clinician` (default) keeps shorthand such as BID and PO; `patient` writes it as plain words.
bidistring–`isolate` wraps protected values in Unicode isolates in Hebrew output. Default none; see /v1/wrap.
date_orderstring–How to read ambiguous numeric dates such as 04/03/2026. Default MDY for English sources, DMY for Hebrew and Russian.
date_stylestring–`hebrew` (default) spells the month out in the target language ("4 במרץ 2026", "4 марта 2026 г."); `iso`; `keep` (unambiguous dates only).
domainstring–`general` (default) for product, commerce, support and interface text. `clinical` adds clinical register and drug, dose, lab and abbreviation detection. `finance` adds a formal banking register, prot…
genderstring–Grammatical gender for the reader where the target language marks it. For assistants, prefer `listener_gender` and `speaker_gender`.
glossaryobject–Source term → required rendering in the target language. Up to 500 entries. Wins over an account term with the same text.
listener_genderstring–Gender of the reader ("you"): תרצי / תרצה. Hebrew and Russian mark it; English does not. Without it, Hebrew interface text uses neutral forms.
message_formatstring–`icu`: the text is an ICU MessageFormat message. The result is a valid ICU message in the target language: arguments ({name}, {count, number}, {d, date, short}) and `#` are kept, plural and selectord…
patient_genderstring–Clinical domain: gender of a patient referred to in the third person.
protectboolean–Keep prices, quantities, numbers, dates, codes, identifiers, product names, interface variables ({name}, %s) and <keep>…</keep> text exactly as written, and verify every sentence. Implied by any prot…
protected_termsarray–Terms kept exactly as written: product names, brand names, SKUs. Up to 500, each up to 200 characters. Added to the account terms list for this request.
qualitystring–`fast`: lowest latency, for high volume and short strings. `balanced`: the default. `smartest`: maximum nuance for long or sensitive text.
redact_termsarray–Kept exactly and never shown to the model: customer names and other personal data. Up to 200.
source_langstring–BCP 47 source language, or `auto` (default) to detect it.
speaker_genderstring–Gender of the speaker ("I"), for an assistant or brand voice: מצאתי, я нашла / я нашёл.
target_langstringyesBCP 47 target language, e.g. `he`, `en`, `ru`. See GET /v1/languages.
textstringyesText to translate, 1 to 20,000 characters. Counts toward the monthly character quota.
transliterateboolean–Include a Latin transliteration when the target is Hebrew.
NameTypeReqDescription
idstring–Request identifier. Include it when you contact support.
qualitystring–Quality tier used.
source––The source text with its directionality metadata.
translation––The translation with its directionality metadata.
usageobject–What this request consumed.

No examples provided.

translate_batch ~1,104

Translate 1 to 50 strings (each up to 5,000 characters) into one target language in a single call; results come back in input order. Use it for the interface strings of a screen, a string file, or the fields of a product. Takes every option of translate: `protect`, `domain` (`general`, `clinical`, `finance`, `legal`), `protected_terms`, `glossary`, `listener_gender`, `speaker_gender`, `message_format: "icu"` and `quality`. With protection, interface variables such as {count}, {{name}} and %s, numbers, prices and dates stay exactly as written, and each item carries its own verification status. Uses the monthly character quota.

NameTypeReqDescription
audiencestring–Clinical domain register. `clinician` (default) keeps shorthand such as BID and PO; `patient` writes it as plain words.
bidistring–`isolate` wraps protected values in Unicode isolates in Hebrew output. Default none; see /v1/wrap.
date_orderstring–How to read ambiguous numeric dates such as 04/03/2026. Default MDY for English sources, DMY for Hebrew and Russian.
date_stylestring–`hebrew` (default) spells the month out in the target language ("4 במרץ 2026", "4 марта 2026 г."); `iso`; `keep` (unambiguous dates only).
domainstring–`general` (default) for product, commerce, support and interface text. `clinical` adds clinical register and drug, dose, lab and abbreviation detection. `finance` adds a formal banking register, prot…
genderstring–Grammatical gender for the reader where the target language marks it.
glossaryobject–Source term → required rendering in the target language. Up to 500 entries. Wins over an account term with the same text.
itemsarrayyes1 to 50 strings, each up to 5,000 characters. A protected batch carries at most 20,000 characters in total.
listener_genderstring–Gender of the reader ("you"): תרצי / תרצה. Hebrew and Russian mark it; English does not. Without it, Hebrew interface text uses neutral forms.
message_formatstring–`icu`: every item is an ICU MessageFormat message. Each result is a valid ICU message in the target language: arguments ({name}, {count, number}, {d, date, short}) and `#` are kept, plural and select…
patient_genderstring–Clinical domain: gender of a patient referred to in the third person.
protectboolean–Keep prices, quantities, numbers, dates, codes, identifiers, product names, interface variables ({name}, %s) and <keep>…</keep> text exactly as written, and verify every sentence. Implied by any prot…
protected_termsarray–Terms kept exactly as written: product names, brand names, SKUs. Up to 500, each up to 200 characters. Added to the account terms list for this request.
qualitystring–Quality tier, applied to every item.
redact_termsarray–Kept exactly and never shown to the model: customer names and other personal data. Up to 200.
source_langstring–BCP 47 source language, or `auto` (default).
speaker_genderstring–Gender of the speaker ("I"), for an assistant or brand voice: מצאתי, я нашла / я нашёл.
target_langstringyesBCP 47 target language, applied to every item.
transliterateboolean–Include a Latin transliteration when the target is Hebrew.
NameTypeReqDescription
resultsarray–One translation per item, in input order.
usageobject–What this request consumed.

No examples provided.

transliterate ~119

Romanize Hebrew into Latin letters (`direction: "he-to-latin"`, the default), or write Latin spelling in Hebrew letters (`direction: "latin-to-he"`) for name entry and search. Up to 5,000 characters. Uses the monthly character quota.

NameTypeReqDescription
directionstring–`he-to-latin` (default) romanizes Hebrew. `latin-to-he` writes Latin spelling in Hebrew letters, for name entry and search.
textstringyesText to transliterate, up to 5,000 characters.
NameTypeReqDescription
directionstring–Direction used.
schemestring–Romanization scheme used.
textstring–The input.
transliterationstring–The transliterated text.

No examples provided.

wrap_for_display ~246

Make one mixed Hebrew/English display line render correctly: every left-to-right unit (a Latin term, a price, a number with its unit, a range such as "10–20%", a date, a comparison such as "<5") is kept whole and in order, so nothing is reversed or mirrored inside a Hebrew line. `format`: `html` (dir spans, for web and React), `isolate` (Unicode isolates, for iOS, Android 7+ and browsers) or `marks` (LRM/RLM, for any renderer including older Android). Pass `base: "rtl"` for a Hebrew line that starts with a Latin term. Deterministic and free: no character quota.

NameTypeReqDescription
basestring–Paragraph direction of the display surface. Pass `rtl` for a Hebrew line even when it starts with a Latin term.
formatstring–`html` for the web; `isolate` (Unicode isolates) for modern text engines; `marks` (LRM/RLM) for every renderer, including older Android.
textstringyesThe display line, up to 20,000 characters.
NameTypeReqDescription
dirstring–Paragraph direction used.
formatstring–Format used.
outputstring–Render-ready text: HTML with `dir` spans, or the text with Unicode isolates or direction marks inserted.
runsarray–The display runs the output was built from.

No examples provided.

Common questions

What is the HebrewCore by baba Hebrew MCP server?

HebrewCore by baba Hebrew is an MCP server listed in the public MCP registry as com.itsbaba/hebrewcore. Hebrew translation that keeps prices, names and dates exact, RTL display, nikud, clinical Hebrew. This page covers its hosted endpoint (https://hc.itsbaba.com/mcp).

Is the HebrewCore by baba Hebrew MCP server safe to use?

HebrewCore by baba Hebrew scores 60 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 HebrewCore by baba Hebrew MCP server expose?

HebrewCore by baba Hebrew exposes 16 tools: translate, translate_batch, analyze_direction, detect_language, wrap_for_display, and 11 more. Their descriptions and schemas cost roughly 4,587 tokens of context every time the server is loaded.

Does the HebrewCore by baba Hebrew MCP server require authentication?

No. We connected to HebrewCore by baba Hebrew without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the HebrewCore by baba Hebrew MCP server still maintained?

HebrewCore by baba Hebrew is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.