Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.hepter/i18n-codelens-mcp

NPM · I18N-CODELENS-MCP · SCANNED SEP 20

Inspect, audit and safely edit i18n locale JSON files from AI agents.

Available components

+4 this week 79 Trust /100
Trust breakdown (7 categories)

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
  • 12 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability81
  • 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 1517 tokens (~151/item across 10 items; 10 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 Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.hepter/i18n-codelens-mcp server?

io.github.hepter/i18n-codelens-mcp runs locally as an npm package, launched with npx -y i18n-codelens-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 · i18n-codelens-mcp

# add to Claude Code
claude mcp add hepter-i18n-codelens-mcp -- npx -y i18n-codelens-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "hepter-i18n-codelens-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "i18n-codelens-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hepter-i18n-codelens-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "i18n-codelens-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add hepter-i18n-codelens-mcp -- npx -y i18n-codelens-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hepter-i18n-codelens-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "i18n-codelens-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hepter-i18n-codelens-mcp --command npx --arg -y --arg i18n-codelens-mcp
# ~/.hermes/config.yaml
mcp_servers:
  hepter-i18n-codelens-mcp:
    command: "npx"
    args: ["-y", "i18n-codelens-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hepter-i18n-codelens-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "i18n-codelens-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add hepter-i18n-codelens-mcp -t stdio -c npx -a -y i18n-codelens-mcp
// mcp.json
{
  "mcpServers": {
    "hepter-i18n-codelens-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "i18n-codelens-mcp"
      ]
    }
  }
}
Changelog

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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 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.

  • 12 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.

  • 11 Sept 26 +3
    • Stability: unverified → 0.27 functional
  • 3 Sept 26 71

    First indexed and scored.

Diagnostics

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/i18n-codelens-mcp@2.0.0

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 23 packages
Packages resolved 23
Stale 12
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~1,193 tokens

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 →

Tool Tokens
i18n_audit ~160

Project-wide health check: keys missing in some locale (vs the base locale), placeholder mismatches, keys used in code but untranslated, and keys never referenced in code. Choose checks to keep the response small.

NameTypeReqDescription
baseLocalestringReference locale (default: first locale).
checksarraySubset of missing, placeholders, code, unused. Default all.
includeReferencesbooleanAttach code locations to untranslated keys.
limitnumberMax items to return (default 50).
localesarrayLocale tags to include, e.g. ['en','tr']. Default: all.
workspaceDirstringSub-directory of the workspace root to operate on. Usually omitted.

No output schema declared.

No examples provided.

i18n_delete_keys ~101

Remove keys from all or selected locales. Previews by default; pass dryRun:false to delete (or confirm the dialog).

NameTypeReqDescription
dryRunbooleanDefault true (preview). false deletes.
keysarrayyes
localesarrayLocale tags to include, e.g. ['en','tr']. Default: all.
workspaceDirstringSub-directory of the workspace root to operate on. Usually omitted.

No output schema declared.

No examples provided.

i18n_file_keys ~92

Translation keys referenced in one source file and the locales that lack each of them. Run after editing a component to verify its copy is complete.

NameTypeReqDescription
filePathstringyesWorkspace-relative or absolute path of a source file.
includeCompletebooleanDefault false: only count fully translated keys.
workspaceDirstringSub-directory of the workspace root to operate on. Usually omitted.

No output schema declared.

No examples provided.

i18n_format_resources ~106

Normalize JSON formatting and sort keys (top level only for mixed files). Previews by default; pass dryRun:false to rewrite.

NameTypeReqDescription
dryRunbooleanDefault true (preview). false rewrites.
localesarrayLocale tags to include, e.g. ['en','tr']. Default: all.
sortKeysbooleanDefault true.
workspaceDirstringSub-directory of the workspace root to operate on. Usually omitted.

No output schema declared.

No examples provided.

i18n_get_translations ~162

