# Unicode-LE (npm · unicode-le-mcp)

Find the Unicode that hides meaning: bidi controls, invisibles, homoglyphs and mixed scripts.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- npm · `unicode-le-mcp`: 79/100 (this document), [markdown](https://verifymcp.io/servers/nolindnaidoo-unicode-le/unicode-le-mcp.md), [page](https://verifymcp.io/servers/nolindnaidoo-unicode-le/unicode-le-mcp)

## Channel facts

- Registry: `npm`
- Package: `unicode-le-mcp`
- Version: `1.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add nolindnaidoo-unicode-le -- npx -y unicode-le-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "nolindnaidoo-unicode-le": {
      "command": "npx",
      "args": [
        "-y",
        "unicode-le-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nolindnaidoo-unicode-le": {
      "command": "npx",
      "args": [
        "-y",
        "unicode-le-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add nolindnaidoo-unicode-le -- npx -y unicode-le-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nolindnaidoo-unicode-le": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "unicode-le-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nolindnaidoo-unicode-le --command npx --arg -y --arg unicode-le-mcp
```

### Hermes

```yaml
mcp_servers:
  nolindnaidoo-unicode-le:
    command: "npx"
    args: ["-y", "unicode-le-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "nolindnaidoo-unicode-le": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "unicode-le-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add nolindnaidoo-unicode-le -t stdio -c npx -a -y unicode-le-mcp
```

### Other

```json
{
  "mcpServers": {
    "nolindnaidoo-unicode-le": {
      "command": "npx",
      "args": [
        "-y",
        "unicode-le-mcp"
      ]
    }
  }
}
```

## 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-10-24 (score 79, +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.

### 2026-10-22 (score 78, +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.

### 2026-10-20 (score 77, +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.

### 2026-10-17 (score 76, +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.

### 2026-10-15 (score 75, +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.

### 2026-10-14 (score 74, +35)

- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.37
- [functional improvement] MCP protocol: unverified → pass
- [functional] Package version: 1.0.0 → 1.1.0

### 2026-10-12 (score 39, −30)

- [security regression] 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.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.0.0 → 1.1.0

### 2026-10-03 (score 69)

First indexed and scored.

## MCP tools (1)

### `detect_unicode_risks` (~358 tokens)

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.

Input parameters:

- `content` (string, required): 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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/nolindnaidoo-unicode-le/unicode-le-mcp#diagnostics

## Score history

- 2026-10-25: 79
- 2026-10-24: 79
- 2026-10-23: 78
- 2026-10-22: 78
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 76
- 2026-10-18: 76
- 2026-10-17: 76
- 2026-10-16: 75
- 2026-10-15: 75
- 2026-10-14: 74
- 2026-10-13: 39
- 2026-10-12: 39
- 2026-10-04: 69
- 2026-10-03: 69

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/unicode-le-mcp
- Socket report: https://socket.dev/npm/package/unicode-le-mcp
- Repository: https://github.com/nolindnaidoo/unicode-le
- Website: https://letools.dev/tools/unicode-le
- Changelog RSS feed: https://verifymcp.io/servers/nolindnaidoo-unicode-le/unicode-le-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/nolindnaidoo-unicode-le/unicode-le-mcp.json
- HTML version of this page: https://verifymcp.io/servers/nolindnaidoo-unicode-le/unicode-le-mcp