com.webhook-studio/webhooks

Webhook Studio

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

Endpointhttps://webhook-studio.com/mcp (streamable-http)
Registry version0.1.1
Now17 tools · grade D (59) · pin ts_1c245110df362c36b88566e4e8efe2fa · protocol 2025-06-18
First / last listed2026-11-10 01:29 UTC / 2026-11-10 01:29 UTC
Grade over time2026-11-10: D (59), 17 tools

Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.

Timeline

First listing · 2026-11-10 01:29 UTC
17 tools, grade D (59)

Tools: create_bucket list_buckets get_bucket delete_bucket latest_event list_events get_event wait_for_event replay_event forward_bucket list_deliveries configure_verification list_schemas get_schema diff_schema generate_types find_correlation_keys

Current tools (17)

create_bucketProvision 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.
params: name, environment, external_ref
list_bucketsList 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.
params: external_ref
get_bucketFetch one webhook endpoint by id, including its url and inbox_url.
params: bucket_id*
delete_bucketPermanently delete a webhook endpoint and its captured events.
params: bucket_id*
latest_eventGet 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.
params: bucket_id*, provider, type
list_eventsList 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.
params: bucket_id*, since, until, provider, type, method, signature_valid, q, limit, cursor
get_eventFetch 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.
params: event_id*
wait_for_eventBlock 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.
params: bucket_id*, timeout, provider, type
replay_eventRe-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
params: event_id*, url*, preserve_headers, headers, body, resign_with, signature_header
forward_bucketSet 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.
params: bucket_id*, url*, name, forward_all, condition_tree, rule_name
list_deliveriesList 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".
params: bucket_id*, success, source, limit, cursor
configure_verificationTurn 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.
params: bucket_id*, secret, hmac_enabled, header_name, tolerance_seconds, on_failure
list_schemasList 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.
params: provider, event_type
get_schemaFetch 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.
params: schema_id*, version
diff_schemaCompare 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.
params: schema_id*, from, to
generate_typesGenerate 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 / ex
params: schema_id*, lang, framework, version
find_correlation_keysList 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.
params: schema_id*, version

Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.