io.github.Shipi18n/shipi18n
NPM · @SHIPI18N/MCP · SCANNED SEP 21
Translation QA for locale files: keyless validators, semantic review and BYO-key translation
Available components
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 114 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 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 801 tokens (~100/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
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
{
"mcpServers": {
"shipi18n-shipi18n": {
"command": "npx",
"args": [
"-y",
"@shipi18n/mcp"
]
}
}
} {
"servers": {
"shipi18n-shipi18n": {
"command": "npx",
"args": [
"-y",
"@shipi18n/mcp"
]
}
}
} codex mcp add shipi18n-shipi18n -- npx -y @shipi18n/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shipi18n-shipi18n": {
"type": "local",
"command": [
"npx",
"-y",
"@shipi18n/mcp"
],
"enabled": true
}
}
} openclaw mcp add shipi18n-shipi18n --command npx --arg -y --arg @shipi18n/mcp
mcp_servers:
shipi18n-shipi18n:
command: "npx"
args: ["-y", "@shipi18n/mcp"] {
"McpServers": {
"shipi18n-shipi18n": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@shipi18n/mcp"
]
}
}
} assistant mcp add shipi18n-shipi18n -t stdio -c npx -a -y @shipi18n/mcp
{
"mcpServers": {
"shipi18n-shipi18n": {
"command": "npx",
"args": [
"-y",
"@shipi18n/mcp"
]
}
}
} 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 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.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 8 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 7 Sept 26 66
First indexed and scored.
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 Sept 2026 · Analysed npm/@shipi18n/mcp@2.1.1
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.5.2 |
| Rekor log index | 2749449579 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:705dc85a7615d50d3c269396edecdf3417a57412bdf202a820e53c4562421c4ba3baee120057b06d5f94ecdc341745781a1d5c229e844f12f7896d095 |
Background: How many MCP packages publish verified provenance →
Dependencies 114 packages
| Packages resolved | 114 |
|---|---|
| Stale | 31 |
| 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 ~88
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 the locale tree, .arb directory, or .xcstrings file |
| source | string | – | Source language code |
No output schema declared.
No examples provided.
check_locales Check locale files ~116
Validate translated locale files against the source language: missing/orphaned keys, dropped or invented placeholders, collapsed plurals, empty values, untranslated copy. 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 the locale tree, .arb directory, or .xcstrings file |
| source | string | – | Source language code |
No output schema declared.
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 ~85
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 the locale tree, .arb directory, or .xcstrings file |
| source | string | – | Source language code |
No output schema declared.
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.
No output schema declared.
No examples provided.
review_locales Get translation pairs for semantic review ~108
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 the locale tree, .arb directory, or .xcstrings file |
| source | string | – | Source language code |
No output schema declared.
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" |
No output schema declared.
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" |
No output schema declared.
No examples provided.
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. Translation QA for locale files: keyless validators, semantic review and BYO-key translation. This page covers its npm package (@shipi18n/mcp).
Is the io.github.Shipi18n/shipi18n MCP server safe to use?
io.github.Shipi18n/shipi18n scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 801 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 21 September 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.