# Webhook Toolkit (npm · webhook-toolkit)

Webhook URLs for AI agents: receive, wait for, replay, sign and verify webhooks (Stripe, GitHub…).

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `webhook-toolkit.com`: 64/100, [markdown](https://verifymcp.io/servers/the-kipdev-webhook-toolkit/webhook-toolkit.md), [page](https://verifymcp.io/servers/the-kipdev-webhook-toolkit/webhook-toolkit)
- npm · `webhook-toolkit`: 69/100 (this document), [markdown](https://verifymcp.io/servers/the-kipdev-webhook-toolkit/webhook-toolkit-2.md), [page](https://verifymcp.io/servers/the-kipdev-webhook-toolkit/webhook-toolkit-2)

## Channel facts

- Registry: `npm`
- Package: `webhook-toolkit`
- Version: `0.1.1`
- 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-09-20.

- **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.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/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).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1989 tokens (~180/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 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.

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

## Install

### How do I install the Webhook Toolkit MCP server?

Webhook Toolkit runs locally as an npm package, launched with npx -y webhook-toolkit. 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 the-kipdev-webhook-toolkit -- npx -y webhook-toolkit
```

### Cursor

```json
{
  "mcpServers": {
    "the-kipdev-webhook-toolkit": {
      "command": "npx",
      "args": [
        "-y",
        "webhook-toolkit"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "the-kipdev-webhook-toolkit": {
      "command": "npx",
      "args": [
        "-y",
        "webhook-toolkit"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add the-kipdev-webhook-toolkit -- npx -y webhook-toolkit
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "the-kipdev-webhook-toolkit": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "webhook-toolkit"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add the-kipdev-webhook-toolkit --command npx --arg -y --arg webhook-toolkit
```

### Hermes

```yaml
mcp_servers:
  the-kipdev-webhook-toolkit:
    command: "npx"
    args: ["-y", "webhook-toolkit"]
```

### Netclaw

```json
{
  "McpServers": {
    "the-kipdev-webhook-toolkit": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "webhook-toolkit"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add the-kipdev-webhook-toolkit -t stdio -c npx -a -y webhook-toolkit
```

### Other

```json
{
  "mcpServers": {
    "the-kipdev-webhook-toolkit": {
      "command": "npx",
      "args": [
        "-y",
        "webhook-toolkit"
      ]
    }
  }
}
```

## 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-09-19 (score 69, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-18 (score 54)

First indexed and scored.

## MCP tools (11)

### `create_webhook_url` (~143 tokens)

Create a webhook URL

Create a public HTTPS URL that captures every HTTP request sent to it (any method, any sub-path). Use it when you need an endpoint to receive a webhook from a third-party service (Stripe, GitHub, Shopify, Slack, Twilio, Clerk…) or from the app you are testing, without deploying or tunnelling anything. Returns the URL, the token the other tools take, and a web inspector link. Anonymous URLs expire after 7 days. Next: configure the sender with the URL, trigger the event, then call wait_for_webhook.

Input parameters:

- `name` (string): Label shown in the dashboard, e.g. 'stripe-checkout-test'.

### `list_webhook_urls` (~45 tokens)

List webhook URLs

List the webhook URLs owned by the account behind WEBHOOK_TOOLKIT_KEY (required). Use it to find the token of an existing permanent URL instead of creating a new one.

### `wait_for_webhook` (~268 tokens)

Wait for a webhook

Block until a webhook reaches a capture URL, then return it (method, path, headers, raw body, detected provider and event type). Use it right after triggering the action that sends the webhook. It is safe to call after the webhook was already sent: requests received since the URL was created in this session, or since the last request this tool returned for the token, are included. Filters skip unrelated deliveries. Calling it again returns the next request. A timeout means nothing matching arrived: check the sender's configuration, then call again.

Input parameters:

- `after` (string): ISO timestamp: only requests strictly newer than this. Overrides the automatic cursor.
- `body_contains` (string): Only requests whose body contains this text.
- `event` (string): Only this event type, e.g. 'checkout.session.completed', 'push'.
- `method` (string): Only this HTTP method, e.g. 'POST'.
- `path_contains` (string): Only requests whose sub-path contains this text.
- `provider` (string): Only a request from this sender, e.g. 'stripe', 'github'.
- `timeout_seconds` (integer): How long to wait. Default 60.
- `token` (string, required): Token returned by create_webhook_url (the last segment of the URL).

### `list_webhook_requests` (~97 tokens)

List captured requests

List the requests captured by a webhook URL, newest first, with method, path, detected provider/event, size and a short body preview. Use it to see what a service actually sent, then get_webhook_request for one in full.

Input parameters:

- `after` (string): ISO timestamp: only requests newer than this.
- `limit` (integer): How many, default 20.
- `token` (string, required): Webhook URL token.

### `get_webhook_request` (~88 tokens)

Get a captured request

Get one captured request in full: method, path, query, all headers, raw body (as received, byte-exact for signature checks), detected provider and event. Use it to inspect a payload before writing or fixing a handler.

Input parameters:

- `request_id` (string, required): Request id from wait_for_webhook or list_webhook_requests.
- `token` (string, required): Webhook URL token.

### `set_webhook_response` (~150 tokens)

Set the URL's response

Change what a webhook URL answers to senders: status code, body and content type (and optionally its name). Use it to simulate a failing endpoint (e.g. 500 so the provider retries) or to answer a verification challenge that expects a specific body. URLs created with an API key can only be changed with that key.

Input parameters:

- `body` (string): Response body.
- `content_type` (string): Response Content-Type, e.g. 'application/json'.
- `name` (string): New label for the URL.
- `status` (integer): HTTP status to answer, e.g. 200, 410, 500.
- `token` (string, required): Webhook URL token.

### `replay_webhook_request` (~181 tokens)

Replay a request locally

Re-send a captured webhook FROM THIS MACHINE to a URL, localhost included (e.g. http://localhost:3000/api/webhooks), with the same method, headers and body. Use it to iterate on a webhook handler without re-triggering the real event. Returns the handler's status, latency and response. The captured sub-path and query are appended to target_url. Timestamped signatures (Stripe, Slack, Svix, Paddle) are replayed as captured, so strict handlers reject them after ~5 minutes: then use send_signed_webhook.

Input parameters:

- `request_id` (string, required): Captured request id.
- `target_url` (string, required): Where to send it, e.g. http://localhost:3000/api/webhooks/stripe (a bare port such as 3000 works).
- `token` (string, required): Webhook URL token.

### `send_signed_webhook` (~288 tokens)

Send a signed webhook

Build a webhook with a valid provider signature (Stripe, GitHub, Shopify, Slack, Twilio, Mailgun, Svix/Clerk/Resend, Paddle, Discord with a test key) and POST it FROM THIS MACHINE to your handler (localhost works). Use it to test signature verification and event handling without the real provider. Returns the handler's status and response. Signing happens locally: the secret never leaves the machine.

Input parameters:

- `event` (string): Event type, e.g. 'checkout.session.completed', 'push', 'orders/create'.
- `payload` (string): Raw body to sign, sent verbatim (JSON text; Twilio: urlencoded or a JSON object of params). Omit to use a realistic sample of `event`.
- `provider` (string, required): Signature scheme. 'svix' also covers Clerk, Resend and Standard Webhooks.
- `secret` (string, required): Signing secret, as your handler knows it (Stripe whsec_…, GitHub webhook secret, Twilio auth token, Discord: an Ed25519 test private key in hex).
- `target_url` (string, required): Handler URL, e.g. http://localhost:3000/api/webhooks/stripe (a bare port such as 3000 works).
- `twilio_url` (string): Twilio only: the public URL Twilio would call (default: target_url).

### `sign_webhook_payload` (~230 tokens)

Sign a webhook payload

Compute valid signature headers for a webhook body without sending it. Use it to write a test fixture, a curl command, or to check what a provider's signature should be for a given secret. Returns headers, body and a curl command. Runs locally.

Input parameters:

- `event` (string): Event type, e.g. 'checkout.session.completed', 'push', 'orders/create'.
- `payload` (string): Raw body to sign, sent verbatim (JSON text; Twilio: urlencoded or a JSON object of params). Omit to use a realistic sample of `event`.
- `provider` (string, required): Signature scheme. 'svix' also covers Clerk, Resend and Standard Webhooks.
- `secret` (string, required): Signing secret, as your handler knows it (Stripe whsec_…, GitHub webhook secret, Twilio auth token, Discord: an Ed25519 test private key in hex).
- `timestamp` (integer): Unix seconds to sign with (default: now).
- `url` (string): Twilio only (required for Twilio): the public URL Twilio calls.

### `verify_webhook_signature` (~232 tokens)

Verify a webhook signature

Check whether a webhook signature is valid and, when it is not, explain why: wrong secret, body modified before verification (JSON re-serialised by a parser, trailing newline, CRLF), whitespace in the secret, expired timestamp, or for Twilio the URL form (http vs https, port, query, trailing slash). Use it when a handler rejects deliveries with 'invalid signature'. Runs locally: the secret never leaves the machine.

Input parameters:

- `headers` (object, required): Request headers, any casing, e.g. {"stripe-signature": "t=…,v1=…"}.
- `provider` (string, required): Signature scheme. 'svix' also covers Clerk, Resend and Standard Webhooks.
- `raw_body` (string, required): The body exactly as received (e.g. the body field of get_webhook_request).
- `secret` (string, required): Signing secret (Discord: the application public key).
- `tolerance_seconds` (integer): Timestamp tolerance, default 300. 0 disables the check.
- `url` (string): Twilio only: the full public URL Twilio called.

### `explain_webhook_request` (~137 tokens)

Explain a captured request (AI)

AI analysis of a captured webhook: what the event means, its key fields, how its signature is verified and common pitfalls; or, with mode 'handler', a ready-to-use handler in node, python, php, go or ruby. Use it on an unfamiliar payload. Needs WEBHOOK_TOOLKIT_KEY; paid feature with 3 free trials.

Input parameters:

- `language` (string): Handler language (mode 'handler').
- `mode` (string): 'explain' (default) or 'handler' to generate code.
- `request_id` (string, required): Captured request id.
- `token` (string, required): Webhook URL token.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/the-kipdev-webhook-toolkit/webhook-toolkit-2#diagnostics

## Score history

- 2026-09-20: 69
- 2026-09-19: 69
- 2026-09-18: 54

## Common questions

### What is the Webhook Toolkit MCP server?

Webhook Toolkit is an MCP server listed in the public MCP registry as io.github.THE-KIPDEV/webhook-toolkit. Webhook URLs for AI agents: receive, wait for, replay, sign and verify webhooks (Stripe, GitHub…). This page covers its npm package (webhook-toolkit).

### Is the Webhook Toolkit MCP server safe to use?

Webhook Toolkit scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Toolkit MCP server expose?

Webhook Toolkit exposes 11 tools: create_webhook_url, list_webhook_urls, wait_for_webhook, list_webhook_requests, get_webhook_request, and 6 more. Their descriptions and schemas cost roughly 1,859 tokens of context every time the server is loaded.

### Is the Webhook Toolkit MCP server still maintained?

Webhook Toolkit is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Toolkit MCP server under?

Webhook Toolkit 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/webhook-toolkit
- Socket report: https://socket.dev/npm/package/webhook-toolkit
- Repository: https://github.com/THE-KIPDEV/webhook-toolkit
- Website: https://webhook-toolkit.com/
- Changelog RSS feed: https://verifymcp.io/servers/the-kipdev-webhook-toolkit/webhook-toolkit-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/the-kipdev-webhook-toolkit/webhook-toolkit-2.json
- HTML version of this page: https://verifymcp.io/servers/the-kipdev-webhook-toolkit/webhook-toolkit-2