Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/fabkho/the-i18n-kitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/fabkho/the-i18n-kit/claude-code-the-i18n-kit)<a href="https://agentmods.dev/mcp/fabkho/the-i18n-kit/claude-code-the-i18n-kit"><img src="https://agentmods.dev/badge/mcp/fabkho/the-i18n-kit/claude-code-the-i18n-kit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/fabkho/the-i18n-kit/claude-code-the-i18n-kit"><img src="https://agentmods.dev/badge/mcp/fabkho/the-i18n-kit/claude-code-the-i18n-kit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
the-i18n-kit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"the-i18n-kit": {
"command": "npx",
"args": [
"-y",
"@the-i18n-kit/mcp@latest"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today First seen · 9 lines scan A 7f236021dadd
the-i18n-kit is an MCP server published in the GitHub repository fabkho/the-i18n-kit (11 stars, last pushed today), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-11.
Other mcp servers, from other repositories
i18next-mcp-server
A comprehensive Model Context Protocol (MCP) server for i18next translation management, health checking, and automated translation workflows. Runs locally from the i18next-mcp-server npm package.
i18n-tools-mcp
MCP server for managing JSON translation files. Runs locally from the i18n-tools-mcp npm package.
intlayer
Intlayer MCP server. Handle MCP to help IDE to use Intlayer. It build, fill, pull, push, dictionaries. Runs locally from the @intlayer/mcp npm package.
intlayer-sse
MCP server "intlayer-sse", hosted remotely at mcp.intlayer.org, as configured in aymericzip/intlayer.
tolgee
Your app's translations in Tolgee: search keys, create translations, trigger machine translation. Remote server at app.tolgee.io.
zendesk-mcp-server
Draft, translate and update Help Center articles and manage Zendesk tickets from your AI assistant. Runs locally from the @fruggr/zendesk-mcp-server npm package. Needs 1 environment variable to run.