Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Webhook Studio

REMOTE · WEBHOOK-STUDIO.COM

Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic.

−1 this week 75 Trust /100

Last scanned (21 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2215 tokens (~130/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_bucket" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 1 Nov 26 −1
    • Tool “list_events” rewrote its description, which is the text the model reads security
    • “list_events” reworded the description of “q” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://webhook-studio.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=webhook-studio.com CN=YE2,O=Let's Encrypt,C=US 14 Sept 2026 13 Dec 2026 ECDSA 256 ECDSA-SHA384 605d8b9f6623de7a7da725e9450ca26a55a
SANs: webhook-studio.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of webhook-studio.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
webhook-studio.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://webhook-studio.com/mcp Verified 200
http (plaintext) http://webhook-studio.com/mcp HTTPS enforced 301 https://webhook-studio.com/mcp
MCP tools · 17 exposed · ~2,119 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
configure_verification ~164

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 the same call; the signature scheme is auto-detected from the header shape.

NameTypeReqDescription
bucket_idstringyesThe endpoint id.
header_namestring–Signature header to read (auto-detected if omitted).
hmac_enabledboolean–Enable verification.
on_failurestring–What to do with a failed signature.
secretstring–The provider's signing secret (≥16 chars).
tolerance_secondsnumber–Max timestamp skew allowed, in seconds.

No output schema declared.

No examples provided.

create_bucket ~136

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 stable name like "acme-api:stripe" — so you can re-find this exact bucket later with list_buckets after losing context.

NameTypeReqDescription
environmentstring–Deployment environment.
external_refstring–Your own stable identifier (unique per account) for idempotent re-provisioning and re-finding.
namestring–Human label for the bucket.

No output schema declared.

No examples provided.

delete_bucket ~30

Permanently delete a webhook endpoint and its captured events.

NameTypeReqDescription
bucket_idstringyesThe endpoint id.

No output schema declared.

No examples provided.

diff_schema ~107

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. from defaults to the version before to.

NameTypeReqDescription
fromstring–Baseline version number (defaults to the one before "to").
schema_idstringyesThe schema id.
tostring–Target version number, or "current".

No output schema declared.

No examples provided.

find_correlation_keys ~115

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 Stripe payment_intent across created -> succeeded, a GitHub PR across its events). Derived from real traffic, so it reflects what THIS account actually receives.

NameTypeReqDescription
schema_idstringyesThe schema id.
versionstring–Version number, or "current" (the default).

No output schema declared.

No examples provided.

forward_bucket ~155

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 rule in one call.

NameTypeReqDescription
bucket_idstringyesThe endpoint id.
condition_treeobject–A condition tree (AND/OR of field comparisons) to forward only matching events. Mutually exclusive with forward_all.
forward_allboolean–Forward every event unconditionally.
namestring–Optional label for the destination.
rule_namestring–Optional name for the routing rule when using condition_tree.
urlstringyesDestination URL to forward to.

No output schema declared.

No examples provided.

generate_types ~175

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, instead of a plausible-but-wrong guess from a model's memory of the provider docs. Pass lang for a bare type (typescript / json-schema / zod), or framework (next / express) for a ready-to-paste handler that validates and hands back a fully-typed event.

NameTypeReqDescription
frameworkstring–Return a ready-to-paste handler scaffold instead of a bare type. Overrides lang.
langstring–Output format for a bare type.
schema_idstringyesThe schema id.
versionstring–Version number, or "current" (the default).

No output schema declared.

No examples provided.

get_bucket ~33

Fetch one webhook endpoint by id, including its url and inbox_url.

NameTypeReqDescription
bucket_idstringyesThe endpoint id.

No output schema declared.

No examples provided.

get_event ~64

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

NameTypeReqDescription
event_idstringyesThe event id.

No output schema declared.

No examples provided.

get_schema ~79

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.

NameTypeReqDescription
schema_idstringyesThe schema id.
versionstring–Version number, or "current" (the default).

No output schema declared.

No examples provided.

latest_event ~124

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 matches, so you never index into an empty list.

NameTypeReqDescription
bucket_idstringyesThe endpoint id.
providerstring–Filter to a provider attributed at ingest (e.g. stripe, github).
typestring–The provider's own event name, matched exactly (e.g. payment_intent.succeeded).

No output schema declared.

No examples provided.

list_buckets ~68

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.

NameTypeReqDescription
external_refstring–Return only the bucket with this exact external_ref.

No output schema declared.

No examples provided.

list_deliveries ~123

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

NameTypeReqDescription
bucket_idstringyesThe endpoint id.
cursorstring–Pagination cursor from a previous response.
limitnumber–Max deliveries to return (1–100, default 20).
sourcestring–Delivery source.
successboolean–Filter to succeeded (true) or failed (false) deliveries.

No output schema declared.

No examples provided.

list_events ~289

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 search over body, content type, method, type and labels; space-separated terms must ALL match, double quotes for an exact phrase, and key:value filters by a label this bucket defines). Use cursor for the next page.

