# dev.lingo/main (remote · mcp.lingo.dev)

Lingo.dev MCP Server - World-class i18n implementation with ICU MessageFormat.

- Trust score: 57/100 (low)
- Change this week: +9
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.lingo.dev`: 57/100 (this document), [markdown](https://verifymcp.io/servers/dev-lingo-main/main.md), [page](https://verifymcp.io/servers/dev-lingo-main/main)

## Channel facts

- Endpoint: `https://mcp.lingo.dev/main`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 19/100
  - AI-judged instruction clarity (poor).
  - Context-footprint check failed: tool/resource definitions use about 3035 tokens (~758/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 29% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http dev-lingo-main https://mcp.lingo.dev/main
```

### Codex

```toml
[mcp_servers.dev-lingo-main]
url = "https://mcp.lingo.dev/main"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-lingo-main": {
      "type": "remote",
      "url": "https://mcp.lingo.dev/main",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-lingo-main --url https://mcp.lingo.dev/main --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-lingo-main:
    url: "https://mcp.lingo.dev/main"
```

### Other

```json
{
  "mcpServers": {
    "dev-lingo-main": {
      "type": "http",
      "url": "https://mcp.lingo.dev/main"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 55, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 50, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 50, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 48, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 48)

First indexed and scored.

## MCP tools (4)

### `get_project_context` (~453 tokens)

Captures the user's project architecture to inform i18n implementation strategy.

\## When to Use

\**Called during i18n_checklist Step 1.**

The checklist tool will tell you when to call this. If you're implementing i18n:
1\. Call i18n_checklist(step_number=1, done=false) FIRST
2\. The checklist will instruct you to call THIS tool
3\. Then use the results for subsequent steps

Do NOT call this before calling the checklist tool

\## Why This Matters

Frameworks handle i18n through completely different mechanisms. The same outcome (locale-aware routing) requires different code for Next.js vs TanStack Start vs React Router. Without accurate detection, you'll implement patterns that don't work.

\## How to Use

1\. Examine the user's project files (package.json, directories, config files)
2\. Identify framework markers and version
3\. Construct a detectionResults object matching the schema
4\. Call this tool with your findings
5\. Store the returned framework identifier for get_framework_docs calls

The schema requires:
\- framework: Exact variant (nextjs-app-router, nextjs-pages-router, tanstack-start, react-router)
\- majorVersion: Specific version number (13-16 for Next.js, 1 for TanStack Start, 7 for React Router)
\- sourceDirectory, hasTypeScript, packageManager
\- Any detected locale configuration
\- Any detected i18n library (currently only react-intl supported)

\## What You Get

Returns the framework identifier needed for documentation fetching. The 'framework' field in the response is the exact string you'll use with get_framework_docs.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `detectionResults` (required)

### `get_framework_docs` (~486 tokens)

Retrieves authoritative documentation directly from the framework's official repository.

\## When to Use

\**Called during i18n_checklist Steps 1-13.**

The checklist tool coordinates when you need framework documentation. Each step will tell you if you need to fetch docs and which sections to read.

If you're implementing i18n: Let the checklist guide you. Don't call this independently

\## Why This Matters

Your training data is a snapshot. Framework APIs evolve. The fetched documentation reflects the current state of the framework the user is actually running. Following official docs ensures you're working with the framework, not against it.

\## How to Use

\**Two-Phase Workflow:**

1\. **Discovery** - Call with action="index" to see available sections
2\. **Reading** - Call with action="read" and section_id to get full content

\**Parameters:**
\- framework: Use the exact value from get_project_context output
\- version: Use "latest" unless you need version-specific docs
\- action: "index" or "read"
\- section_id: Required for action="read", format "fileIndex:headingIndex" (from index)

\**Example Flow:**
\```
// See what's available
get_framework_docs(framework="nextjs-app-router", action="index")

// Read specific section
get_framework_docs(framework="nextjs-app-router", action="read", section_id="0:2")
\```

\## What You Get

\- **Index**: Table of contents with section IDs
\- **Read**: Full section with explanations and code examples

Use these patterns directly in your implementation.

Input parameters:

- `action` (string)
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `framework` (string, required)
- `section_id` (string): Required if action='read'. Format: 'fileIndex:headingIndex'
- `version` (string)

### `get_i18n_library_docs` (~426 tokens)

Retrieves authoritative documentation for i18n libraries (currently react-intl).

\## When to Use

\**Called during i18n_checklist Steps 7-10.**

The checklist tool will tell you when you need i18n library documentation. Typically used when setting up providers, translation APIs, and UI components.

If you're implementing i18n: Let the checklist guide you. It will tell you when to fetch library docs

\## Why This Matters

Different i18n libraries have different APIs and patterns. Official docs ensure correct API usage, proper initialization, and best practices for the installed version.

\## How to Use

\**Two-Phase Workflow:**

1\. **Discovery** - Call with action="index"
2\. **Reading** - Call with action="read" and section_id

\**Parameters:**
\- library: Currently only "react-intl" supported
\- version: Use "latest"
\- action: "index" or "read"
\- section_id: Required for action="read"

\**Example:**
\```
get_i18n_library_docs(library="react-intl", action="index")
get_i18n_library_docs(library="react-intl", action="read", section_id="0:3")
\```

\## What You Get

\- **Index**: Available documentation sections
\- **Read**: Full API references and usage examples

Input parameters:

- `action` (string)
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `library` (string, required)
- `section_id` (string)
- `version` (string)

### `i18n_checklist` (~1670 tokens)

\## ⚠️ MANDATORY TOOL FOR ALL I18N WORK ⚠️

THIS IS NOT OPTIONAL. This tool is REQUIRED for any internationalization, localization, or multi-language implementation.

\## When to Use (MANDATORY)

\**ALWAYS use this tool when the user says ANY of these phrases:**

\- "set up i18n"
\- "add internationalization"
\- "implement localization"
\- "support multiple languages"
\- "add translations"
\- "make my app multilingual"
\- "add French/Spanish/etc support"
\- "implement i18n"
\- "configure internationalization"
\- "add locale support"
\- ANY request about supporting multiple languages

\**Recognition Pattern:**
\```
User message contains: [i18n, internationalization, localization, multilingual, translations, locale, multiple languages]
→ YOU MUST call this tool as your FIRST ACTION
→ DO NOT explore the codebase first
→ DO NOT call other tools first
→ DO NOT plan the implementation first
→ IMMEDIATELY call: i18n_checklist(step_number=1, done=false)
\```

\## Why This is Mandatory

Without this tool, you will:
❌ Miss critical integration points (80% failure rate)
❌ Implement steps out of order (causes cascade failures)
❌ Use patterns that don't work for the framework
❌ Create code that compiles but doesn't function
❌ Waste hours debugging preventable issues

This tool is like Anthropic's "think" tool - it forces structured reasoning and prevents catastrophic mistakes.

\## The Forcing Function

You CANNOT proceed to step N+1 without completing step N.
You CANNOT mark a step complete without providing evidence.
You CANNOT skip the build check for steps 2-13.

This is by design. The tool prevents you from breaking the implementation.

\## How It Works

This tool gives you ONE step at a time:
1\. Shows exactly what to implement
2\. Tells you which docs to fetch
3\. Waits for concrete evidence
4\. Validates your build passes
5\. Unlocks the next step only when ready

You don't need to understand all 13 steps upfront. Just follow each step as it's given.

\## FIRST CALL (Start Here)

When user reque…

Input parameters:

- `build_passing` (boolean)
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `done` (boolean, required)
- `evidence` (array)
- `step_number` (integer, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-lingo-main/main#diagnostics

## Score history

- 2026-08-03: 57
- 2026-08-02: 56
- 2026-08-01: 56
- 2026-07-31: 55
- 2026-07-30: 50
- 2026-07-29: 50
- 2026-07-28: 49
- 2026-07-27: 48
- 2026-07-26: 48

## Links

- Remote endpoint: https://mcp.lingo.dev/main
- Changelog RSS feed: https://verifymcp.io/servers/dev-lingo-main/main/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-lingo-main/main/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dev-lingo-main/main