io.github.Pakvothe/i1n
NPM · I1N
Agent-complete localization: extract strings, push keys, AI-translate, pull type-safe TS types.
Available components
Last scanned (1 hour ago)
Scores higher than 66% 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
- 31 of 108 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 26 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 869 tokens (~86/item across 10 items; 9 tools + 1 resources), lean.Pass
- 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 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
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.
- 5 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 22 Oct 26 −1
- Stability: pass → 0.93 functional
- 16 Oct 26 +1
- Stability: 0.97 → pass security
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 5 Nov 2026 · Analysed npm/i1n@1.4.7
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 →
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 108 packages
| Packages resolved | 108 |
|---|---|
| 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 →
i1n_add_language ~70
Add new languages to the project and optionally auto-translate existing keys
| Name | Type | Req | Description |
|---|---|---|---|
| languages | string | yes | Comma-separated language codes to add (e.g. 'es,fr,de') |
| translate | boolean | – | Whether to auto-translate existing keys to the new languages (default: true) |
No output schema declared.
No examples provided.
i1n_check ~67
Validate local translation files offline: missing keys per language, broken interpolation placeholders, empty values, and coverage. Returns a JSON report. Safe for CI — no API calls.
| Name | Type | Req | Description |
|---|---|---|---|
| minCoverage | number | – | Fail (error-level issue) when overall translation coverage % is below this value |
No output schema declared.
No examples provided.
i1n_extract_and_translate ~84
Accept extracted strings, push them to i1n, translate to all active languages, and pull updated types. Pass an array of {key, value, namespace?} objects.
| Name | Type | Req | Description |
|---|---|---|---|
| languages | string | – | Optional comma-separated target language codes. If omitted, translates to all active languages. |
| strings | array | yes | Array of strings to extract and translate |
No output schema declared.
No examples provided.
i1n_pull ~22
Pull translations from i1n and generate TypeScript types
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
i1n_push ~29
Push local translation files to i1n (with diff detection, only changed keys are pushed)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
i1n_search ~43
Search existing translations by key name, namespace, or source value
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query — matches against key, namespace, and source locale value |
No output schema declared.
No examples provided.
i1n_setup_bridge ~458
Detect any i18n library (i18next, vue-i18n, next-intl, react-intl, etc.) and configure i1n bridge mode in this project — end-to-end, with no terminal needed. Use when the user asks to 'set up / configure the bridge', 'wire up i1n with my existing i18n library', or 'install i1n on top of <library>'. If `i1n.config.json` doesn't exist yet, pass `apiKey` (and optionally `projectId`) and the tool runs init non-interactively (validate, pick project, write config) before wiring the bridge. If `apiKey` is missing, the tool returns status `needs_api_key` so you can ask the user for it. If multiple projects exist, it returns status `multiple_projects` with the list — re-call with the chosen `projectId`. Pass `write=true` to actually write the bridge helper file (do this whenever the user asks to *configure*/*install*; only leave it false if they explicitly asked to *analyze* or *preview*). For libraries outside the known list, the tool still emits a best-effort snippet flagged for verification.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | i1n API key (format: i1n_<32 hex>). Required only when i1n.config.json doesn't exist yet — the tool will run init non-interactively. Ask the user for it the first time; do not invent one. |
| bridgePath | string | – | Path for the bridge helper file. Default: 'src/i18n/i1n-bridge.ts' (or '.js' if no TypeScript detected). |
| overwrite | boolean | – | If true, allow overwriting an existing file at bridgePath. Default: false (refuses to overwrite to avoid clobbering source files). |
| projectId | string | – | UUID of the i1n project to use during init. Only needed when the API key's organization has more than one project. |
| write | boolean | – | If true, writes the bridge helper file to disk (use this when the user asks to *configure*/install). Default: false. |
No output schema declared.
No examples provided.
i1n_status ~23
Get project status including plan, limits, languages, and configuration
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
i1n_translate ~54
Translate to specified languages with AI. Estimates cost, translates, polls for completion, and auto-pulls results.
| Name | Type | Req | Description |
|---|---|---|---|
| languages | string | yes | Comma-separated target language codes (e.g. 'es,fr,de') |
No output schema declared.
No examples provided.
How do I install the io.github.Pakvothe/i1n MCP server?
io.github.Pakvothe/i1n runs locally as an npm package, launched with npx -y i1n. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · i1n
claude mcp add pakvothe-i1n -- npx -y i1n
What is the io.github.Pakvothe/i1n MCP server?
io.github.Pakvothe/i1n is an MCP server listed in the public MCP registry as io.github.Pakvothe/i1n. Agent-complete localization: extract strings, push keys, AI-translate, pull type-safe TS types. This page covers its npm package (i1n).
Is the io.github.Pakvothe/i1n MCP server safe to use?
io.github.Pakvothe/i1n scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 io.github.Pakvothe/i1n MCP server expose?
io.github.Pakvothe/i1n exposes 9 tools: i1n_status, i1n_pull, i1n_push, i1n_check, i1n_translate, and 4 more. Their descriptions and schemas cost roughly 850 tokens of context every time the server is loaded.
Is the io.github.Pakvothe/i1n MCP server still maintained?
io.github.Pakvothe/i1n is still listed as active in the MCP registry. We last reached this channel on 5 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.Pakvothe/i1n MCP server under?
io.github.Pakvothe/i1n declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.