localingos
https://mcp.localingos.com/mcp ↗
Description
AI-powered app translation for developers. Push your source strings, get translations back in 50+ languages automatically. ## What it does Localingos translates your application strings using AI (Amazon Bedrock Claude). Connect your AI assistant to Localingos and manage your entire i18n workflow without leaving your editor. ## Tools - **localingos_sync** — Push source strings and pull translations in one step - **localingos_push** — Push source strings to Localingos - **localingos_get_translations** — Retrieve translations for your project - **localingos_get_translatables** — List all source strings - **localingos_family_members** — List project members - **localingos_add_member** / **localingos_remove_member** — Manage project access - **localingos_billing_status** — Check subscription and usage - **localingos_attach_billing** / **localingos_detach_billing** — Manage billing for projects ## Getting started 1. Sign up at https://localingos.com (free — 5,000 words, no credit card)
What our measurements say
localingos is a remote MCP server published at mcp.localingos.com. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 1,888 ms, a delay an agent will notice. It exposes a broad tool surface of 18 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names like 'localingos_sync' and 'localingos_push' clearly indicate their primary function.
- Billing-related tools (e.g., 'localingos_detach_billing') explicitly describe consequences (e.g., 'Project becomes read-only').
Weaknesses
- Tool names like 'localingos_get_translatables' and 'localingos_get_translations' are functionally similar but not clearly differentiated.
- Descriptions often omit use cases (e.g., 'List translation jobs' lacks context about filtering by state).
- Parameter requirements (required/optional) and types are not specified in the provided schema.
- Overlap between 'localingos_sync' (combined push/pull) and 'localingos_push'/'localingos_get_translations' may confuse agents.
localingos_get_translatables— Name does not clearly distinguish from 'localingos_get_translations'localingos_get_translations— Description lacks context about when to use itlocalingos_detach_billing— No mention of error handling for invalid billing detach attemptslocalingos_delete_translatables— No clarification on required parameters (e.g., foreign IDs)
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'legacy' · transition to legacy era, compliance score initialized
- 2026-09-11T03:50:39.090Z — compliance score set to 100 · indicates full compliance, no smoke test results yet
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 371ms → warm 374ms (penalty 0ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 0.1.0
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/juhsis-localingos)<a href="https://mcpmetrics.io/servers/juhsis-localingos"><img src="https://mcpmetrics.io/badge/juhsis/localingos/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see