io.github.fabkho/nuxt-i18n-mcp
NPM · NUXT-I18N-MCP · SCANNED SEP 20
MCP server for managing i18n translations in Nuxt projects.
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 99 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- 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 165 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1632 tokens (~125/item across 13 items; 13 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 Management97
- Stability observed for 29 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_translations" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 13 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.fabkho/nuxt-i18n-mcp server?
io.github.fabkho/nuxt-i18n-mcp runs locally as an npm package, launched with npx -y nuxt-i18n-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 · nuxt-i18n-mcp
claude mcp add fabkho-nuxt-i18n-mcp -- npx -y nuxt-i18n-mcp
{
"mcpServers": {
"fabkho-nuxt-i18n-mcp": {
"command": "npx",
"args": [
"-y",
"nuxt-i18n-mcp"
]
}
}
} {
"servers": {
"fabkho-nuxt-i18n-mcp": {
"command": "npx",
"args": [
"-y",
"nuxt-i18n-mcp"
]
}
}
} codex mcp add fabkho-nuxt-i18n-mcp -- npx -y nuxt-i18n-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fabkho-nuxt-i18n-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"nuxt-i18n-mcp"
],
"enabled": true
}
}
} openclaw mcp add fabkho-nuxt-i18n-mcp --command npx --arg -y --arg nuxt-i18n-mcp
mcp_servers:
fabkho-nuxt-i18n-mcp:
command: "npx"
args: ["-y", "nuxt-i18n-mcp"] {
"McpServers": {
"fabkho-nuxt-i18n-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"nuxt-i18n-mcp"
]
}
}
} assistant mcp add fabkho-nuxt-i18n-mcp -t stdio -c npx -a -y nuxt-i18n-mcp
{
"mcpServers": {
"fabkho-nuxt-i18n-mcp": {
"command": "npx",
"args": [
"-y",
"nuxt-i18n-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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Stability: pass → 0.83 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 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 20 Sept 2026 · Analysed npm/nuxt-i18n-mcp@1.0.1
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 99 packages
| Packages resolved | 99 |
|---|---|
| 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 →
add_translations Add Translations ~101
Add new translation keys to the specified layer. Provide translations per locale file name. Keys are inserted in alphabetical order. Fails if a key already exists (use update_translations instead).
| Name | Type | Req | Description |
|---|---|---|---|
| layer | string | yes | Layer name (e.g., "root", "app-admin") |
| projectDir | string | – | Absolute path to the Nuxt project root. Defaults to server cwd. |
| translations | object | yes | Map of key paths to locale-value pairs |
No output schema declared.
No examples provided.
cleanup_unused_translations Cleanup Unused Translations ~193
Find translation keys not referenced in source code and remove them. Combines find_orphan_keys + remove_translations in one step. Always does a dry run first unless dryRun is explicitly set to false.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | If true (default), only report what would be removed. Set to false to actually delete the keys. |
| excludeDirs | array | – | Additional directory names to skip when scanning (e.g., ["storybook", "__tests__"]). |
| layer | string | – | Layer name to clean up. If omitted, cleans all layers. |
| locale | string | – | Locale code to read keys from for orphan detection. Defaults to the project default locale. |
| projectDir | string | – | Absolute path to the Nuxt project root. Defaults to server cwd. |
| scanDirs | array | – | Directories to scan for source code (absolute paths). Defaults to all layer root directories. |
No output schema declared.
No examples provided.
detect_i18n_config Detect i18n Config ~65
Detect the Nuxt i18n configuration from the project. Returns locales, locale directories, default locale, and fallback chain. Call this first before using other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| projectDir | string | – | Absolute path to the Nuxt project root. Defaults to server cwd. |
No output schema declared.
No examples provided.
find_orphan_keys Find Orphan Translation Keys ~158
Find translation keys that exist in locale JSON files but are not referenced in any Vue/TS source code. Scans a specific layer or all layers. Reports keys that can potentially be removed.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeDirs | array | – | Additional directory names to skip when scanning (e.g., ["storybook", "__tests__"]). |
| layer | string | – | Layer name to check. If omitted, checks all layers. |
| locale | string | – | Locale code to read keys from. Defaults to the project default locale. |
| projectDir | string | – | Absolute path to the Nuxt project root. Defaults to server cwd. |
| scanDirs | array | – | Directories to scan for source code (absolute paths). Defaults to all layer root directories. |
No output schema declared.
No examples provided.
get_missing_translations Get Missing Translations ~118
Find translation keys that exist in the reference locale but are missing in other locales. Scans a specific layer or all layers.
| Name | Type | Req | Description |
|---|---|---|---|
| layer | string | – | Layer name to scan. If omitted, scans all layers. |
| projectDir | string | – | Absolute path to the Nuxt project root. Defaults to server cwd. |
| referenceLocale | string | – | Reference locale code to compare against. Defaults to the project default locale. |
| targetLocales | array | – | Locale codes to check for missing keys. Defaults to all locales except the reference. |
No output schema declared.
No examples provided.
get_translations Get Translations ~123
Get translation values for given key paths from a specific locale and layer. Use "*" as locale to read from all locales.
| Name | Type | Req | Description |
|---|---|---|---|
| keys | array | yes | Dot-separated key paths (e.g., ["common.actions.save"]) |
| layer | string | yes | Layer name (e.g., "root", "app-admin") |
| locale | string | yes | Locale code, file name, or "*" for all locales (e.g., "en", "en-US.json", "*") |
| projectDir | string | – | Absolute path to the Nuxt project root. Defaults to server cwd. |
No output schema declared.
No examples provided.
list_locale_dirs List Locale Directories ~56
List all i18n locale directories in the project, grouped by layer. Shows file count and top-level key namespaces per layer.
| Name | Type | Req | Description |
|---|---|---|---|
| projectDir | string | – | Absolute path to the Nuxt project root. Defaults to server cwd. |
No output schema declared.
No examples provided.
remove_translations Remove Translations ~117
Remove one or more translation keys from ALL locale files in the specified layer. Use dryRun to preview changes before applying them.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | If true, return a preview of changes without writing. Default: false. |
| keys | array | yes | Dot-separated key paths to remove (e.g., ["common.actions.save"]) |
| layer | string | yes | Layer name (e.g., "root", "app-admin") |
| projectDir | string | – | Absolute path to the Nuxt project root. Defaults to server cwd. |
No output schema declared.
No examples provided.
rename_translation_key Rename Translation Key ~145
Rename/move a translation key across ALL locale files in a layer. Preserves the value in every locale. Use dryRun to preview changes before applying them.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | If true, return a preview of changes without writing. Default: false. |
| layer | string | yes | Layer name (e.g., "root", "app-admin") |
| newKey | string | yes | New dot-separated key path (e.g., "common.buttons.save") |
| oldKey | string | yes | Current dot-separated key path (e.g., "common.actions.save") |
| projectDir | string | – | Absolute path to the Nuxt project root. Defaults to server cwd. |
No output schema declared.
No examples provided.
scan_code_usage Scan Code for Translation Key Usage ~140
Scan Vue/TS source files to find where translation keys are referenced. Shows file paths and line numbers for each key. Useful for understanding where a key is used before renaming or removing it.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeDirs | array | – | Additional directory names to skip (e.g., ["storybook", "__tests__"]). |
| keys | array | – | Specific dot-path keys to search for. If omitted, returns all key usages found in code. |
| projectDir | string | – | Absolute path to the Nuxt project root. Defaults to server cwd. |
| scanDirs | array | – | Directories to scan (absolute paths). Defaults to all layer root directories. |
No output schema declared.
No examples provided.
search_translations Search Translations ~122
Search translation files by key pattern (glob/regex) or value substring. Useful for finding existing translations before adding duplicates.
| Name | Type | Req | Description |
|---|---|---|---|
| layer | string | – | Layer to search in. If omitted, searches all layers. |
| locale | string | – | Locale to search in. If omitted, searches all locales. |
| projectDir | string | – | Absolute path to the Nuxt project root. Defaults to server cwd. |
| query | string | yes | Search query — matched against keys and/or values |
| searchIn | string | – | Where to search. Default: "both" |
No output schema declared.
No examples provided.
translate_missing Translate Missing ~198
Find keys missing in target locales and translate them. Uses the host LLM via MCP sampling if available, otherwise returns context for the agent to translate inline. Uses project config (glossary, translation prompt, locale notes, examples) if available.
| Name | Type | Req | Description |
|---|---|---|---|
| batchSize | number | – | Max keys per sampling request. Default: 50. |
| dryRun | boolean | – | If true, return what would be translated without writing. Default: false. |
| keys | array | – | Specific keys to translate. If omitted, translates all missing keys. |
| layer | string | yes | Layer name to translate (e.g., "root", "app-admin") |
| projectDir | string | – | Absolute path to the Nuxt project root. Defaults to server cwd. |
| referenceLocale | string | – | Reference locale code. Defaults to the project default locale. |
| targetLocales | array | – | Locale codes to translate into. Defaults to all locales except the reference. |
No output schema declared.
No examples provided.
update_translations Update Translations ~96
Update existing translation keys in the specified layer. Provide new values per locale file name. Fails if a key does not exist (use add_translations instead).
| Name | Type | Req | Description |
|---|---|---|---|
| layer | string | yes | Layer name (e.g., "root", "app-admin") |
| projectDir | string | – | Absolute path to the Nuxt project root. Defaults to server cwd. |
| translations | object | yes | Map of key paths to locale-value pairs |
No output schema declared.
No examples provided.
What is the io.github.fabkho/nuxt-i18n-mcp server?
io.github.fabkho/nuxt-i18n-mcp is listed in the public MCP registry as io.github.fabkho/nuxt-i18n-mcp. MCP server for managing i18n translations in Nuxt projects. This page covers its npm package (nuxt-i18n-mcp).
Is the io.github.fabkho/nuxt-i18n-mcp server safe to use?
io.github.fabkho/nuxt-i18n-mcp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.fabkho/nuxt-i18n-mcp server expose?
io.github.fabkho/nuxt-i18n-mcp exposes 13 tools: detect_i18n_config, list_locale_dirs, get_translations, add_translations, update_translations, and 8 more. Their descriptions and schemas cost roughly 1,632 tokens of context every time the server is loaded.
Is the io.github.fabkho/nuxt-i18n-mcp server still maintained?
io.github.fabkho/nuxt-i18n-mcp is still listed as active in the MCP registry. We last reached this channel on 20 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.fabkho/nuxt-i18n-mcp server under?
io.github.fabkho/nuxt-i18n-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.