Webhook Studio MCP server
com.webhook-studio/webhookswebhook-studio.comstreamable-httpv0.1.1Scanned
Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic.
17 tools: 1 can delete or cancel things, 5 change things and 11 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Webhook Studio MCP server can do
The Webhook Studio MCP server is published by webhook-studio.com, a domain the MCP Registry verified. It has 17 tools. It can delete or cancel things (1 tool: delete_bucket) and create or change data (5 tools: create_bucket, replay_event, forward_bucket, configure_verification and 1 more). 11 tools only read.
1 tool reads private data (get_bucket); 1 tool brings in text other people can write (get_bucket); 2 tools can send data out of your system (replay_event and forward_bucket). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 0.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
17 tools
Deletes or cancels 1Claude Code: deny
delete_bucketPermanently delete a webhook endpoint and its captured events.No findings
Why it is in this group
- The name "delete_bucket" says "delete": a word for removing or ending something.
- The description says "Permanently delete".
Description, as the server wrote it Permanently delete a webhook endpoint and its captured events.
Changes things 5Claude Code: ask
configure_verificationTurn on HMAC signature verification for a bucket using the provider's own signing secret (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
create_bucketProvision a new webhook endpoint (a "bucket") that captures incoming HTTP requests.No findings
Why it is in this group
- The name "create_bucket" says "create": a word for a change.
Description, as the server wrote it 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.
forward_bucketSet up standing forwarding from a bucket to a URL.Can send data outNo findings
Why it is in this group
- The description's first verb is "set": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
generate_typesGenerate types, a runtime validator, or a full handler from a learned schema — the payoff of the knowledge layer.No findings
Why it is in this group
- The name "generate_types" says "generate": a word for a change.
Description, as the server wrote it 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.
replay_eventRe-send a captured event to any URL — the test runner for a handler you just wrote.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Only reads 11Show 11 read-only tools
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.No findings
Why it is in this group
- The name "diff_schema" says "diff": a word for reading.
Description, as the server wrote it 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.
find_correlation_keysList the correlation-key candidates for a learned schema — the fields that look like identifiers (e.g.No findings
Why it is in this group
- The name "find_correlation_keys" says "find": a word for reading.
Description, as the server wrote it 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.
get_bucketFetch one webhook endpoint by id, including its url and inbox_url.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_bucket" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "inbox": it reads mail.
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Fetch one webhook endpoint by id, including its url and inbox_url.
get_eventFetch one captured event by id with its full headers, body, signature verification result (and failure reason), and every outbound delivery attempt.No findings
Why it is in this group
- The name "get_event" says "get": a word for reading.
Description, as the server wrote it 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.
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 recei…No findings
Why it is in this group
- The name "get_schema" says "get": a word for reading.
Description, as the server wrote it 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.
latest_eventGet the single most recent event captured by a bucket, optionally filtered by provider and event type.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it 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.
list_bucketsList your webhook endpoints.No findings
Why it is in this group
- The name "list_buckets" says "list": a word for reading.
Description, as the server wrote it 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.
list_deliveriesList outbound delivery attempts for a bucket, newest first, with the full request and response of each.No findings
Why it is in this group
- The name "list_deliveries" says "list": a word for reading.
Description, as the server wrote it 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".
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 sear…No findings
Why it is in this group
- The name "list_events" says "list": a word for reading.
Description, as the server wrote it 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.
list_schemasList the payload schemas Webhook Studio has learned from this account's real traffic, optionally filtered by provider and event_type.No findings
Why it is in this group
- The name "list_schemas" says "list": a word for reading.
Description, as the server wrote it 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.
wait_for_eventBlock until the next matching event arrives on a bucket, or until the timeout.No findings
Why it is in this group
- The name "wait_for_event" says "wait": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__webhooks__get_bucket"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:50 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 destructive, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://webhook-studio.com/mcp: tools/list returned 17 tools to an anonymous client, including delete_bucket (destructive), create_bucket (write), replay_event (write), forward_bucket (write), configure_verification (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:list_eventsOnly readsdescriptioninputSchema
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http webhooks https://webhook-studio.com/mcpclaude mcp add --transport http webhooks https://webhook-studio.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__webhooks__list_buckets",
"mcp__webhooks__get_bucket",
"mcp__webhooks__latest_event",
"mcp__webhooks__list_events",
"mcp__webhooks__get_event",
"mcp__webhooks__wait_for_event",
"mcp__webhooks__list_deliveries",
"mcp__webhooks__list_schemas",
"mcp__webhooks__get_schema",
"mcp__webhooks__diff_schema",
"mcp__webhooks__find_correlation_keys"
],
"ask": [
"mcp__webhooks__create_bucket",
"mcp__webhooks__replay_event",
"mcp__webhooks__forward_bucket",
"mcp__webhooks__configure_verification",
"mcp__webhooks__generate_types"
],
"deny": [
"mcp__webhooks__delete_bucket"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as webhooks. Review it before you use it.
Capability tags behind 3 rules
- mcp__webhooks__get_bucket private-data, untrusted-input
- mcp__webhooks__replay_event outbound
- mcp__webhooks__forward_bucket outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.webhook-studio/webhooks/verify?hash=8ebbd259380d220b958710e2dc625229e752c057612b6a37282a9ee7e239481e" | jq -e '.changed == false'Pinned hash 8ebbd259380d, from Nov 11, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.webhook-studio/webhooks/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.webhook-studio/webhooks)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:10 UTC.
Webhook Studio MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Webhook Studio MCP server safe?
- No scan can promise that. What its definitions show: 17 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Webhook Studio MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: delete_bucket.
Can the Webhook Studio MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Webhook Studio MCP server have?
- 17 tools: 1 destructive, 5 write, 11 read. delete_bucket, create_bucket, replay_event, forward_bucket, configure_verification, generate_types, list_buckets, get_bucket and 9 more.
Does the Webhook Studio MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Webhook Studio MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): replay_event and forward_bucket.
Has the Webhook Studio MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.