# Regex-LE (npm · regex-le-mcp)

Extract regular expressions from code, each with a ReDoS safety verdict.

- Trust score: 75/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-15

## Components

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

## Channel facts

- Registry: `npm`
- Package: `regex-le-mcp`
- Version: `2.3.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-08-15.

- **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 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 238 tokens (~238/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**: 30/100
  - Stability observed for 9 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "nolindnaidoo-regex-le": {
      "command": "npx",
      "args": [
        "-y",
        "regex-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-08-15 (score 75, +1)

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

### 2026-08-14 (score 74, +1)

- [security regression] Stability: 0.23 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Schema quality: pass → fail
- [functional] Package version: 2.2.4 → 2.3.0

### 2026-08-11 (score 73, +2)

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

### 2026-08-09 (score 71, +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-08-08 (score 70, +31)

- [functional improvement] Stability: unverified → 0.07
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] Package version: 2.2.2 → 2.2.4

### 2026-08-07 (score 39, −30)

- [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] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] Package version: 2.2.2 → 2.2.4

### 2026-08-06 (score 69, +30)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-08-05 (score 39)

First indexed and scored.

## MCP tools (1)

### `extract_patterns` (~238 tokens)

Extract every regular expression from source code — JavaScript and TypeScript literals and RegExp constructors, and the call sites Python, Rust, Go, Java, Ruby, PHP and C# write a pattern at — with its flags, 1-based position, and a ReDoS verdict saying whether the pattern can be driven into catastrophic backtracking. Duplicate pattern-and-flags pairs are reported once, at first occurrence: the output is a pattern list, not an occurrence list.

Input parameters:

- `content` (string, required): The source text to scan.
- `filename` (string): Filename used to infer the language when `format` is absent, e.g. "validate.py".
- `format` (string): Language of the document, so only its own spellings are looked for: javascript, typescript, python, rust, go, java, ruby, php, csharp. Common extensions and aliases are accepted. Optional — with no l…
- `maxResults` (integer): Cap on returned patterns (default 500). meta.truncated reports whether any were dropped.

## Diagnostics

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

## Score history

- 2026-08-15: 75
- 2026-08-14: 74
- 2026-08-13: 73
- 2026-08-12: 73
- 2026-08-11: 73
- 2026-08-10: 71
- 2026-08-09: 71
- 2026-08-08: 70
- 2026-08-07: 39
- 2026-08-06: 69
- 2026-08-05: 39

## Links

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