webhooks.cc
NPM · @WEBHOOKS-CC/MCP · 2 COMPONENTS
Capture, inspect, send and assert on webhooks and inbound email from your coding agent.
Available components
Last scanned (22 hours ago)
Scores higher than 53% 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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1100 tokens (~100/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_endpoint" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 11 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
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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 +1
- Package version: 1.16.0 → 1.17.0 functional
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 1.15.1 → 1.16.0 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 1.14.0 → 1.15.1 functional
- Package version: 1.14.0 → 1.15.0 functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.86 ▲ 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 4 Nov 2026 · Analysed npm/@webhooks-cc/mcp@1.17.0
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 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
about_sandbox ~37
Explain what this agent can do without a webhooks.cc account, the sandbox limits, and how to connect an account. No network call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
connect_account ~126
Connect this agent to a human's webhooks.cc account, for the full tool set (mock responses, signatures, email, teams) and to keep the sandbox endpoints. Returns a link and a 6-digit code: show both to the human, who signs in or signs up with that email and enters the code. Then call wait_for_connection. Calling again gives a new code.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email the human signs in to webhooks.cc with (their GitHub or Google primary email if they sign in that way); only someone signed in as it can connect |
No output schema declared.
No examples provided.
create_endpoint ~326
Create a temporary webhook capture endpoint in the agent sandbox (no account needed): up to 3 endpoints at a time, 25 captured requests each and 100 in all, deleted 24 hours after the sandbox was created. The first call registers the sandbox, which takes a few seconds of proof of work. Mock responses, notifications and signature verification need an account: see connect_account.
| Name | Type | Req | Description |
|---|---|---|---|
| ephemeral | boolean | – | Create a temporary endpoint that auto-expires |
| expiresIn | string|number | – | Auto-expire after this duration, for example "12h" |
| mockResponse | object | – | Optional mock response to return when the endpoint receives a request |
| name | string | – | Display name for the endpoint |
| notificationUrl | string | – | URL to POST a JSON summary to after each captured request (e.g. Slack/Discord webhook) |
| responseRules | array | – | Conditional response rules. Each rule has conditions and a response. First matching rule wins. |
| signingHeader | string | – | Custom signature header name. Only used with generic-hmac provider. |
| signingProvider | string | – | Signing provider for automatic signature verification (e.g. stripe, github, shopify) |
| signingSecret | string | – | Signing secret (encrypted server-side, never returned). Required when signingProvider is set. |
| site | string | – | Which site's dashboard lists the endpoint: webhooks (webhooks.cc), mailhooks (mailhooks.cc) or both (the default when creating). Only the listing: its HTTP URL and email address work either way. Owne… |
No output schema declared.
No examples provided.
delete_endpoint ~47
Delete one of this agent's sandbox endpoints and its captured requests. Frees a slot; the sandbox's request budget is not refunded.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The endpoint slug to delete |
No output schema declared.
No examples provided.
generate_payload_schema ~209
Generate TypeScript interfaces, Zod schemas, Pydantic models, or JSON Schema from the bodies of requests captured by a sandbox endpoint. Several requests of one event teach which fields are optional or nullable.
| Name | Type | Req | Description |
|---|---|---|---|
| endpointSlug | string | yes | The endpoint slug |
| event | string | – | Only requests whose detected provider event matches, e.g. "invoice.paid" or "push". One event per schema gives the tightest types. |
| format | string | – | Output: "typescript" interfaces, "zod" schemas, "pydantic" models, or "json-schema" |
| limit | integer | – | How many of the latest requests to read before filtering |
| method | string | – | Only requests with this HTTP method |
| name | string | – | Root type name (default: from the detected event, else WebhookPayload) |
| path | string | – | Only requests with this path |
| requestIds | array | – | Use exactly these requests instead of the latest ones |
No output schema declared.
No examples provided.
get_endpoint ~36
Get one of this agent's sandbox endpoints by slug, with its sandbox limits and usage.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The endpoint slug |
No output schema declared.
No examples provided.
get_request ~31
Get full details for a request captured by a sandbox endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | The request ID |
No output schema declared.
No examples provided.
list_endpoints ~57
List this agent's sandbox endpoints. Empty until create_endpoint starts the sandbox.
| Name | Type | Req | Description |
|---|---|---|---|
| team | string | – | Team id or name (case-insensitive). Keeps endpoints shared with you from that team and endpoints you own that are shared with it. |
No output schema declared.
No examples provided.
list_requests ~76
List recent requests captured by a sandbox endpoint, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| endpointSlug | string | yes | The endpoint slug |
| kind | string | – | Only HTTP requests ("http") or only captured emails ("email") |
| limit | integer | – | Max requests to return |
| since | number | – | Only return requests after this timestamp in ms |
No output schema declared.
No examples provided.
wait_for_connection ~79
Wait for the human to enter the code from connect_account. On success the full webhooks.cc tools for their account replace these sandbox tools. Returns after timeoutSeconds (default 45) if they have not finished yet; call it again to keep waiting.
| Name | Type | Req | Description |
|---|---|---|---|
| timeoutSeconds | integer | – | How long to wait, in seconds (default 45) |
No output schema declared.
No examples provided.
wait_for_request ~76
Wait for a request to arrive at a sandbox endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| endpointSlug | string | yes | The endpoint slug to monitor |
| pollInterval | string|number | – | Interval between polls, for example "500ms" or "1s" |
| timeout | string|number | – | How long to wait, for example "30s" |
No output schema declared.
No examples provided.
How do I install the webhooks.cc MCP server?
webhooks.cc runs locally as an npm package, launched with npx -y @webhooks-cc/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 · @webhooks-cc/mcp
claude mcp add kroqdotdev-webhooks-cc -- npx -y @webhooks-cc/mcp
What is the webhooks.cc MCP server?
webhooks.cc is an MCP server listed in the public MCP registry as io.github.kroqdotdev/webhooks-cc. Capture, inspect, send and assert on webhooks and inbound email from your coding agent. This page covers its npm package (@webhooks-cc/mcp).
Is the webhooks.cc MCP server safe to use?
webhooks.cc scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 webhooks.cc MCP server expose?
webhooks.cc exposes 11 tools: create_endpoint, list_endpoints, get_endpoint, delete_endpoint, list_requests, and 6 more. Their descriptions and schemas cost roughly 1,100 tokens of context every time the server is loaded.
Is the webhooks.cc MCP server still maintained?
webhooks.cc is still listed as active in the MCP registry. We last reached this channel on 4 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 webhooks.cc MCP server under?
webhooks.cc declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.