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/translated/lara-mcpWrote 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/translated/lara-mcp/lara-translate)<a href="https://agentmods.dev/mcp/translated/lara-mcp/lara-translate"><img src="https://agentmods.dev/badge/mcp/translated/lara-mcp/lara-translate/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/translated/lara-mcp/lara-translate"><img src="https://agentmods.dev/badge/mcp/translated/lara-mcp/lara-translate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lara-translate 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 10d 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
{
"lara-translate": {
"type": "http",
"url": "https://mcp-v2.laratranslate.com/v1"
}
}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.
- 10d ago First seen · 6 lines scan A 3e6ebefd8f85
lara-translate is an MCP server published in the GitHub repository translated/lara-mcp (97 stars, last pushed 5d 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-30.
Other mcp servers, from other repositories
unity-info-mcp
Standalone MCP server for Unity runtime inspection (modding/localization workflows). Runs locally from the unity-info-mcp Python package.
aigc-humanizer-zh
MCP server "aigc-humanizer-zh" as configured in shuohui-air-technology/aigc-humanizer-zh. Runs locally from the aigc-humanizer-zh Python package.
ai-l10n-mcp
MCP Server that turns your AI agent into a localization expert with token-efficient i18n translation. Runs locally from the ai-l10n-mcp npm package. Needs 1 environment variable to run.
crowdin
MCP server for Crowdin — projects, files, strings, translation progress, tasks, and members. Remote server at crowdin.usefulapi.io.
timezone-mcp
IANA timezone conversions with real DST rules. Runs locally from the @mukundakatta/timezone-mcp npm 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.