io.github.rog0x/regex
NPM · @ROG0X/MCP-REGEX-TOOLS
Regex test, explain, replace patterns for AI agents
Available components
Last scanned (6 hours ago)
Scores higher than 84% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 228 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 458 tokens (~91/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed npm/@rog0x/mcp-regex-tools@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
regex_explain ~56
Take a regex pattern and return a human-readable explanation of each component, including flags.
| Name | Type | Req | Description |
|---|---|---|---|
| flags | string | – | Regex flags to explain (e.g. 'gi') |
| pattern | string | yes | The regular expression pattern to explain |
No output schema declared.
No examples provided.
regex_extract ~107
Extract all matches of a regex pattern from text. Returns a structured array of match objects with full match text, captured groups, and named groups.
| Name | Type | Req | Description |
|---|---|---|---|
| captureGroup | number | – | If set, return only the value of this capture group number from each match (0 = full match) |
| flags | string | – | Regex flags. Defaults to 'g' |
| pattern | string | yes | The regular expression pattern to extract matches for |
| text | string | yes | The text to extract matches from |
No output schema declared.
No examples provided.
regex_replace ~122
Find and replace using a regex pattern. Supports capture group references ($1, $2, $&, etc.) in the replacement string.
| Name | Type | Req | Description |
|---|---|---|---|
| flags | string | – | Regex flags (e.g. 'gi'). Defaults to 'g' |
| pattern | string | yes | The regular expression pattern to match |
| replacement | string | yes | The replacement string. Use $1, $2 for captured groups, $& for full match, $` for text before match, $' for text after match |
| text | string | yes | The input text to perform replacements on |
No output schema declared.
No examples provided.
regex_test ~81
Test a regex pattern against text. Returns all matches with indices, captured groups, and named groups.
| Name | Type | Req | Description |
|---|---|---|---|
| flags | string | – | Regex flags (e.g. 'gi' for global case-insensitive). Defaults to 'g' |
| pattern | string | yes | The regular expression pattern to test |
| text | string | yes | The text to test the pattern against |
No output schema declared.
No examples provided.
text_transform ~92
Apply common text transformations. Available transforms: camelCase, snake_case, kebab-case, PascalCase, UPPER, lower, title, reverse, trim, deduplicate_lines, sort_lines, remove_blank_lines, count. Multiple transforms can be chained and will be applied in order.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The input text to transform |
| transforms | array | yes | One or more transformations to apply in order |
No output schema declared.
No examples provided.
How do I install the io.github.rog0x/regex MCP server?
io.github.rog0x/regex runs locally as an npm package, launched with npx -y @rog0x/mcp-regex-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-regex-tools
claude mcp add rog0x-regex -- npx -y @rog0x/mcp-regex-tools
What is the io.github.rog0x/regex MCP server?
io.github.rog0x/regex is an MCP server listed in the public MCP registry as io.github.rog0x/regex. Regex test, explain, replace patterns for AI agents. This page covers its npm package (@rog0x/mcp-regex-tools).
Is the io.github.rog0x/regex MCP server safe to use?
io.github.rog0x/regex scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.rog0x/regex MCP server expose?
io.github.rog0x/regex exposes 5 tools: regex_test, regex_replace, regex_extract, regex_explain, text_transform. Their descriptions and schemas cost roughly 458 tokens of context every time the server is loaded.
Is the io.github.rog0x/regex MCP server still maintained?
io.github.rog0x/regex is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.rog0x/regex MCP server under?
io.github.rog0x/regex declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.rog0x/regex MCP server?
VerifyMCP ran 15 checks on io.github.rog0x/regex, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.rog0x/regex: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.