Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
KAERIS i18n is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
223
downloads in 30d
local
runs on your machine
7
tools declared
What it does
Translate app language files into 46 languages and check placeholders, plurals and missing keys.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user kaeris-i18n-mcp '--' uvx kaeris-mcp
# 2 — ask your agent for something these tools do
# kaeris_list_languages, kaeris_scan_repo, kaeris_status and 4 more
KAERIS i18n costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
KIAll 1 server
kaeris-io1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts KAERIS i18n as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user kaeris-i18n-mcp '--' uvx kaeris-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add — some of its tools take a key of its publisher’s own, and the rest work without.
What it asks of you
Nothing is required, but it can take KAERIS_API_KEY (KAERIS API key (optional; the free demo works without one)), KAERIS_OPENROUTER_KEY (OpenRouter key for the Lifetime (BYOK) plan (optional)) if you want to set them. Its publisher says some of its tools need one of them, and the rest work without.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List every target language KAERIS can translate into.
Takes no parameters.
Discover a repo's i18n setup: which locale files exist, what the base (source) language and target languages are, and which framework/convention is in use. Purely local — reads the filesystem, makes no API call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | directory to scan (default: current directory). |
Completeness/health check for every target locale against a source file — the "i18n firewall". Works for EVERY supported format: JSON is checked fully offline; other formats (.arb/.strings/.po/.xml/.ftl/…) are parsed by the backend /api/parse endpoint (no translation, no cost).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | path to the base-language locale file, e.g. "locales/en.json" or "lib/l10n/app_en.arb" (typically kaeris_scan_repo's base_lang file). |
| langs | array | no | target language codes to check, e.g. ["de", "fr"]. If omitted, falls back to kaeris.json's "langs" if present, else auto-discovers sibling <lang> files next to the source. |
| out | string | no | directory containing the target locale files (default: source's own directory; each target is expected at "<out>/<lang><source-ext>", e.g. de.json for en.json, de.arb for en.arb). |
The exact keys missing or placeholder-broken in ONE target locale, with their source-language text, so an agent knows exactly what to translate/fix.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | path to the base-language locale file, e.g. "locales/en.json" or "app_en.arb". |
| lang | string | yes | the target language code to inspect, e.g. "de". |
| out | string | no | directory containing the target locale file (default: source's own directory; expected at "<out>/<lang><source-ext>", e.g. de.json / de.arb). |
| limit | integer | no | how many missing keys to return in this call (default 200, max 2000). |
| offset | integer | no | where to start — pass "page.next_offset" from the previous call. |
Bootstrap a BRAND-NEW target locale by translating the entire source file into it and writing the result. Use this when kaeris_scan_repo/kaeris_status show a language with no locale file at all yet (in "missing_files").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | path to the base-language locale file, e.g. "locales/en.json". |
| lang | string | yes | the new target language code to create, e.g. "de". |
| out | string | no | output directory (default: source file's own directory). |
| tone | string | no | "formal" or "casual" to steer register; "" (default) is neutral. |
| icu | boolean | no | True if the source uses ICU MessageFormat (plurals/select), so the model preserves the syntax instead of translating it. |
| keep | array | no | optional list of terms to NEVER translate (brand/product names). |
| context | string | no | one line about what the app IS, e.g. "a mobile bank for teenagers" or "a wildlife documentary app". The model uses it to pick the right sense of ambiguous strings — "Bank" becomes Ufer in the second a |
| api_key | string | no | — |
| openrouter_key | string | no | — |
| job_id | string | no | leave empty to start a translation. If a previous call came back with {"status": "running", "job_id": ...}, pass that id (with the same source/out) to collect the finished result instead of paying for |
Translate a set of UI strings into one or more languages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| strings | object | yes | key → source-text pairs, e.g. {"greeting": "Hello", "save": "Save"}. |
| target_languages | array | yes | language codes from kaeris_list_languages, e.g. ["es", "fr", "ja"]. |
| keep | array | no | optional list of terms to NEVER translate — kept verbatim in every language (brand/product names), e.g. ["KAERIS", "GitHub"]. |
| verify | boolean | no | back-translation and meaning check for your review — back-translates into back_lang and flags lines whose meaning may have changed (uses more tokens). |
| back_lang | string | no | language for the verify back-translation (default "en"). |
| tone | string | no | "formal" or "casual" to steer register; "" (default) is neutral. |
| icu | boolean | no | True if values may contain ICU MessageFormat (plurals/select) so the model preserves the syntax instead of translating it. |
| reuse | object | no | optional {lang: {key: previous_translation}} translation-memory map — strings that are unchanged from a prior run are reused verbatim server-side and only new/changed strings are actually translated. |
| context | string | no | one line about what the app IS, e.g. "a mobile bank for teenagers" or "a wildlife documentary app". The model uses it to pick the right sense of ambiguous strings — "Bank" becomes Ufer in the second a |
| api_key | string | no | — |
| openrouter_key | string | no | — |
| job_id | string | no | — |
Translate a strings file on disk and write the results next to it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_path | string | yes | path to the source file, e.g. "locales/en.json". |
| target_languages | array | yes | language codes, e.g. ["de", "uk", "zh"]. |
| out_dir | string | no | where to write outputs (default: the source file's directory). |
| only_new | boolean | no | reproducible incremental mode — translate only new AND edited keys, tracked via kaeris.lock (a tone/ICU/glossary change re-translates all); unchanged stays stable. JSON and ARB only — for any other fo |
| keep | array | no | optional list of terms to NEVER translate — kept verbatim in every language (brand/product names), e.g. ["KAERIS", "GitHub"]. |
| verify | boolean | no | back-translation and meaning check for your review; with only_new the result carries them as "back_translations". |
| back_lang | string | no | language for the verify back-translation (default "en"). |
| tone | string | no | "formal" or "casual" to steer register; "" (default) is neutral. |
| icu | boolean | no | True if values may contain ICU MessageFormat (plurals/select) so the model preserves the syntax instead of translating it. |
| reuse | object | no | optional {lang: {key: previous_translation}} translation-memory map — strings unchanged from a prior run are reused verbatim server-side (non-incremental only; only_new does its own client-side diffin |
| context | string | no | one line about what the app IS, e.g. "a mobile bank for teenagers" or "a wildlife documentary app". The model uses it to pick the right sense of ambiguous strings — "Bank" becomes Ufer in the second a |
| api_key | string | no | — |
| openrouter_key | string | no | — |
| job_id | string | no | — |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install KAERIS i18n or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.2.18 · scanned 1 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest1ce13df2836e396f5566f5e440eb35a2530984bbca4f6cdd70d7093106972683
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| kaeris_list_languages | no tags | |
| kaeris_scan_repo | no tags | |
| kaeris_status | no tags | |
| kaeris_list_missing_keys | no tags | |
| kaeris_add_language | no tags | |
| kaeris_translate | no tags | |
| kaeris_translate_file | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest1ce13df2836e396f
Scanned2026-11-01
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.18. Pin a release below and the command asks for exactly that one.
0.2.18
1 Nov 2026
latestNo release note was published with this version.
0.2.17
29 Oct 2026
No release note was published with this version.
0.2.16
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish KAERIS i18n can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.