Developer · Local MCP server
Regex-LE
Extract regular expressions from code, each with a ReDoS safety verdict.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.nolindnaidoo/regex-le- Version
- 2.5.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- nolindnaidoo (GitHub) · 11 servers with pages here
- Website
- letools.dev/tools/regex-le
- Repository
- github.com/nolindnaidoo/regex-le
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | regex-le-mcp | 2.5.1 | stdio |
How to connect Regex-LE
Regex-LE runs locally from a Node.js package published to the npm registry: regex-le-mcp version 2.5.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y regex-le-mcp@2.5.1.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"regex-le": {
"command": "npx",
"args": [
"-y",
"regex-le-mcp@2.5.1"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from nolindnaidoo (GitHub)
| Server | Runs |
|---|---|
| Colors-LEExtract colors from stylesheets and code, with their notation and position. | Local · stdio |
| Dates-LEExtract dates and timestamps from logs, data files and code, with their format and position. | Local · stdio |
| EnvSync-LECompare dotenv files and report which keys are missing or extra, by name only. | Local · stdio |
| Numbers-LEExtract numeric values from config files, data files and plain text. | Local · stdio |
| Paths-LEExtract file and directory paths from config files and code, with their kind and position. | Local · stdio |
| Scrape-LEAnalyse robots.txt content and report whether a path may be crawled. | Local · stdio |
| Secrets-LEDetect hardcoded secrets in source and config. Reports masked previews, never the values. | Local · stdio |
| Strings-LEExtract string values from config files, data files and plain text. | Local · stdio |
| Unicode-LEFind the Unicode that hides meaning: bidi controls, invisibles, homoglyphs and mixed scripts. | Local · stdio |
| URLs-LEExtract URLs from documentation, configuration and code, with their protocol and position. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| Ref Tools Ref Tools MCPProvide your AI coding tools with token-efficient access to up-to-date technical documentation for… | Remote · HTTP |
| Refactoring MCP ServerMCP server exposing Martin Fowler's refactoring catalog to LLMs with 71+ refactorings. | Local · stdio |
| refdRead AI search visibility, competitors, and citations from refd; manage tracked prompts. | Remote · HTTP |
| Refinery MCPClean raw HTML into LLM-ready text before agents spend tokens. | Local · stdio |
| RegexForgeDeterministic regex synthesis from labeled examples. Zero LLM, proof matrix, backtracking audit. | Remote · HTTP |
| RegiaBI chartsChart code that fits your data first try, as source you own: you pay to author it, never to run it. | Local · stdio |
| Regintel MCPMCP server for the RegIntel API: regulatory data across 41 jurisdictions, 212 regulations. | Local · stdio |
| RegistryThe MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install. | Remote · HTTP |