Unicode-LE
NPM · UNICODE-LE-MCP
Find the Unicode that hides meaning: bidi controls, invisibles, homoglyphs and mixed scripts.
Available components
Last scanned (4 hours ago)
Scores higher than 66% of npm servers
Category Security
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 358 tokens (~358/item across 1 items; 1 tools + 0 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 Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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
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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +35
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.37 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 1.0.0 → 1.1.0 functional
- 12 Oct 26 −30
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 1.0.0 → 1.1.0 functional
- 3 Oct 26 69
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 25 Oct 2026 · Analysed npm/unicode-le-mcp@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
detect_unicode_risks ~358
Find the Unicode characters in a document that hide meaning: bidirectional controls (the Trojan Source class, CVE-2021-42574), invisible characters, homoglyphs, words that mix scripts, text that is not in NFC, spaces that are not the space, and unassigned or private-use codepoints. Each finding carries a 1-based line and column, a byte offset, the codepoints as U+XXXX, the script and a severity. It never returns the offending characters themselves, and never rewrites anything. A document plainly written in a non-Latin script is not judged for homoglyphs unless that script is named in `scripts`; it says so in `refusals` rather than guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The document text to scan. |
| filename | string | – | The document's name, as an alternative to `format`. Only its extension is read, and nothing is opened. |
| format | string | – | The document's format, so each finding can carry the key path that names where it sits. Omit it and findings carry a line and column only; an unrecognised name costs the key paths and never a finding. |
| kinds | array | – | Report only these kinds. Omit for all of them, which is the only setting under which an empty result means clean. |
| maxResults | integer | – | Cap on returned findings (default 500). meta.truncated reports whether any were dropped. |
| scripts | array | – | Non-Latin scripts this document is expected to be written in, by Unicode name or ISO 15924 tag, e.g. Han or Cyrillic. Naming them is what allows the homoglyph check to run on a translated document. |
No output schema declared.
No examples provided.
How do I install the Unicode-LE MCP server?
Unicode-LE runs locally as an npm package, launched with npx -y unicode-le-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · unicode-le-mcp
claude mcp add nolindnaidoo-unicode-le -- npx -y unicode-le-mcp
What is the Unicode-LE MCP server?
Unicode-LE is an MCP server listed in the public MCP registry as io.github.nolindnaidoo/unicode-le. Find the Unicode that hides meaning: bidi controls, invisibles, homoglyphs and mixed scripts. This page covers its npm package (unicode-le-mcp).
Is the Unicode-LE MCP server safe to use?
Unicode-LE scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 October 2026. It declares no install or post-install scripts. 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 Unicode-LE MCP server expose?
Unicode-LE exposes 1 tool: detect_unicode_risks. Their descriptions and schemas cost roughly 358 tokens of context every time the server is loaded.
Is the Unicode-LE MCP server still maintained?
Unicode-LE is still listed as active in the MCP registry. We last reached this channel on 25 October 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 Unicode-LE MCP server under?
Unicode-LE declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.