webhook-crash-lab-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y webhook-crash-lab-mcp@0.2.5
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.
list_scenarios | Returned a result under 0.1 s · 1,445 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
run_crash_lab configPath, cwd, scenarios, reportPath
Replay hostile webhook deliveries (duplicates, concurrent duplicates, out-of-order events, forged/missing/stale signatures, malformed JSON) against the handler described by a crash-lab config file, and return structured failures with fix hints. Use a TEST database and test secret only. Create a config with `npx webhook-crash-lab init` if none exists.
run_demo mode
Run crash-lab against its built-in demo credits app. "broken" shows the typical AI-generated Stripe handler failing; "fixed" shows the same app done right. Needs no config. Use it to show what crash-lab checks before setting up a real config.
explain_report reportPath, report, cwd
Read a JSON report produced by `webhook-crash-lab run --json <file>` (e.g. from CI) and return the failures in fix order, with why/fix hints and next steps.
list_scenarios
List every scenario crash-lab can run, with what it sends, why it matters in production, and how to fix a failure.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=20 |
| Source | github.com/Krrishkumar125/webhook-crash-lab-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-q6KOKw5hogheLOpaZpQodqZ1bcC8xu4UuzPS4JVfHmVHMGP0NcnQd8tVpgjRepUEZaF370oWU2DonNE8y++gbA== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/webhook-crash-lab-mcp)
New version out? Ask for a fresh report.