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/Pakvothe/i1n-cliWrote 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/pakvothe/i1n-cli/i1n)<a href="https://agentmods.dev/mcp/pakvothe/i1n-cli/i1n"><img src="https://agentmods.dev/badge/mcp/pakvothe/i1n-cli/i1n/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/pakvothe/i1n-cli/i1n"><img src="https://agentmods.dev/badge/mcp/pakvothe/i1n-cli/i1n.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
i1n 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 1mo ago.
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
{
"i1n": {
"command": "npx",
"args": [
"-y",
"i1n"
],
"env": {}
}
}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.
- 1mo ago First seen · 10 lines scan A 7b77afe11ae6
i1n is an MCP server published in the GitHub repository Pakvothe/i1n-cli (2 stars, last pushed 8d ago), 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-08-31.
Other mcp servers, from other repositories
shipi18n
Translation QA for locale files: keyless validators, semantic review and BYO-key translation. Runs locally from the @shipi18n/mcp npm package. Needs 2 environment variables to run.
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.
i18n-tools-mcp
MCP server for managing JSON translation files. Runs locally from the i18n-tools-mcp npm package.
apitype
Generate TypeScript types, Zod schemas, TypeBox, and JSON Schema from any API endpoint or JSON — instantly. Works as a CLI, MCP server, Vite plugin, and GitHub Action. Runs locally from the @jayeshbansal/apitype npm package.