# Regex Verifier

**MCP Tool:** `regex_verifier`  
**Tier:** Tier 2 — Differentiated  
**Category:** validators  
**Endpoint:** https://obfus.link/mcp  
**Price:** $0.015 / call  
**Verification:** ✓ TDD verified  

> Verify, generate, explain, and translate regular expressions

## Atomic Answer

Regex Verifier tests, generates, explains, and translates regular expressions in one tool. Generator mode produces patterns from positive and negative examples. Explain mode renders any pattern in plain English. Translation converts between JavaScript, Python, Go, Rust, and PCRE flavors. Anti-pattern detection flags ReDoS vulnerabilities with one-line fixes.

## Description

Tests regex patterns against cases, generates regex from positive and negative examples, explains patterns in plain English, detects ReDoS anti-patterns with severity ratings, and translates between JavaScript, Python, Go, Rust, and PCRE flavors with feature warnings.

## Agentic Reasoning

USE THIS WHEN: (1) You need to test a regex pattern against specific test cases. (2) You know what strings should match but not the regex syntax — use generate mode. (3) You need to translate a pattern between language dialects (Python lookbehind, Go no-backreferences, etc). (4) You want a plain-English explanation of what a regex does. DO NOT USE WHEN: you just need JavaScript RegExp.test() — call it directly. OVER ALTERNATIVES: prefer this over regex101.com (no MCP API, no generate mode) and manual writing (misses ReDoS vulnerabilities and dialect mismatches).

## MCP Description

Multi-mode regex tool: verify, generate from examples, translate between dialects, or explain a pattern in English. USE WHEN: testing patterns, you know what should match but not the syntax (generate mode), translating between language dialects, or auditing for ReDoS. INPUT: mode plus mode-specific fields. OUTPUT: results, optional explanation, anti-pattern findings, or translated pattern. COST: 1 unit.

## Input Schema

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `mode` | `verify` \| `generate` \| `translate` | yes |  |
| `flags` | `string` | no |  |
| `pattern` | `string` | no |  |
| `testCases` | `array` | no |  |
| `explainMode` | `boolean` | no |  |
| `sourceDialect` | `string` | no |  |
| `targetDialect` | `string` | no |  |
| `detectAntiPattern` | `boolean` | no |  |
| `generatorStrategy` | `precise` \| `balanced` \| `permissive` | no |  |

## Output Schema

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `valid` | `boolean` | no |  |
| `results` | `array` | no |  |
| `explanation` | `string` | no |  |
| `translation` | `object` | no |  |
| `antiPatterns` | `array` | no |  |
| `generatedPattern` | `string` | no |  |

## How To Use

1. **Select mode** — verify (test pattern), generate (produce from examples), or translate (between dialects).
2. **Enter pattern** — Drop in the regex pattern with optional flags (i, g, m, s, u, y).
3. **Add test cases** — For verify mode: list inputs and whether each should match. For generate mode: provide positive and negative examples.
4. **Enable options** — Turn on Explain Mode for plain-English description. Turn on Detect Anti-Pattern for ReDoS warnings.
5. **Run and review** — Click Run or press Ctrl+Enter. Pass/fail per test case, explanation, and anti-pattern findings appear.

## FAQs

**What is Generate mode?**

Inverts the verification workflow: you provide strings that should match and strings that should not, and the tool produces a regex that satisfies both sets. Three strategies (precise, balanced, permissive) control how strictly the pattern matches the positive examples.

**Which dialects does Translate mode support?**

JavaScript, Python, Go, Rust, and PCRE. Features that do not translate cleanly (variable-length lookbehind, backreferences in Go, atomic groups) are flagged in the warnings array with per-feature explanations and suggested workarounds.

**What does the anti-pattern detector catch?**

Catastrophic backtracking patterns (ReDoS), missing anchors, over-broad wildcards (.*), redundant character class escapes, and unnecessary capture groups. Each finding has severity (critical, warn, info) and a one-line fix.

**Can I use this tool via the MCP API?**

Yes. The tool is registered on the obfus.link MCP server at https://obfus.link/mcp. Call it from any MCP-compatible agent with a Shared Payment Token. The MCP tool name matches the snake_case slug shown in the integration snippet.

## Tags

`regex` · `regexp` · `pattern` · `validate` · `generate` · `explain`

---

*obfus.link — A Subether Labs Infrastructure Project*  
*Canonical URL: https://obfus.link/tool/regex-verifier*  
*JSON view: https://obfus.link/tool/regex-verifier/json*