Regex Test Mcp
Run JavaScript regex matches with trustworthy offsets and named groups without silent hangs from zero-width loops.
Overview
Regex Test MCP is a MCP server for the Ship phase that runs trustworthy JavaScript regex tests with offsets, named groups, and zero-width loop safety.
What is this MCP server?
- JavaScript-regex semantics with real match offsets
- Named capture groups supported in test output
- Guards against zero-width infinite loops that freeze naive testers
- stdio npm @mukundakatta/regex-test-mcp v0.1.0
- Agent-callable alternative to guessing regex in chat
- Server version 0.1.0
- stdio npm transport
- JavaScript regex engine semantics
What problem does it solve?
Agents and browser regex toys give wrong offsets or hang on zero-width patterns, so you ship broken parsers.
Who is it for?
Builders writing Node or browser regex for parsing, validation, or extraction who test patterns through MCP.
Skip if: POSIX-only pipelines, PCRE-only backends, or security audits of user-supplied regex denial-of-service.
What do I get? / Deliverables
You see accurate JS match spans and group values from the agent before merging validation code.
- Structured match results with offsets and named capture values
- Safer feedback on patterns prone to zero-width looping
Recommended MCP Servers
Journey fit
Regex behavior is verified during ship-phase testing when parsers, validators, and scrapers must match production JavaScript semantics. Unit-style pattern checks against sample strings belong in testing, not one-off copy-paste in a REPL.
How it compares
JS regex execution MCP, not an agent skill for explaining regex theory.
Common Questions / FAQ
Who is regex-test-mcp for?
Developers and solo builders who want Claude or Cursor to test JavaScript regex with reliable match indices.
When should I use regex-test-mcp?
When you are refining a pattern for logs, forms, or scrapers and need named groups and offsets verified in JS.
How do I add regex-test-mcp to my agent?
Add stdio MCP config for @mukundakatta/regex-test-mcp from npm and restart your MCP-enabled editor.