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.

io.github.CloudCorpRecords/alephtext

NPM · @RENETURCIOS/ALEPHTEXT · 2 COMPONENTS

Hebrew translation with protected terms: nikud, transliteration, RTL layout and clinical checks.

69 Trust /100

Last scanned (19 hours ago)

Scores higher than 39% of npm servers

Category Health and Science

Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4600 tokens (~287/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 Management17
  • Stability observed for 5 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "strip_nikud" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 16 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

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.

  • 21 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 67

    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 21 Nov 2026 · Analysed npm/@reneturcios/alephtext@0.1.0

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 →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~4,600 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.

No output schema declared.

No examples provided.

add_terms ~132

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
termsarrayyesThe protected terms to add or update (matched by exact term text).

No output schema declared.

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`.

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/alephtext MCP server?

io.github.CloudCorpRecords/alephtext runs locally as an npm package, launched with npx -y @reneturcios/alephtext 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 · @reneturcios/alephtext

# add to Claude Code
claude mcp add cloudcorprecords-alephtext -- npx -y @reneturcios/alephtext mcp
Common questions

What is the io.github.CloudCorpRecords/alephtext MCP server?

io.github.CloudCorpRecords/alephtext is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/alephtext. Hebrew translation with protected terms: nikud, transliteration, RTL layout and clinical checks. This page covers its npm package (@reneturcios/alephtext).

Is the io.github.CloudCorpRecords/alephtext MCP server safe to use?

io.github.CloudCorpRecords/alephtext scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting 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 io.github.CloudCorpRecords/alephtext MCP server expose?

io.github.CloudCorpRecords/alephtext exposes 16 tools: translate, translate_batch, analyze_direction, detect_language, wrap_for_display, and 11 more. Their descriptions and schemas cost roughly 4,600 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/alephtext MCP server still maintained?

io.github.CloudCorpRecords/alephtext 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 io.github.CloudCorpRecords/alephtext MCP server under?

io.github.CloudCorpRecords/alephtext 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 io.github.CloudCorpRecords/alephtext MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/alephtext, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.