Values of specific keys in every (or selected) locale; null marks a missing translation. A key ending with '.' returns the whole namespace. Use includeValues:false for presence only.

NameTypeReqDescription
includeValuesbooleanDefault true. False returns the locales holding each key.
keysarrayyesExact keys, or namespaces ending with '.' (e.g. 'nav.').
limitnumberMax items to return (default 50).
localesarrayLocale tags to include, e.g. ['en','tr']. Default: all.
maxValueCharsnumberTruncate values (default 160).
workspaceDirstringSub-directory of the workspace root to operate on. Usually omitted.

No output schema declared.

No examples provided.

i18n_key_references ~81

Where keys are used in code, as path:line:column, with exact totals. Useful before renaming or deleting a key.

NameTypeReqDescription
keysarrayyes
limitnumberMax locations per key (default 25).
workspaceDirstringSub-directory of the workspace root to operate on. Usually omitted.

No output schema declared.

No examples provided.

i18n_project_info ~58

Locales, key format (plain or namespace:key), key counts, resolved config and warnings. Call once per session before other tools.

NameTypeReqDescription
workspaceDirstringSub-directory of the workspace root to operate on. Usually omitted.

No output schema declared.

No examples provided.

i18n_rename_key ~139

Rename a key across locales, or move a whole namespace when from ends with '.' (e.g. 'nav.' -> 'menu.'). Refuses when a target exists. Previews by default; pass dryRun:false to apply.

NameTypeReqDescription
dryRunbooleanDefault true (preview). false applies.
fromstringyesKey, or namespace prefix ending with '.'.
localesarrayLocale tags to include, e.g. ['en','tr']. Default: all.
tostringyes
workspaceDirstringSub-directory of the workspace root to operate on. Usually omitted.

No output schema declared.

No examples provided.

i18n_search_keys ~183

Find keys by substring of the key or the translated text, optionally under a key prefix. Keys missing from some locales are marked with "in". Add includeValues to see the text.

NameTypeReqDescription
caseSensitiveboolean
includeValuesbooleanDefault false.
keyPrefixstringOnly keys starting with this prefix, e.g. 'component.chat.'.
limitnumberMax items to return (default 50).
localesarrayLocale tags to include, e.g. ['en','tr']. Default: all.
maxValueCharsnumber
querystringSubstring to look for (case-insensitive by default).
searchInstringDefault both.
workspaceDirstringSub-directory of the workspace root to operate on. Usually omitted.

No output schema declared.

No examples provided.

i18n_upsert_translations ~111

Create or update keys in one call, with a value per locale. Writes immediately and never deletes keys. An existing value that differs is reported as a conflict unless overwrite:true. Reports missing locales and placeholder mismatches.

NameTypeReqDescription
dryRunbooleanPreview only (default false).
entriesarrayyes
overwritebooleanReplace values that already differ (default false).
workspaceDirstringSub-directory of the workspace root to operate on. Usually omitted.

No output schema declared.

No examples provided.

Common questions

What is the io.github.hepter/i18n-codelens-mcp server?

io.github.hepter/i18n-codelens-mcp is listed in the public MCP registry as io.github.hepter/i18n-codelens-mcp. Inspect, audit and safely edit i18n locale JSON files from AI agents. This page covers its npm package (i18n-codelens-mcp).

Is the io.github.hepter/i18n-codelens-mcp server safe to use?

io.github.hepter/i18n-codelens-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.hepter/i18n-codelens-mcp server expose?

io.github.hepter/i18n-codelens-mcp exposes 10 tools: i18n_project_info, i18n_get_translations, i18n_search_keys, i18n_file_keys, i18n_key_references, and 5 more. Their descriptions and schemas cost roughly 1,193 tokens of context every time the server is loaded.

Is the io.github.hepter/i18n-codelens-mcp server still maintained?

io.github.hepter/i18n-codelens-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.hepter/i18n-codelens-mcp server under?

io.github.hepter/i18n-codelens-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.