Webhook Studio is an MCP server with 17 tools an agent can call, among them configure_verification, create_bucket, delete_bucket. It answers at https://webhook-studio.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 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
configure_verification | Turn on HMAC signature verification for a bucket using the provider's own signing secret (e.g. Stripe's whsec_). This is how you finish a "verified webhook" integration end to end. Set secret to the provider secret and hmac_enabled:true in Inputs: bucket_id, secret, hmac_enabled, header_name, tolerance_seconds, on_failure |
create_bucket | Provision a new webhook endpoint (a "bucket") that captures incoming HTTP requests. Returns its id, public ingest url to point a provider at, inbox_url (the live human view to hand back), and signing secret. Pass external_ref — your own sta Inputs: name, environment, external_ref |
delete_bucket | Permanently delete a webhook endpoint and its captured events. Inputs: bucket_id |
diff_schema | Compare two versions of a learned schema and get exactly which fields were added, removed or changed type, each flagged as breaking or not. This is the "why did my handler start failing" answer, produced without reading a single payload. fr Inputs: schema_id, from, to |
find_correlation_keys | List the correlation-key candidates for a learned schema — the fields that look like identifiers (e.g. data.object.id), ranked by how consistently they appear. These are the fields to group events by when reconstructing a lifecycle (a Strip Inputs: schema_id, version |
forward_bucket | Set up standing forwarding from a bucket to a URL. Pass forward_all:true to forward every event, or condition_tree to forward only matching events (same AND/OR condition grammar the routing engine uses). Creates the destination and routing Inputs: bucket_id, url, name, forward_all, condition_tree, rule_name |
generate_types | Generate types, a runtime validator, or a full handler from a learned schema — the payoff of the knowledge layer. Everything is derived from the payloads this account ACTUALLY received, with genuinely-optional fields marked optional, instea Inputs: schema_id, lang, framework, version |
get_bucket | Fetch one webhook endpoint by id, including its url and inbox_url. Inputs: bucket_id |
get_event | Fetch one captured event by id with its full headers, body, signature verification result (and failure reason), and every outbound delivery attempt. This is how you find out whether your forward actually reached its target and what came bac Inputs: event_id |
get_schema | Fetch one learned schema with every field, its type, whether it is optional, and how often it actually appears — the real shape of the payload, derived from what this account received rather than guessed from training data. Inputs: schema_id, version |
latest_event | Get the single most recent event captured by a bucket, optionally filtered by provider and event type. Returns one event with its headers, body and delivery results — the one-shot answer to "what did Stripe last send me". 404 if nothing mat Inputs: bucket_id, provider, type |
list_buckets | List your webhook endpoints. Pass external_ref to fetch the specific bucket you created earlier under that name — this is how you re-anchor after losing the conversation, since you never need to have stored the bucket id. Inputs: external_ref |
list_deliveries | List outbound delivery attempts for a bucket, newest first, with the full request and response of each. Pass success:false to see only failures — the direct answer to "which of my forwards are broken and why". Inputs: bucket_id, success, source, limit, cursor |
list_events | List events captured by a bucket, newest first, with composable filters: since/until (ISO 8601 or YYYY-MM-DD), provider, type, method, signature_valid, and q (case-insensitive substring over body, content type, method, type and labels). Use Inputs: bucket_id, since, until, provider, type, method |
list_schemas | List the payload schemas Webhook Studio has learned from this account's real traffic, optionally filtered by provider and event_type. These outlive the payloads they were learned from, so this answers "what shapes do I know about" even afte Inputs: provider, event_type |
replay_event | Re-send a captured event to any URL — the test runner for a handler you just wrote. preserve_headers defaults to true so the original signature header (e.g. Stripe-Signature) arrives intact. If you changed the body or the receiver verifies Inputs: event_id, url, preserve_headers, headers, body, resign_with |
wait_for_event | Block until the next matching event arrives on a bucket, or until the timeout. Use this to turn "go click Send test webhook in Stripe" into a synchronous step: call it, tell the human to trigger the event, and it returns as soon as one arri Inputs: bucket_id, timeout, provider, type |
Every block below points at https://webhook-studio.com/mcp. Pick your client and copy.
claude mcp add --transport http webhook-studio https://webhook-studio.com/mcp
{
"mcpServers": {
"webhook-studio": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://webhook-studio.com/mcp"]
}
}
}{
"mcpServers": {
"webhook-studio": {
"url": "https://webhook-studio.com/mcp"
}
}
}{
"servers": {
"webhook-studio": {
"type": "http",
"url": "https://webhook-studio.com/mcp"
}
}
}{
"context_servers": {
"webhook-studio": {
"url": "https://webhook-studio.com/mcp"
}
}
}{
"mcpServers": {
"webhook-studio": {
"serverUrl": "https://webhook-studio.com/mcp"
}
}
}{
"mcpServers": {
"webhook-studio": {
"url": "https://webhook-studio.com/mcp"
}
}
}name: Webhook Studio
version: 0.0.1
schema: v1
mcpServers:
- name: Webhook Studio
type: streamable-http
url: https://webhook-studio.com/mcp{
"mcpServers": {
"webhook-studio": {
"httpUrl": "https://webhook-studio.com/mcp"
}
}
}{
"mcpServers": {
"webhook-studio": {
"type": "http",
"url": "https://webhook-studio.com/mcp"
}
}
}{
"mcpServers": {
"webhook-studio": {
"url": "https://webhook-studio.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fwebhook-studio.com%2Fmcp&type=streamable_http&id=webhook-studio&name=Webhook%20Studio
It answered our last check on 19 October 2026 in 172 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by webhook-studio.com and served from webhook-studio.com, the vendor's own domain: https://webhook-studio.com/mcp.
17, as returned by the server's own tools/list on 11 September 2026: configure_verification, create_bucket, delete_bucket, diff_schema, find_correlation_keys, forward_bucket, generate_types, get_bucket, and 9 more.
It answered our last check on 19 October 2026 in 172 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://webhook-studio.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: com.webhook-studio. Endpoint host: webhook-studio.com. ARD identifier: urn:air:com.webhook-studio:mcp:webhooks.
First indexed 10 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.