# webhooks.cc (npm · @webhooks-cc/mcp)

Capture, inspect, send and assert on webhooks and inbound email from your coding agent.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `webhooks.cc`: 39/100, [markdown](https://verifymcp.io/servers/kroqdotdev-webhooks-cc/webhooks.md), [page](https://verifymcp.io/servers/kroqdotdev-webhooks-cc/webhooks)
- npm · `@webhooks-cc/mcp`: 76/100 (this document), [markdown](https://verifymcp.io/servers/kroqdotdev-webhooks-cc/webhooks-cc-mcp.md), [page](https://verifymcp.io/servers/kroqdotdev-webhooks-cc/webhooks-cc-mcp)

## Channel facts

- Registry: `npm`
- Package: `@webhooks-cc/mcp`
- Version: `1.17.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1100 tokens (~100/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add kroqdotdev-webhooks-cc -- npx -y @webhooks-cc/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "kroqdotdev-webhooks-cc": {
      "command": "npx",
      "args": [
        "-y",
        "@webhooks-cc/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kroqdotdev-webhooks-cc": {
      "command": "npx",
      "args": [
        "-y",
        "@webhooks-cc/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add kroqdotdev-webhooks-cc -- npx -y @webhooks-cc/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kroqdotdev-webhooks-cc": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@webhooks-cc/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kroqdotdev-webhooks-cc --command npx --arg -y --arg @webhooks-cc/mcp
```

### Hermes

```yaml
mcp_servers:
  kroqdotdev-webhooks-cc:
    command: "npx"
    args: ["-y", "@webhooks-cc/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "kroqdotdev-webhooks-cc": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@webhooks-cc/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add kroqdotdev-webhooks-cc -t stdio -c npx -a -y @webhooks-cc/mcp
```

### Other

```json
{
  "mcpServers": {
    "kroqdotdev-webhooks-cc": {
      "command": "npx",
      "args": [
        "-y",
        "@webhooks-cc/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 76, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 61, +1)

- [functional] Package version: 1.16.0 → 1.17.0

### 2026-11-02 (score 60, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 1.15.1 → 1.16.0

### 2026-11-01 (score 75, +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.

### 2026-10-30 (score 74, +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.

### 2026-10-29 (score 73, 0)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.17 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional] Package version: 1.14.0 → 1.15.1
- [functional] Package version: 1.14.0 → 1.15.0

### 2026-10-28 (score 73, +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.

### 2026-10-26 (score 72, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.86

## MCP tools (11)

### `create_endpoint` (~326 tokens)

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.

Input parameters:

- `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…

### `list_endpoints` (~57 tokens)

List this agent's sandbox endpoints. Empty until create_endpoint starts the sandbox.

Input parameters:

- `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.

### `get_endpoint` (~36 tokens)

Get one of this agent's sandbox endpoints by slug, with its sandbox limits and usage.

Input parameters:

- `slug` (string, required): The endpoint slug

### `delete_endpoint` (~47 tokens)

Delete one of this agent's sandbox endpoints and its captured requests. Frees a slot; the sandbox's request budget is not refunded.

Input parameters:

- `slug` (string, required): The endpoint slug to delete

### `list_requests` (~76 tokens)

List recent requests captured by a sandbox endpoint, newest first.

Input parameters:

- `endpointSlug` (string, required): 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

### `get_request` (~31 tokens)

Get full details for a request captured by a sandbox endpoint.

Input parameters:

- `requestId` (string, required): The request ID

### `wait_for_request` (~76 tokens)

Wait for a request to arrive at a sandbox endpoint.

Input parameters:

- `endpointSlug` (string, required): 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"

### `generate_payload_schema` (~209 tokens)

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.

Input parameters:

- `endpointSlug` (string, required): 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

### `connect_account` (~126 tokens)

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.

Input parameters:

- `email` (string, required): 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

### `wait_for_connection` (~79 tokens)

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.

Input parameters:

- `timeoutSeconds` (integer): How long to wait, in seconds (default 45)

### `about_sandbox` (~37 tokens)

Explain what this agent can do without a webhooks.cc account, the sandbox limits, and how to connect an account. No network call.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/kroqdotdev-webhooks-cc/webhooks-cc-mcp#diagnostics

## Score history

- 2026-11-04: 76
- 2026-11-03: 61
- 2026-11-02: 60
- 2026-11-01: 75
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 73
- 2026-10-28: 73
- 2026-10-27: 72
- 2026-10-26: 72
- 2026-10-25: 61
- 2026-10-24: 71
- 2026-10-23: 56

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@webhooks-cc/mcp
- Socket report: https://socket.dev/npm/package/@webhooks-cc/mcp
- Repository: https://github.com/kroqdotdev/webhooks-cc
- Website: https://webhooks.cc/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/kroqdotdev-webhooks-cc/webhooks-cc-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/kroqdotdev-webhooks-cc/webhooks-cc-mcp.json
- HTML version of this page: https://verifymcp.io/servers/kroqdotdev-webhooks-cc/webhooks-cc-mcp