regexlab-mcp@0.1.0
VERIFIED· not startedPublisher claims: "Enables AI agents to run the same regex in real Python, JavaScript, and optional regex engines side by side, flag disagreements, confirm ReDoS by timing adversarial input in a killed child process, explain patterns, convert Python/JavaScript syntax, preview substitutions, and generate verified test suggestions. All execution is isolated in throwaway processes with hard timeouts and strict input caps." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-09 and scored it 84/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.// stdout, flushing after each so a parent that has to kill us still sees everythingFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""Run argv with stdin_text; kill the whole tree if it is still running after `timeout` s."""Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out._JS_SPACE = set("\t\n\x0b\x0c\r
") | {Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.raise SandboxError(f"could not kill process {proc.pid}") from eFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.g = subprocess.Popen([sys.executable, "-c", "import time; time.sleep(120)"])Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.kill us still sees everything finished so far. The pattern is only ever handed toFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.