io.github.Shipi18n/shipi18n
NPM · @SHIPI18N/MCP
Check locale files for broken placeholders, plurals and missing keys. Validators need no API key.
Available components
Last scanned (4 hours ago)
Scores higher than 93% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Shipi18n/shipi18n). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 26 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1043 tokens (~130/item across 8 items; 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
- Structured output schemas are declared (88% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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 →
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.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 15 Oct 26 −3
- Stability: pass → 0.80 functional
- 14 Oct 26 +46
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 13 Oct 26 0
- Package version: 2.3.1 → 2.3.2 functional
- 12 Oct 26 −45
- Stability: 0.93 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 2.3.1 → 2.3.2 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 6 Nov 2026 · Analysed npm/@shipi18n/mcp@2.3.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Shipi18n/shipi18n |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Shipi18n/shipi18n/.github/workflows/publish.yml@refs/tags/v2.16.1 |
| Rekor log index | 3188304144 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a9f350e48f72d5e7ea3761150ad39c8077181e8ce93c772ecad9dc083e805c01530e722a8155f6ce9f78b801f0d26853d25b857b7eabe1250a89d563b |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 111 packages
| Packages resolved | 111 |
|---|---|
| Stale | 30 |
| 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 →
check_glossary Check glossary compliance ~141
Enforce do-not-translate terms and locked per-language translations across a locale tree. Deterministic string matching — no API key and no model call required.
| Name | Type | Req | Description |
|---|---|---|---|
| glossaryPath | string | yes | Path to a glossary JSON file |
| path | string | yes | Path to a locale folder or file: JSON (flat or nested, i18next/vue-i18n/next-intl), YAML incl. Rails config/locales, a Flutter .arb folder, an Apple .xcstrings file, an Android res/ folder, gettext .… |
| source | string | – | Source language code |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| terms | array | yes | – |
| violations | array | yes | – |
No examples provided.
check_locales Check locale files ~199
Validate translated locale files against the source language: missing/orphaned keys, dropped or invented placeholders, collapsed plurals, empty values, untranslated copy. Reads JSON, YAML (incl. Rails), Flutter ARB, Apple .xcstrings, Android strings.xml, gettext .po and XLIFF. Deterministic — no API key and no model call required.
| Name | Type | Req | Description |
|---|---|---|---|
| glossaryPath | string | – | Path to a glossary JSON file |
| ignoreKeys | string | – | Comma-separated '*' globs of keys to silence |
| path | string | yes | Path to a locale folder or file: JSON (flat or nested, i18next/vue-i18n/next-intl), YAML incl. Rails config/locales, a Flutter .arb folder, an Apple .xcstrings file, an Android res/ folder, gettext .… |
| source | string | – | Source language code |
| Name | Type | Req | Description |
|---|---|---|---|
| languages | array | yes | – |
| layout | string | yes | – |
| source | string | yes | – |
| totals | object | yes | – |
No examples provided.
check_placeholders Check Placeholders ~47
Verify a translated string preserves all placeholders from the source (no LLM call).
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | The source string |
| translation | string | yes | The translated string to check |
No output schema declared.
No examples provided.
diff_locales Diff locales against the source ~138
Answer "what needs translating?": per language, the keys missing from the translation and the keys present that no longer exist in the source. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Limit to one language |
| path | string | yes | Path to a locale folder or file: JSON (flat or nested, i18next/vue-i18n/next-intl), YAML incl. Rails config/locales, a Flutter .arb folder, an Apple .xcstrings file, an Android res/ folder, gettext .… |
| source | string | – | Source language code |
| Name | Type | Req | Description |
|---|---|---|---|
| languages | array | yes | – |
| source | string | yes | – |
No examples provided.
list_languages List Languages ~33
List the language codes and names Shipi18n recognizes (any BCP-47 code works; these have friendly names).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| languages | array | yes | – |
No examples provided.
review_locales Get translation pairs for semantic review ~161
Return source/translation pairs plus review criteria so YOU can judge translation quality with your own reasoning. The server performs no model call and needs no API key. Structurally broken keys are excluded — run check_locales for those.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | yes | Language to review |
| limit | integer | – | Maximum pairs to return |
| path | string | yes | Path to a locale folder or file: JSON (flat or nested, i18next/vue-i18n/next-intl), YAML incl. Rails config/locales, a Flutter .arb folder, an Apple .xcstrings file, an Android res/ folder, gettext .… |
| source | string | – | Source language code |
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | yes | – |
| excludedStructurallyBroken | number | yes | – |
| instructions | string | yes | – |
| lang | string | yes | – |
| pairs | array | yes | – |
| returned | number | yes | – |
| source | string | yes | – |
No examples provided.
translate_file Translate File ~158
Read a JSON locale file from disk, translate it into one or more languages, and write <lang>.json files. Set incremental=true to reuse existing output files and only translate new/missing keys.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Source language code (default: en) |
| incremental | boolean | – | Reuse existing <lang>.json and only translate new keys |
| model | string | – | – |
| outDir | string | – | Output directory (default: same directory as the source file) |
| path | string | yes | Path to the source locale JSON file, e.g. locales/en.json |
| provider | string | – | – |
| to | string | yes | Target language code(s), comma-separated, e.g. "es,fr,de" |
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | yes | – |
| warnings | array | yes | – |
| written | – | – | – |
No examples provided.
translate_json Translate JSON ~166
Translate an i18n locale JSON object to one or more target languages, preserving structure and placeholders. Requires your own LLM key (ANTHROPIC_API_KEY/OPENAI_API_KEY). For key-free work use the validation tools. Legacy: the MCP client's model via sampling.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The source locale as a JSON string, e.g. {"greeting":"Hello {{name}}"} |
| from | string | – | Source language code (default: en) |
| model | string | – | Override the provider default model |
| provider | string | – | Force a provider: anthropic or openai. Omit to auto-detect from the environment. |
| to | string | yes | Target language code(s), comma-separated, e.g. "es,fr,de" |
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | yes | – |
| translations | object | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the io.github.Shipi18n/shipi18n MCP server?
io.github.Shipi18n/shipi18n runs locally as an npm package, launched with npx -y @shipi18n/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 · @shipi18n/mcp
claude mcp add shipi18n-shipi18n -- npx -y @shipi18n/mcp
What is the io.github.Shipi18n/shipi18n MCP server?
io.github.Shipi18n/shipi18n is an MCP server listed in the public MCP registry as io.github.Shipi18n/shipi18n. Check locale files for broken placeholders, plurals and missing keys. Validators need no API key. This page covers its npm package (@shipi18n/mcp).
Is the io.github.Shipi18n/shipi18n MCP server safe to use?
io.github.Shipi18n/shipi18n scores 90 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.Shipi18n/shipi18n MCP server expose?
io.github.Shipi18n/shipi18n exposes 8 tools: check_locales, check_glossary, diff_locales, review_locales, list_languages, and 3 more. Their descriptions and schemas cost roughly 1,043 tokens of context every time the server is loaded.
Is the io.github.Shipi18n/shipi18n MCP server still maintained?
io.github.Shipi18n/shipi18n is still listed as active in the MCP registry. We last reached this channel on 6 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.Shipi18n/shipi18n MCP server under?
io.github.Shipi18n/shipi18n declares the Apache-2.0 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.Shipi18n/shipi18n MCP server?
VerifyMCP ran 16 checks on io.github.Shipi18n/shipi18n, 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.