Webhook Toolkit MCP Server

by the-kipdev Your server? Claim it

answering

Webhook Toolkit is answering right now. Last checked 15 min ago. 293 installs a week from npm. It exposes 10 tools. Last commit 18 Sep 2026.

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

Installs per day peak 229 · avg 7

a month agotoday

Uptime history 4 days of history

4 days agonow

100.0%

Uptime 24h

90 of 90 checks

Tools

read from the server

282 ms

Response time

average over 24h

293

Installs / week

npm and PyPI

Nothing serious here today

Today is the operative word: we check Webhook Toolkit every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add webhook-toolkit --transport http https://webhook-toolkit.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "webhook-toolkit": {
      "url": "https://webhook-toolkit.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.webhook-toolkit]
url = "https://webhook-toolkit.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "webhook-toolkit": {
      "url": "https://webhook-toolkit.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "webhook-toolkit": {
      "url": "https://webhook-toolkit.com/mcp"
    }
  }
}

This one needs environment variables set before it will start: WEBHOOK_TOOLKIT_KEY (Optional webhook-toolkit.com API key (whk_…): permanent URLs, listing URLs, AI explanations.). The author declared them in the registry entry; get the values from the project itself.

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

webhook

create_webhook_url

Create a public HTTPS URL that captures every 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 while building or debugging an integration. Returns the URL to configure in the service and a live inspector link for the human.

get_webhook_request

Return one captured request in full (headers, raw body, detected provider/event).

list_webhook_requests

List the most recent requests captured by a webhook URL, newest first (summaries; use get_webhook_request for one full request).

list_webhook_urls

List the webhook URLs of the account behind the API key (requires an API key).

set_webhook_response

Choose what the webhook URL answers to callers (status code, body, content type) — e.g. return 500 to test the sender's retries, or a specific JSON/XML body the service expects.

explain

explain_webhook_request

AI analysis of a captured request. mode=explain: who sent it, which event, key fields, how to verify the signature, pitfalls. mode=handler: complete receiving code that verifies the signature and handles this event. Included in paid plans; anonymous and free users get 3 trials.

replay

replay_webhook_request

Re-send a captured request (same method, headers and raw body) to a PUBLIC URL and return the target's response. Localhost and private IPs are refused here: for localhost use the CLI (`npx webhook-toolkit replay`) or the local MCP server (`npx webhook-toolkit mcp`).

sign

sign_webhook_payload

Build a webhook body with a VALID signature header for a provider, to test a handler's signature verification without triggering a real event. Providers: stripe, github, shopify, slack, twilio, mailgun. Returns the headers, the exact body to send and a ready-to-run curl command.

verify

verify_webhook_signature

Check whether a webhook signature is valid for a raw body and a secret, and diagnose why it fails (wrong secret, whitespace, re-serialized JSON body, expired timestamp, wrong URL for Twilio). Providers: stripe, github, shopify, slack, twilio.

wait

wait_for_webhook

Block until the next request reaches a webhook URL (or the timeout elapses), then return it in full: method, path, headers, body, detected provider and event. Use right after triggering an action that should send a webhook. Call again with `after` set to the last request's createdAt to wait for the following one.

Endpoints

URL	Transport	State	Latency	Checked
https://webhook-toolkit.com/mcp	streamable-http	answering	329 ms	15 min ago

Alternatives to Webhook Toolkit

same job, measured the same way

Protect MCP

by tomjwxf

Signed receipts and Cedar policies for AI agent tool calls. Claude Code hooks, MCP gateway.

1 944 installs/wk local only

Agenticmail

by agenticmail

Real email and SMS for AI agents — send mail, receive verification codes, drive a real inbox.

215 installs/wk local only

agentsbase — Email for AI Agents

by agentsbase

Email for AI agents. Create mailboxes, send/receive emails, and auto-extract verification codes.

27 installs/wk local only

Hookwarden — Webhook Integrity

by hookwarden

Webhook signature-verification audit. Stripe, GitHub, Shopify, Twilio +17. Local. Deterministic.

50 installs/wk local only

Secretguard MCP

by vladimirbakalov

Scans code for hardcoded secrets (AWS, Stripe, GitHub, JWTs) before an AI agent commits it.

local only

Github Webhook MCP

by liplus-project

MCP server bridging GitHub webhooks via Cloudflare Worker for real-time event streaming

36 installs/wk local only

Flagrix

by flagrix-io

Scan GitHub repos and profiles for malware before cloning — commit-pinned risk verdicts for agents

44 installs/wk local only

bounty-mcp

by weiseer

Live coding-bounty deal-flow from verified-escrow GitHub bounties for AI agents.

36 installs/wk local only

Webhook Toolkit — questions

Answers built from our own checks of this server.

What can Webhook Toolkit do?

It exposes 10 tools, read directly from the server on our last check. Among them: create_webhook_url, explain_webhook_request, get_webhook_request, list_webhook_requests, list_webhook_urls, replay_webhook_request and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Webhook Toolkit working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 90 checks got a reply (100.0%), average response time 282 ms. The bar chart above shows every period we have measured.

How do I connect Webhook Toolkit?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Webhook Toolkit need an API key?

No. Webhook Toolkit completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Webhook Toolkit?

It answers our handshake in 282 ms on average, which is faster than 56% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Webhook Toolkit?

The npm package webhook-toolkit was installed 293 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Webhook Toolkit open source?

Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.