Webhook Crash Lab
NPM · WEBHOOK-CRASH-LAB-MCP
Lets coding agents crash-test webhook handlers and re-run until they survive retries.
Available components
Last scanned (4 hours ago)
Scores higher than 35% of npm servers
Category Testing and QA
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 94 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 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 346 tokens (~86/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 53
First indexed and scored.
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 5 Nov 2026 · Analysed npm/webhook-crash-lab-mcp@0.2.4
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 94 packages
| Packages resolved | 94 |
|---|---|
| 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 →
explain_report Explain a crash-lab report ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | – |
| report | – | – | Report JSON, as text or object |
| reportPath | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| failures | array | yes | – |
| name | string | yes | – |
| nextSteps | array | yes | – |
| notTested | array | yes | – |
| ok | boolean | yes | – |
| reportPath | string | – | – |
| scenarios | array | yes | – |
| summary | object | yes | – |
No examples provided.
list_scenarios List crash-lab scenarios ~37
List every scenario crash-lab can run, with what it sends, why it matters in production, and how to fix a failure.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| scenarios | array | yes | – |
No examples provided.
run_crash_lab Run webhook-crash-lab ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| configPath | string | yes | Path to a crash-lab config (.mjs, .js, .cjs, .ts, .mts or .cts), relative to cwd |
| cwd | string | – | Project directory; defaults to the server working directory |
| reportPath | string | – | Also write the full JSON report here |
| scenarios | array | – | Run only these scenarios |
| Name | Type | Req | Description |
|---|---|---|---|
| failures | array | yes | – |
| name | string | yes | – |
| nextSteps | array | yes | – |
| notTested | array | yes | – |
| ok | boolean | yes | – |
| reportPath | string | – | – |
| scenarios | array | yes | – |
| summary | object | yes | – |
No examples provided.
run_demo Run the built-in demo ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| failures | array | yes | – |
| name | string | yes | – |
| nextSteps | array | yes | – |
| notTested | array | yes | – |
| ok | boolean | yes | – |
| reportPath | string | – | – |
| scenarios | array | yes | – |
| summary | object | yes | – |
No examples provided.
How do I install the Webhook Crash Lab MCP server?
Webhook Crash Lab runs locally as an npm package, launched with npx -y webhook-crash-lab-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · webhook-crash-lab-mcp
claude mcp add krrishkumar125-webhook-crash-lab-mcp -- npx -y webhook-crash-lab-mcp
What is the Webhook Crash Lab MCP server?
Webhook Crash Lab is an MCP server listed in the public MCP registry as io.github.Krrishkumar125/webhook-crash-lab-mcp. Lets coding agents crash-test webhook handlers and re-run until they survive retries. This page covers its npm package (webhook-crash-lab-mcp).
Is the Webhook Crash Lab MCP server safe to use?
Webhook Crash Lab scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Webhook Crash Lab MCP server expose?
Webhook Crash Lab exposes 4 tools: run_crash_lab, run_demo, explain_report, list_scenarios. Their descriptions and schemas cost roughly 346 tokens of context every time the server is loaded.
Is the Webhook Crash Lab MCP server still maintained?
Webhook Crash Lab is still listed as active in the MCP registry. We last reached this channel on 5 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 Webhook Crash Lab MCP server under?
Webhook Crash Lab declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.