Legesher
PYPI · LEGESHER-MCP
Translate Python between English keywords and your language, with round-trip verification.
Available components
Last scanned (5 hours ago)
Scores higher than 63% of PyPI servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs pdm.backend at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 3 of 49 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to legesher/legesher). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1334 tokens (~190/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 77% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/legesher-mcp@0.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | legesher/legesher |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/legesher/legesher/.github/workflows/publish-pypi.yml@refs/heads/main |
| Rekor log index | 3681453631 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:1e2bb6b77ce8f1791371ca3b90eb21ac214c1faa419724722d792eb5086be98b |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | pdm.backend |
Background: Why install scripts are a supply-chain risk →
Dependencies 49 packages
| Packages resolved | 49 |
|---|---|
| Stale | 2 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explain_in_language ~165
Return the engine facts needed to explain code in a language. Deterministic material only — construct-by-construct keyword mappings for the constructs actually present in the code, and a static (compile-only, never executed) validation result. YOU compose the explanation from these facts; the tool never generates prose, so engine truth stays distinct from narration.
| Name | Type | Req | Description |
|---|---|---|---|
| code_lang | string | – | ISO 639 language code from the legesher://languages catalog. |
| explain_in | string | yes | ISO 639 language code from the legesher://languages catalog. |
| include_translation | boolean | – | Also return the source translated into explain_in. |
| python_version | string | – | – |
| source | string | yes | Python source text (a complete file or a fragment). |
| Name | Type | Req | Description |
|---|---|---|---|
| code_lang | string | yes | – |
| constructs | array | yes | – |
| explain_in | string | yes | – |
| python_version | string | yes | – |
| translated_source | – | – | The code translated into explain_in, when requested. |
| validation | – | yes | – |
No examples provided.
lookup_keyword_mapping ~116
Look up how specific terms render in a language. The quick-reference tool: pass English terms for a filtered answer, or omit them for the language's full mapping. For browsing the whole dictionary prefer the legesher://languages/{lang}/terms resource.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | yes | ISO 639 language code from the legesher://languages catalog. |
| python_version | string | – | – |
| terms | – | – | English terms to look up (e.g. ['def', 'print']). Omit for the full mapping. |
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | yes | – |
| mappings | – | yes | – |
| python_version | string | yes | – |
| unmatched_terms | array | – | Requested terms with no entry in any category. |
No examples provided.
map_existing_codebase ~183
Report what translating a codebase into a language would look like. The legibility report: per-file translatability, construct counts, constructs the target language's pack cannot map yet (they stay English after translation), and an aggregate coverage summary. Orchestrates per-file translate + validate; for a large repo, iterate in batches of files across calls.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Files to map. Paths are report labels only — they are content, never logged, never used to touch the filesystem. |
| include_translations | boolean | – | Also return the translated files (default: report only). |
| python_version | string | – | – |
| source_lang | string | – | ISO 639 language code from the legesher://languages catalog. |
| target_lang | string | yes | ISO 639 language code from the legesher://languages catalog. |
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | – |
| python_version | string | yes | – |
| source_lang | string | yes | – |
| summary | – | yes | – |
| target_lang | string | yes | – |
| translated_files | – | – | – |
No examples provided.
translate_to_native ~231
Translate Python source code into the caller's natural language. Accepts complete files and fragments alike — there is no separate snippet mode to choose. When neither language is English the engine pivots through English (packs are authored against English) and the result reports `pivoted: true`. Formatting, comments, identifiers, and string contents are preserved; only keywords, builtins, exceptions, and reserved words are translated.
| Name | Type | Req | Description |
|---|---|---|---|
| python_version | string | – | – |
| source | string | yes | Python source text (a complete file or a fragment). |
| source_lang | string | – | ISO 639 language code from the legesher://languages catalog. |
| target_lang | string | yes | ISO 639 language code from the legesher://languages catalog. |
| verify_round_trip | boolean | – | Also verify the round trip: translate the result back, compare byte-for-byte, and check the canonical form compiles. Use this instead of comparing two renderings yourself — exact comparison over a lo… |
| Name | Type | Req | Description |
|---|---|---|---|
| pivoted | boolean | yes | True when translated via the English pivot (X→en→Y): the engine has no direct X→Y path, so both hops rode language packs and round-trip fidelity depends on both. |
| python_version | string | yes | – |
| round_trip | – | – | Round-trip verification result. Present only when the tool was called with verify_round_trip: true; absent otherwise. |
| source_lang | string | yes | – |
| target_lang | string | yes | – |
| translated_source | string | yes | – |
No examples provided.
translate_to_source ~196
Translate native-language code back to English-keyword Python. The inverse of translate_to_native and the round-trip half of the collaboration story: the output is the form the interpreter, the toolchain, and upstream collaborators use. The target is fixed to English — for a general X→Y translation call translate_to_native with an explicit source_lang.
| Name | Type | Req | Description |
|---|---|---|---|
| python_version | string | – | – |
| source | string | yes | Python source text (a complete file or a fragment). |
| source_lang | string | yes | ISO 639 language code from the legesher://languages catalog. |
| verify_round_trip | boolean | – | Also verify the round trip: translate the result back, compare byte-for-byte, and check the canonical form compiles. Use this instead of comparing two renderings yourself — exact comparison over a lo… |
| Name | Type | Req | Description |
|---|---|---|---|
| pivoted | boolean | yes | True when translated via the English pivot (X→en→Y): the engine has no direct X→Y path, so both hops rode language packs and round-trip fidelity depends on both. |
| python_version | string | yes | – |
| round_trip | – | – | Round-trip verification result. Present only when the tool was called with verify_round_trip: true; absent otherwise. |
| source_lang | string | yes | – |
| target_lang | string | yes | – |
| translated_source | string | yes | – |
No examples provided.
validate_identifier_translations ~262
Check proposed identifier translations before you record them. Packs make keywords deterministic; identifiers have no pack, so this is the guarantee they get instead. Each proposal is checked for a name the pack has reserved, for drift (one concept acquiring a second term) and for collision (one term acquiring a second concept) — against both the existing glossary and the rest of the batch. Returns a verdict per proposal plus ``accepted``, the conflict-free subset as a mapping ready to merge into the project glossary. Recording it is the caller's to do: this server writes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| glossary | – | – | The project's existing identifier translations for this one language, flat: {source_identifier: translation}. If your repo has .legesher/identifier_map.json, that file is nested by language — send th… |
| proposals | array | yes | Proposed identifier translations to check, as source/translation pairs. |
| python_version | string | – | – |
| target_lang | string | yes | ISO 639 language code from the legesher://languages catalog. |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | object | – | The conflict-free proposals as a source -> translation mapping, ready to merge into the project glossary. The caller persists it; this server writes nothing. Both sides are NFC-normalized per the sto… |
| python_version | string | yes | – |
| results | array | yes | – |
| target_lang | string | yes | – |
No examples provided.
How do I install the Legesher MCP server?
Legesher runs locally as a PyPI package, launched with uvx legesher-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · legesher-mcp
claude mcp add legesher-legesher-mcp -- uvx legesher-mcp
What is the Legesher MCP server?
Legesher is an MCP server listed in the public MCP registry as io.github.legesher/legesher-mcp. Translate Python between English keywords and your language, with round-trip verification. This page covers its PyPI package (legesher-mcp).
Is the Legesher MCP server safe to use?
Legesher scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Legesher MCP server expose?
Legesher exposes 6 tools: translate_to_native, translate_to_source, explain_in_language, lookup_keyword_mapping, validate_identifier_translations, map_existing_codebase. Their descriptions and schemas cost roughly 1,153 tokens of context every time the server is loaded.
Is the Legesher MCP server still maintained?
Legesher is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Legesher MCP server under?
Legesher declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.