localize.dev
NPM · LOCALIZE-DEV · 2 COMPONENTS
Find hardcoded UI text, give it translation keys, translate it and write the locale files.
Available components
Last scanned (15 hours ago)
Scores higher than 41% of npm servers
Category Developer Tools
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 Security99
- 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
- 11 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 885 tokens (~177/item across 5 items; 5 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 Management37
- Stability observed for 11 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- Maintenance
- Security disclosure
- 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.
- License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Nov 26 +11
- CVE-2026-112366 no longer affects this package ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.92 ▲ functional
- 19 Nov 26 −10
- Known CVEs: partial → unverified ▼ security
- CVE-2026-112366 no longer affects this package ▲ security
- Known CVEs: partial → pass ▲ security
- Dependency health: 0.91 → unverified ▼ functional
- Package version: 0.35.4 → 0.36.0 functional
- 18 Nov 26 0
- CVE-2026-112366 affects this package ▼ security
- Known CVEs: pass → partial ▼ security
- 17 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.91 ▲ functional
- 16 Nov 26 −10
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Dependency health: 0.91 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.35.0 → 0.35.4 functional
- Package version: 0.35.0 → 0.35.3 functional
- Package version: 0.35.0 → 0.35.2 functional
- Package version: 0.35.0 → 0.35.1 functional
- 15 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.
- 13 Nov 26 +15
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.34.6 → 0.35.0 functional
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/localize-dev@0.36.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 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 11 |
| 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 →
add_language Add a language ~112
Adds a language: puts it in targetLocales in localize.config.json (creating the file when missing), translates every message into it and adds it to the i18n setup localize.dev generated. Needs a localize.dev API key.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | Monorepo: the app to work in (e.g. apps/web), relative to the repository root. Default: the root. |
| locale | string | yes | BCP 47 code, e.g. "ja", "pt-BR". |
No output schema declared.
No examples provided.
check Check localization ~205
Finds UI copy still hardcoded in the code and translations missing or out of date in the locale files, each with its file and line. Changes nothing and needs no API key. Run it before and after localize or translate.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | Monorepo: the app to work in (e.g. apps/web), relative to the repository root. Default: the root. |
| changed | boolean | – | Only the files changed since the last commit (staged or not, and new ones), like paths. |
| dir | string | – | Source folder to scan, relative to the app (default: localize.config.json, else the framework's own). |
| only | string | – | Check only hardcoded copy, or only translations. |
| paths | array | – | Only these files, relative to the source folder (e.g. ["components/Cart.tsx"]): hardcoded copy and unknown keys in them. Fast; use it on the files you just changed. |
No output schema declared.
No examples provided.
config Read localization settings ~101
The project's localization settings: source and target languages, where locale files live, the folder scanned, the framework and i18n library, and its glossary (terms kept untranslated, preferred translations per language, tone). Read it before writing UI copy or translations by hand, so new strings follow the same conventions.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | Monorepo: the app to work in (e.g. apps/web), relative to the repository root. Default: the root. |
No output schema declared.
No examples provided.
localize Localize hardcoded text ~244
Extracts hardcoded UI strings into translation keys, rewrites the code to call the i18n library (setting it up when missing), and translates the new messages into every target language. Follows localize.config.json. Writes files unless dry_run; review the diff afterwards. Needs a localize.dev API key.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | Monorepo: the app to work in (e.g. apps/web), relative to the repository root. Default: the root. |
| changed | boolean | – | Only the files changed since the last commit (staged or not, and new ones), instead of paths. |
| dir | string | – | Source folder to scan, relative to the app (default: localize.config.json, else the framework's own). |
| dry_run | boolean | – | Report what would change without writing files. |
| locales | array | – | Target languages, e.g. ["es","fr"] (default: localize.config.json). |
| paths | array | – | Only these files or globs, relative to the source folder (e.g. ["components/Cart.tsx"]). Pass the files you just changed, so a run stays quick. |
No output schema declared.
No examples provided.
translate Fill missing translations ~135
Fills in missing translations, and redoes ones whose source text changed, in the existing locale files (JSON, YAML, .po, .arb, strings.xml, .xcstrings, .strings, messages.json). Code is not changed. Needs a localize.dev API key.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | Monorepo: the app to work in (e.g. apps/web), relative to the repository root. Default: the root. |
| dry_run | boolean | – | Report what would change without writing files. |
| locales | array | – | Languages to translate into, creating files as needed (default: the languages already there). |
No output schema declared.
No examples provided.
How do I install the localize.dev MCP server?
localize.dev runs locally as an npm package, launched with npx -y localize-dev 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 · localize-dev
claude mcp add ufortstephen-localize-dev -- npx -y localize-dev mcp
What is the localize.dev MCP server?
localize.dev is an MCP server listed in the public MCP registry as io.github.ufortstephen/localize-dev. Find hardcoded UI text, give it translation keys, translate it and write the locale files. This page covers its npm package (localize-dev).
Is the localize.dev MCP server safe to use?
localize.dev scores 70 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 localize.dev MCP server expose?
localize.dev exposes 5 tools: check, localize, translate, add_language, config. Their descriptions and schemas cost roughly 797 tokens of context every time the server is loaded.
Is the localize.dev MCP server still maintained?
localize.dev 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 did VerifyMCP test on the localize.dev MCP server?
VerifyMCP ran 15 checks on localize.dev, 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 localize.dev: License. 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.