A-

mcp.lingo.dev

Item: mcp.lingo.dev
Rating: 90
Author: wmcp.sh

https://mcp.lingo.dev/main

90/100 · MCP Trust Grade · checked 6h ago · MCP 2025-06-18

✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 4 tools · Developer Tools

get_project_context

Captures the user's project architecture to inform i18n implementation strategy. ## When to Use **Called during i18n_checklist Step 1.** The checklist

get_framework_docs

Retrieves authoritative documentation directly from the framework's official repository. ## When to Use **Called during i18n_checklist Steps 1-13.** T

get_i18n_library_docs

Retrieves authoritative documentation for i18n libraries (currently react-intl). ## When to Use **Called during i18n_checklist Steps 7-10.** The check

i18n_checklist

## ⚠️ MANDATORY TOOL FOR ALL I18N WORK ⚠️ THIS IS NOT OPTIONAL. This tool is REQUIRED for any internationalization, localization, or multi-language im

Spec conformance20%100

✓ initialize → protocolVersion 2025-06-18
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 4 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

4 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%70

single-probe latency 2017ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%80

100% of tools have typed inputSchema
0/4 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%90

HTTPS ✓
RFC 9728 oauth-protected-resource metadata ✓
advertises protocol 2025-06-18

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade mcp.lingo.dev on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — mcp.lingo.dev grade A-

Share on X Open card image

https://wmcp.sh/mcp/grade/mcp.lingo.dev

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade A-](https://wmcp.sh/mcp/grade/mcp.lingo.dev/badge.svg)](https://wmcp.sh/mcp/grade/mcp.lingo.dev)

HTML

<a href="https://wmcp.sh/mcp/grade/mcp.lingo.dev"><img src="https://wmcp.sh/mcp/grade/mcp.lingo.dev/badge.svg" alt="MCP Trust Grade A- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.