Developer · Remote MCP server
Webhook Studio
Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.webhook-studio/webhooks- Version
- 0.1.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-21
- Updated
- 2026-08-21
- Publisher
- com.webhook-studio
- Namespace
- Namespace verified by the MCP Registry via the domain webhook-studio.com · how
- Website
- webhook-studio.com/mcp/setup
- Repository
- github.com/lestertww/webhookstudio
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://webhook-studio.com/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- webhook-studio 0.1.1 · protocol 2025-06-18
- Tools discovered
17 - show names
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- Checked on
- 2026-10-05
How to connect Webhook Studio
Webhook Studio is a remote MCP server: there is nothing to install. Its endpoint is https://webhook-studio.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, webhook-studio.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More developer servers
| Server | Runs |
|---|---|
| webfetchSelf-hosted web search for LLM agents: search -> fetch -> rank pipeline with semantic caching. | Local · stdio |
| Webhook AdminSend, retry and monitor webhooks: manage endpoints, event types and API keys (OAuth). | Remote · HTTPLive check: sign-in required |
| Webhook Ai MCPWebhook Ai tools for AI agents. Capabilities: validate webhook signature, log webhook event, replay. | Local · stdio |
| Webhook Signature Fixture LabGenerates deterministic webhook HMAC-SHA256 fixtures and optionally verifies a supplied signature... | Remote · HTTPLive check: ✓ handshake |
| Webhook ToolkitWebhook URLs for AI agents: receive, wait for, replay, sign and verify webhooks (Stripe, GitHub…). | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| webhook.coReceive, inspect, replay and deliver webhooks - with signature verification and agent triggers. | Remote · HTTPLive check: sign-in required |
| Webhook.site MCP ServerCapture HTTP, email, and DNS callbacks with webhook.site from MCP clients. | Local · stdio |
| WebhookTest.netAnonymous webhook capture, inspection, waiting, and response configuration for AI agents. | Remote · HTTPLive check: ✓ handshake |