Webhook Studio
v0.1.1Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic.
Endpoint health
online- Last checked
- 11/20/2026, 8:17:16 AM
- Latency
- 40 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.webhook-studio%2Fwebhooks
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.webhook-studio/webhooks": {
"url": "https://webhook-studio.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
17 shown · authentication unknown
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 the same call; the signature scheme is auto-detected from the header shape.
Schema valid · SHA-256 a0666aae0ea5…
View input schema
{ "type": "object", "properties": { "bucket_id": { "type": "string", "description": "The endpoint id." }, "secret": { "type": "string", "description": "The provider's signing secret (≥16 chars)." }, "hmac_enabled": { "type": "boolean", "description": "Enable verification." }, "header_name": { "type": "string", "description": "Signature header to read (auto-detected if omitted)." }, "tolerance_seconds": { "type": "number", "description": "Max timestamp skew allowed, in seconds." }, "on_failure": { "type": "string", "description": "What to do with a failed signature.", "enum": [ "reject", "accept_log" ] } }, "required": [ "bucket_id" ], "additionalProperties": false }create_bucket
Provision a new webhook endpoint (a "bucket") that captures incoming HTTP requests. Start here when building, testing or debugging a webhook handler. Works with NO account and no API key: in that case it returns endpoint_id (use it as bucket_id), ingest_url (point the provider at it), inbox_url (the live view to hand the human) and api_token — pass that api_token as the `token` argument of the event, replay and delivery tools. A keyless bucket and its token expire after 3 days and every keyless call mints a new one (5 per hour), so call this once and reuse the result. With an API key it instead returns id, url, inbox_url and the signing secret, the bucket is permanent, and external_ref — your own stable name like "acme-api:stripe" — lets you re-find it later with list_buckets.
Connections
streamable-http
https://webhook-studio.com/mcp