Webhook Toolkit is a remote MCP server that gives an AI agent 10 tools, among them create_webhook_url, explain_webhook_request, get_webhook_request. It answers at https://webhook-toolkit.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 23 September 2026; the last check, on 6 November 2026, succeeded.
Webhook URLs for AI agents: receive, wait for, replay, sign and verify webhooks (Stripe, GitHub…).
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 con Inputs: name |
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; Inputs: token, request_id, mode, language |
get_webhook_request | Return one captured request in full (headers, raw body, detected provider/event). Inputs: token, request_id |
list_webhook_requests | List the most recent requests captured by a webhook URL, newest first (summaries; use get_webhook_request for one full request). Inputs: token, limit |
list_webhook_urls | List the webhook URLs of the account behind the API key (requires an API key). |
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 (` Inputs: token, request_id, target_url |
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. Inputs: token, status, body, content_type |
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 t Inputs: provider, secret, payload, event_type, target_url |
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, twili Inputs: provider, secret, raw_body, signature, timestamp, url |
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 Inputs: token, timeout_seconds, after |
Every block below points at https://webhook-toolkit.com/mcp. Pick your client and copy.
claude mcp add --transport http webhook-toolkit https://webhook-toolkit.com/mcp
{
"mcpServers": {
"webhook-toolkit": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://webhook-toolkit.com/mcp"]
}
}
}{
"mcpServers": {
"webhook-toolkit": {
"url": "https://webhook-toolkit.com/mcp"
}
}
}{
"servers": {
"webhook-toolkit": {
"type": "http",
"url": "https://webhook-toolkit.com/mcp"
}
}
}{
"context_servers": {
"webhook-toolkit": {
"url": "https://webhook-toolkit.com/mcp"
}
}
}{
"mcpServers": {
"webhook-toolkit": {
"serverUrl": "https://webhook-toolkit.com/mcp"
}
}
}{
"mcpServers": {
"webhook-toolkit": {
"url": "https://webhook-toolkit.com/mcp"
}
}
}name: Webhook Toolkit
version: 0.0.1
schema: v1
mcpServers:
- name: Webhook Toolkit
type: streamable-http
url: https://webhook-toolkit.com/mcp{
"mcpServers": {
"webhook-toolkit": {
"httpUrl": "https://webhook-toolkit.com/mcp"
}
}
}{
"mcpServers": {
"webhook-toolkit": {
"type": "http",
"url": "https://webhook-toolkit.com/mcp"
}
}
}{
"mcpServers": {
"webhook-toolkit": {
"url": "https://webhook-toolkit.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fwebhook-toolkit.com%2Fmcp&type=streamable_http&id=webhook-toolkit&name=Webhook%20Toolkit
It answered our last check on 6 November 2026 in 239 ms. Over 4 checks since 23 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
10, as returned by the server's own tools/list on 9 November 2026: create_webhook_url, explain_webhook_request, get_webhook_request, list_webhook_requests, list_webhook_urls, replay_webhook_request, set_webhook_response, sign_webhook_payload, and 2 more.
It answered our last check on 6 November 2026 in 239 ms. Over 4 checks since 23 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://webhook-toolkit.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.the-kipdev. Endpoint host: webhook-toolkit.com. ARD identifier: urn:air:io.github.the-kipdev:mcp:webhook-toolkit.
First indexed 18 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.