NameTypeReqDescription
bucket_idstringyesThe endpoint id.
cursorstring–Pagination cursor from a previous response.
limitnumber–Max events to return (1–100, default 20).
methodstring–HTTP method (GET, POST, ...).
providerstring–Filter to a provider (e.g. stripe, github).
qstring–Case-insensitive search over body/content-type/method/type/labels. Space-separated terms must all match; use double quotes for an exact phrase, and key:value to filter by a label name and exact value.
signature_validboolean–Only events whose signature verification passed/failed.
sincestring–Only events at or after this time (ISO 8601 or YYYY-MM-DD).
typestring–The provider's own event name, matched exactly.
untilstring–Only events at or before this time.

No output schema declared.

No examples provided.

list_schemas ~101

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 after old events are gone. Start here to discover what you can generate types or diffs for.

NameTypeReqDescription
event_typestring–The provider's own event name.
providerstring–Filter to a provider.

No output schema declared.

No examples provided.

replay_event ~211

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 with a different secret, pass resign_with (the dev's own signing secret) so the payload is re-signed and their verification code passes unmodified. Returns the response status, latency and body.

NameTypeReqDescription
bodystring–Replacement request body (defaults to the captured body).
event_idstringyesThe event id to replay.
headersobject–Header overrides layered on top of the preserved set.
preserve_headersboolean–Replay the captured headers verbatim (default true).
resign_withstring–Signing secret to re-sign the payload with (≥16 chars).
signature_headerstring–Header name for resign_with (default x-signature).
urlstringyesDestination URL to send it to.

No output schema declared.

No examples provided.

wait_for_event ~145

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 arrives. Filters (provider, type) mean unrelated traffic does not wake it. Returns the event, or nothing if it times out.

NameTypeReqDescription
bucket_idstringyesThe endpoint id.
providerstring–Only resolve on an event from this provider.
timeoutnumber–Seconds to wait (1–55, default 30).
typestring–Only resolve on this event type.

No output schema declared.

No examples provided.

Install

How do I install the Webhook Studio MCP server?

Webhook Studio is a hosted endpoint at https://webhook-studio.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · webhook-studio.com

# add to Claude Code
claude mcp add --transport http com-webhook-studio-webhooks 'https://webhook-studio.com/mcp'
Common questions

What is the Webhook Studio MCP server?

Webhook Studio is an MCP server listed in the public MCP registry as com.webhook-studio/webhooks. Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic. This page covers its hosted endpoint (https://webhook-studio.com/mcp).

Is the Webhook Studio MCP server safe to use?

Webhook Studio scores 75 out of 100 on VerifyMCP. 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 Studio MCP server expose?

Webhook Studio exposes 17 tools: create_bucket, list_buckets, get_bucket, delete_bucket, latest_event, and 12 more. Their descriptions and schemas cost roughly 2,119 tokens of context every time the server is loaded.

Does the Webhook Studio MCP server require authentication?

No. We connected to Webhook Studio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Webhook Studio MCP server still maintained?

Webhook Studio is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.