Developer · Remote MCP server

webhook.co

Receive, inspect, replay and deliver webhooks - with signature verification and agent triggers.

Visit webhook.co's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
co.webhook/webhook
Version
1.0.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-07-23
Updated
2026-07-23
Publisher
co.webhook
Namespace
Namespace verified by the MCP Registry via the domain webhook.co · how
Website
docs.webhook.co/mcp/overview
Repository
github.com/webhook-co/webhook (folder apps/mcp)
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.webhook.co/mcpNone

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 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

How to connect webhook.co

webhook.co is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.webhook.co/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.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

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

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Webhook Ai MCPWebhook Ai tools for AI agents. Capabilities: validate webhook signature, log webhook event, replay.Local · stdioPyPI: webhook-ai-mcp
Webhook Signature Fixture LabGenerates deterministic webhook HMAC-SHA256 fixtures and optionally verifies a supplied signature...Remote · HTTPLive check: ✓ handshakemcp-factory.bowling-anthony.workers.dev
Webhook StudioKeyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic.Remote · HTTPLive check: ✓ handshakewebhook-studio.com
Webhook ToolkitWebhook URLs for AI agents: receive, wait for, replay, sign and verify webhooks (Stripe, GitHub…).Remote & Local · HTTP, stdioLive check: ✓ handshakewebhook-toolkit.com
Webhook.site MCP ServerCapture HTTP, email, and DNS callbacks with webhook.site from MCP clients.Local · stdioPyPI: webhook-mcp-server
WebhookTest.netAnonymous webhook capture, inspection, waiting, and response configuration for AI agents.Remote · HTTPLive check: ✓ handshakewebhooktest.net
Webmcpactionreceipt MCPPaid remote MCP for WebMCP action receipt MCP, structured receipts, audit logs, and reviewer-ready e.Remote · HTTPLive check: ✗ no handshakewebmcpactionreceipt.clauxel.com
WebnavA zero-LLM MCP server that replays recorded site maps instead of re-exploring browser routes.Local · stdionpm: @dikshanty94/webnav