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/aymericzip/intlayerWrote 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/aymericzip/intlayer/intlayer-sse)<a href="https://agentmods.dev/mcp/aymericzip/intlayer/intlayer-sse"><img src="https://agentmods.dev/badge/mcp/aymericzip/intlayer/intlayer-sse/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/aymericzip/intlayer/intlayer-sse"><img src="https://agentmods.dev/badge/mcp/aymericzip/intlayer/intlayer-sse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
intlayer-sse 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
{
"intlayer-sse": {
"transport": "sse",
"url": "https://mcp.intlayer.org"
}
}What else mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 6 lines scan A 823a778bb047
intlayer-sse is an MCP server published in the GitHub repository aymericzip/intlayer (856 stars, last pushed yesterday), licensed Apache-2.0. 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-06.
Other mcp servers, from other repositories
mastra
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 1 environment variable to run.
i1n
Agent-complete localization: extract strings, push keys, AI-translate, pull type-safe TS types. Runs locally from the i1n npm package.
next-devtools
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
the-i18n-kit
Let your AI agent manage translations — find orphans, translate missing keys, add languages. Works with Cursor, Claude, VS Code. Supports Nuxt, Laravel, Vue, React/Next.js, and any framework. Runs locally from the @the-i18n-kit/mcp npm package.
deepl-i18n
DeepL-first translation of localization files (JSON, YAML, .arb, .strings, .properties, Android XML, CSV, gettext), with placeholder-safety, a web UI, an MCP server and a local-LLM fallback. Runs locally from the deepl-i18n Python package.
electron-live-i18n
MCP server "electron-live-i18n" as configured in dee0917/electron-live-i18n. Runs locally from the electron-live-i18n Python package.