mcpbeat Sign in

Webhook Inspector MCP Server

by voronyuk-webhook Your server? Claim it
answering

Webhook Inspector is answering right now. Last checked 9 min ago.

Capture and inspect webhooks: create URLs, wait for requests, read headers and bodies, set replies.

Uptime history 13 days of history
13 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
229 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Webhook Inspector every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add inspector --transport http https://webhook.voronyuk.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://webhook.voronyuk.com/mcp
~/.codex/config.toml
[mcp_servers.inspector]
url = "https://webhook.voronyuk.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "inspector": {
      "url": "https://webhook.voronyuk.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "inspector": {
      "type": "http",
      "url": "https://webhook.voronyuk.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://webhook.voronyuk.com/mcp streamable-http sign-in 223 ms 9 min ago

Alternatives to Webhook Inspector

same job, measured the same way
Hookden
by pages-hookden

Webhook capture bins for agents: get a URL, wait for webhooks, set replies, verify signatures.

7 tools answering
WebhookTest.net
by webhooktest

Anonymous webhook capture, inspection, waiting, and response configuration for AI agents.

8 tools answering
Otterkit
by useotterkit

Tunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events.

46 installs/wk local only
Hookline
by hookline

Hookline MCP — create webhook endpoints, inspect requests, and validate payloads from AI agents.

75 installs/wk local only
HeySale — AI Website Salesperson
by heysale

Create and install an AI Website Salesperson for sales, qualification, and lead capture.

6 tools answering
Hooksense
by ozers

Webhook & callback layer for AI agents: create a URL, wait_for_callback, and verify over MCP.

44 installs/wk local only
Pipehero
by pipehero

Debug webhooks from your AI agent: inspect and replay captured webhooks on localhost.

25 tools answering
Hooklistener
by hooklistener

Webhook, email, WebSocket and tunnel testing for AI agents: capture, wait, verify, replay.

answering

Webhook Inspector — questions

Answers built from our own checks of this server.

Why is there no tool list for Webhook Inspector?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Webhook Inspector working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 229 ms. The bar chart above shows every period we have measured.
How do I connect Webhook Inspector?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Webhook Inspector?
No API key is involved. Webhook Inspector answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Webhook Inspector?
It answers our handshake in 229 ms on average, which is faster than 62% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.