An astronaut overseeing a futuristic data hub

Connect i18n Hardcoded String Detector to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Catch un-translated text before it hits production.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 3 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-03

3 capabilities in this set.

Part of 3 available through i18n Hardcoded String Detector.

  1. 01

    Audit strings

    This capability compares discovered strings against your translation dictionary to find mismatches.

  2. 02

    Verify dictionary syntax

    This capability checks your JSON or JS translation files to ensure they are structurally sound.

  3. 03

    Analyze codebase

    This capability scans a specific directory to find all candidate user-facing string literals.

Real work

What teams actually run

01

Pre-release Audits

Run a full scan of your codebase to ensure no hardcoded strings slipped into the UI before a launch.

02

Dictionary Cleanup

Find orphaned keys in your JSON files that are no longer used by any part of the application.

03

Accessibility Compliance

Check aria-label attributes to ensure all accessibility text is properly internationalized.

04

Syntax Verification

Quickly check if a newly updated translation file has valid JSON or JS syntax.

One connector, every AI

i18n Hardcoded String Detector works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put i18n Hardcoded String Detector to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

695ms average. Fast in production.

i18n Hardcoded String Detector is checked daily against the live service.

Daily averagePeak 946ms
Oct 3Today
Fastest day
551ms
Slowest day
946ms
14-day trend
Improving-7%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 3 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of i18n Hardcoded String Detector, so you can see the experience inside your AI.

It does not authenticate your account with i18n Hardcoded String Detector. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

i18n Hardcoded String Detector Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_MnZ7GP6wyVNT1qGzNQAkSfdyJd8ZduAumjbqc3sn/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — i18n Hardcoded String Detector capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "i18n-hardcoded-string-detector-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_MnZ7GP6wyVNT1qGzNQAkSfdyJd8ZduAumjbqc3sn/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up i18n Hardcoded String Detector in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work i18n Hardcoded String Detector owners hand off.

Frontend engineers and localization specialists who need to ensure their UI is ready for global markets.

  • 01

    Frontend Engineer

    You'll use this to catch hardcoded text during development or PR reviews.

  • 02

    QA Engineer

    You can hand this to your agent to audit the codebase for localization readiness.

  • 03

    Localization Manager

    You'll use the audit reports to identify orphaned keys that need cleaning up.

FAQ

Questions i18n Hardcoded String Detector owners ask.

  • 01

    How does this MCP find hardcoded strings?

    It uses Abstract Syntax Tree (AST) parsing to look at the structure of your code and identify text in JSX, HTML, and aria-labels.

  • 02

    What kind of files can it check?

    It can check your source code directories and your JSON or JS translation dictionary files.

  • 03

    Can I use this with Cursor or Claude?

    Yes, you can use this MCP with any MCP-compatible client like Claude, Cursor, or Windsurf.

  • 04

    What is an orphaned key?

    An orphaned key is a translation entry in your dictionary that doesn't match any text found in your codebase.

  • 05

    Does this require me to host anything?

    No, Vinkius hosts and manages the MCP so it is ready to use as soon as you connect your client.

  • 06

    How does the capability identify strings without using regex?

    The capability performs deterministic AST traversal to distinguish between actual UI text nodes and technical identifiers like CSS classes or console logs.

  • 07

    Can I use audit_strings with any translation format?

    Yes, as long as you provide the extracted keys and values from your dictionary to the capability.

  • 08

    What does a 'hardcoded' violation mean?

    A violation is flagged when a string literal found in your UI (via analyze_codebase) does not exist as a key or value in your translation dictionary.

Connect i18n Hardcoded String Detector to Claude, Cursor, ChatGPT & more