Search / com.gumballtools/regex-explainer
protogridR0· no sign-inExplain a regex in plain English and detect catastrophic backtracking risk.
v0.1.0 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"regex-explainer": {
"type": "http",
"url": "https://regex-explainer.gumballtools.com/api/mcp"
}
}
}claude mcp add --transport http regex-explainer https://regex-explainer.gumballtools.com/api/mcp[mcp_servers.regex-explainer]
url = "https://regex-explainer.gumballtools.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"regex-explainer": {
"type": "remote",
"url": "https://regex-explainer.gumballtools.com/api/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"regex-explainer": {
"type": "http",
"url": "https://regex-explainer.gumballtools.com/api/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=regex-explainer&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vcmVnZXgtZXhwbGFpbmVyLmd1bWJhbGx0b29scy5jb20vYXBpL21jcCJ9"
}{
"servers": {
"regex-explainer": {
"type": "http",
"url": "https://regex-explainer.gumballtools.com/api/mcp"
}
}
}{
"mcpServers": {
"regex-explainer": {
"httpUrl": "https://regex-explainer.gumballtools.com/api/mcp"
}
}
}extensions:
"regex-explainer":
enabled: true
name: "regex-explainer"
type: streamable_http
uri: "https://regex-explainer.gumballtools.com/api/mcp"
timeout: 300
protocol.modernsupports 2026-07-28 (server/discover)protocol.statelessanswers without a sessionprotocol.transportstreamable HTTPprotocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every useauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length1 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations1 of 1 tools declare readOnlyHint or destructiveHinttools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: explain_regex (destructiveHint, idempotentHint)tools.token_costabout 472 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +dns-namespace +website +reachable +uptime-100% ~updated-44d-ago -duplicate-repo(16 names)
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://regex-explainer.gumballtools.com/api/mcp streamable-http | none | yes | 100% | 894 ms | 2026-07-28 | 2026-10-20 |
explain_regexread-only | Explain a regular expression in plain English and detect the failure modes that make patterns dangerous rather than merely wrong. Use this whenever a regex needs to be read, reviewed, or verified — and ALWAYS before putting a pattern somewhere it will run against untrusted input. The critical check is catastrophic backtracking: a pattern like (a+)+$ is three characters longer than a safe equivalent, looks harmless, and takes minutes of CPU on a 30-character input that almost matches. That makes it a denial-of-service vector. Whether a pattern is vulnerable depends on whether nested quantifiers can match the same characters in more than one way, which is a structural property that is unreliable to judge by reading. It also flags: missing anchors (an unanchored validator accepts any string that merely CONTAINS a valid value), unescaped dots, character ranges like [A-z] that span punctuation, alternation precedence mistakes where an anchor applies to only one branch, and constructs JavaScript does not support. Input: `pattern` accepts either a bare pattern or a full /pattern/flags literal. JavaScript syntax; PCRE-only constructs are reported as unsupported rather than guessed at. Returns: `summary` (one sentence), `steps` (an ordered walkthrough), `warnings` (each with a code, severity, detail, and fix), `flagNotes`, capture group counts and names, and `hasBlockingIssue` — check that flag first. If the pattern cannot be parsed it returns an error naming the position, rather than a plausible-looking explanation of something else. |
Schemas: list_tools.
15 other active names share this repository (showing 10): com.crontoenglish/cron-translator, com.gumballtools/amortize, com.gumballtools/body-metrics, com.gumballtools/check-digit, com.gumballtools/color-companion, com.gumballtools/due-date, com.gumballtools/equation-steps, com.gumballtools/iso-week, com.gumballtools/json-to-types, com.gumballtools/payload-validator
And 8 more from this publisher.
{
"name": "com.gumballtools/regex-explainer",
"title": "Regex Explainer",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://regex-explainer.gumballtools.com/api/mcp",
"type": "streamable-http"
}
],
"version": "0.1.0",
"repository": {
"url": "https://github.com/bwalvoord/gumball",
"source": "github"
},
"websiteUrl": "https://regex-explainer.gumballtools.com",
"description": "Explain a regex in plain English and detect catastrophic backtracking risk."
}