Server data from the Official MCP Registry
Test, validate and explain regular expressions with match highlighting. x402 micropayment.
Test, validate and explain regular expressions with match highlighting. x402 micropayment.
Remote endpoints: sse: https://regex-generator.api.klymax402.com/mcp
Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: trusted author (155/159 approved); 6 highly-trusted packages.
1 tool verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-br0ski777-regex-generator": {
"url": "https://regex-generator.api.klymax402.com/mcp"
}
}
}From the project's GitHub README.
Test regex patterns against strings. Get all matches, capture groups, positions, and plain-English pattern explanations. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"regex-generator": {
"url": "https://regex-generator.api.klymax402.com/mcp"
}
}
}
curl -X POST "https://regex-generator.api.klymax402.com/api/test" \
-H "Content-Type: application/json" \
-d '{"pattern":"...","testStrings":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
text_test_regex | POST | /api/test | $0.001 | Test a regex pattern against input strings |
text_test_regexUse this when you need to test a regular expression against one or more strings. Returns all matches, capture groups, positions, and a human-readable explanation of the pattern.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
pattern | string | yes | Regular expression pattern (without delimiters) |
flags | string | no | Regex flags: g, i, m, s, u (default: g) |
testStrings | array | yes | Array of strings to test against the pattern |
Example response:
{"pattern":"\d{3}-\d{4}","flags":"g","explanation":"Matches 3 digits, a hyphen, then 4 digits","results":[{"input":"Call 555-1234","matched":true,"matches":[{"value":"555-1234","index":5,"groups":[]}]}],"totalMatches":1}
When to use: validating regex patterns before deploying them in code, debugging why a pattern fails to match, or extracting structured data from text. Use this BEFORE writing complex regex into production code.
Not for: text classification (use text_classify_content), PII detection (use privacy_detect_pii), text comparison (use text_compare_diff).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.