Regex Tester API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026

Test, validate and explain regular expressions with match highlighting. x402 micropayment.

VerifiedSSEWeb executableFinanceDeveloper Tools

Overview

AI-generated overview

A remote MCP endpoint that tests regular expressions against strings, returning matches, capture groups, positions and plain-English explanations.

What you can do
Test a regex pattern against one or more input strings, with optional flags such as g, i, m, s and u (text_test_regex). Retrieve every match with its position and capture groups. Get a human-readable explanation of what the pattern does.
When to use it
Useful for checking a regex before putting it into production code, debugging why a pattern fails to match, or extracting structured data from text. It is not intended for text classification, PII detection or text comparison.
Requirements
A remote MCP endpoint reached over SSE; no API key or signup is declared. Each call is paid per use through x402 micropayments in USDC on Base L2, so an x402-aware client and a funded wallet are needed.
Before you install
Every call costs money ($0.003 per test per the README) and is settled in USDC on Base, so a wallet is involved and spending should be capped. Test strings are sent to a third-party service. The README also mentions ATXP OAuth-wrapped access.

Installation

In SourceWeft

  1. Open Regex Tester API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fregex-generator/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "regex-tester-api": {
      "type": "sse",
      "url": "https://regex-generator.api.klymax402.com/mcp"
    }
  }
}

README

Regex Tester API

[MCP Server] [x402] [License: MIT]

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.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

json
{  "mcpServers": {    "regex-generator": {      "url": "https://regex-generator.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
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.

Tools

ToolMethodPathPriceDescription
text_test_regexPOST/api/test$0.003Test a regex pattern against input strings

text_test_regex

Use 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

NameTypeRequiredDescription
patternstringyesRegular expression pattern (without delimiters)
flagsstringnoRegex flags: g, i, m, s, u (default: g)
testStringsarrayyesArray of strings to test against the pattern

Example response:

json
{"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).

Example agent prompts

  • "Test a regular expression against one or more strings"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Source: README.md at commit 2a14433

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts