Webhook Toolkit MCP Server

by the-kipdev Your server? Claim it

answering

Webhook Toolkit is answering right now. Last checked 13 min ago. 51 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 12 · -83% w/w

a month agotoday

Uptime history 51 days of history · worst day 98%

51 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

350 ms

Response time

average over 24h

Installs / week

npm and PyPI

Webhook Toolkit missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 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

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "webhook-toolkit": {
      "type": "http",
      "url": "https://webhook-toolkit.com/mcp"
    }
  }
}

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	1006 ms	13 min ago

Alternatives to Webhook Toolkit

same job, measured the same way

BotsInbox — Email Inboxes for AI Agents

by botsinbox

Free email inboxes for AI agents: self sign-up, receive email and verification codes.

answering

Bridgly

by bridgly

Scrape X, Reddit, LinkedIn, GitHub, Instagram and TikTok data as tools for AI agents.

answering

asms

by asms

Phone numbers for AI agents: SMS verification codes and rented numbers that receive SMS.

14 tools answering

Agenticmail

by agenticmail

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

177 installs/wk local only

Steadfast Repository Governance

by rllibo833-sudo

Local-first repository governance and verification tools for AI coding agents.

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

92 installs/wk local only

Hookwarden — Webhook Integrity

by hookwarden

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

108 installs/wk local only

socket.help

by socket

Email inboxes, webhooks, mock APIs, 2FA codes, approvals and 170 tools for AI agents.

55 tools answering

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 91 of 91 checks got a reply (100.0%), average response time 350 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 in the form 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 350 ms on average, which is faster than 40% 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 51 times in the last week. Week over week that is -83%. 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?

The code is open source: it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at webhook-toolkit.com, which runs on its operator's own terms.