Regex-LE
Regex-LE is an MCP server published by nolindnaidoo; its MCP spec-revision support has not been verified yet. Last verified 2026-08-15.
Does Regex-LE support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision Regex-LE supports (as of 2026-08-15).
Is Regex-LE a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Regex-LE (as of 2026-08-15).
How do I connect to Regex-LE?
Regex-LE is available via the package npm:regex-le-mcp, the official MCP Registry under io.github.nolindnaidoo/regex-le, the source repository at https://github.com/nolindnaidoo/regex-le. Authentication: unknown. Transports: stdio.
When were Regex-LE's facts last verified?
2026-08-15. Each fact on this page links to the sources used to verify it.
Extract regular expressions from code, each with a ReDoS safety verdict.
How widely adopted is Regex-LE?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for Regex-LE
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 2
- Forks
- 0
- Last pushed
- (45 days ago)
- Created
- Open issues
- 0
- Primary language
- Rust
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Declared topics: catastrophic-backtracking, cli, code-review, developer-tools, dos, letools, lint, mcp, pattern-matching, redos, regex, regular-expression, rust, security, static-analysis, typescript, validation, vscode, vscode-extension — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
2.3.0- Last published
- First published
- Releases
- 4
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 0
- Unpacked size
- 24 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: registry-record
· confidence 0.85 (Good).