# localize.dev (npm · localize-dev)

Find hardcoded UI text, give it translation keys, translate it and write the locale files.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `uselocalize.dev`: 38/100, [markdown](https://verifymcp.io/servers/ufortstephen-localize-dev/api-mcp.md), [page](https://verifymcp.io/servers/ufortstephen-localize-dev/api-mcp)
- npm · `localize-dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/ufortstephen-localize-dev/localize-dev.md), [page](https://verifymcp.io/servers/ufortstephen-localize-dev/localize-dev)

## Channel facts

- Registry: `npm`
- Package: `localize-dev`
- Version: `0.36.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 11 of 41 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - 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.
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add ufortstephen-localize-dev -- npx -y localize-dev mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ufortstephen-localize-dev": {
      "command": "npx",
      "args": [
        "-y",
        "localize-dev",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ufortstephen-localize-dev": {
      "command": "npx",
      "args": [
        "-y",
        "localize-dev",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ufortstephen-localize-dev -- npx -y localize-dev mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ufortstephen-localize-dev": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "localize-dev",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ufortstephen-localize-dev --command npx --arg -y --arg localize-dev --arg mcp
```

### Hermes

```yaml
mcp_servers:
  ufortstephen-localize-dev:
    command: "npx"
    args: ["-y", "localize-dev", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ufortstephen-localize-dev": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "localize-dev",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ufortstephen-localize-dev -t stdio -c npx -a -y localize-dev mcp
```

### Other

```json
{
  "mcpServers": {
    "ufortstephen-localize-dev": {
      "command": "npx",
      "args": [
        "-y",
        "localize-dev",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 70, +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.

### 2026-11-20 (score 69, +11)

- [security improvement] CVE-2026-112366 no longer affects this package
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.92

### 2026-11-19 (score 58, −10)

- [security regression] Known CVEs: partial → unverified
- [security improvement] CVE-2026-112366 no longer affects this package
- [security improvement] Known CVEs: partial → pass
- [functional regression] Dependency health: 0.91 → unverified
- [functional] Package version: 0.35.4 → 0.36.0

### 2026-11-18 (score 68, 0)

- [security regression] CVE-2026-112366 affects this package
- [security regression] Known CVEs: pass → partial

### 2026-11-17 (score 68, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.91

### 2026-11-16 (score 57, −10)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.17 → unverified
- [functional regression] Dependency health: 0.91 → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] 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

### 2026-11-15 (score 67, +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.

### 2026-11-13 (score 66, +15)

- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.34.6 → 0.35.0

## MCP tools (5)

### `check` (~205 tokens)

Check localization

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.

Input parameters:

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

### `localize` (~244 tokens)

Localize hardcoded text

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.

Input parameters:

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

### `translate` (~135 tokens)

Fill missing translations

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.

Input parameters:

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

### `add_language` (~112 tokens)

Add a language

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.

Input parameters:

- `app` (string): Monorepo: the app to work in (e.g. apps/web), relative to the repository root. Default: the root.
- `locale` (string, required): BCP 47 code, e.g. "ja", "pt-BR".

### `config` (~101 tokens)

Read localization settings

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.

Input parameters:

- `app` (string): Monorepo: the app to work in (e.g. apps/web), relative to the repository root. Default: the root.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ufortstephen-localize-dev/localize-dev#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 58
- 2026-11-18: 68
- 2026-11-17: 68
- 2026-11-16: 57
- 2026-11-15: 67
- 2026-11-14: 66
- 2026-11-13: 66
- 2026-11-12: 51
- 2026-11-11: 50
- 2026-11-10: 50

## Common questions

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

## Links

- npm package: https://www.npmjs.com/package/localize-dev
- Socket report: https://socket.dev/npm/package/localize-dev
- Repository: https://github.com/ufortstephen/localize-dev
- Website: https://uselocalize.dev/
- Changelog RSS feed: https://verifymcp.io/servers/ufortstephen-localize-dev/localize-dev.xml
- Changelog JSON feed: https://verifymcp.io/servers/ufortstephen-localize-dev/localize-dev/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ufortstephen-localize-dev/localize-dev.json
- HTML version of this page: https://verifymcp.io/servers/ufortstephen-localize-dev/localize-dev
