hooks.bot gives you a disposable endpoint that records every request sent to it, and a debugger that works out why a webhook signature will not verify — rebuilding the signature every way it could plausibly have been made and naming the step that differs. No account, no API key.
Your coding agent can drive all of it over MCP at
https://hooks.bot/mcp —
create an endpoint, wait for the webhook to land, and diagnose it without anything
being copied by hand. Tools: create_endpoint, wait_for_request, list_requests,
get_request, diagnose_signature.
Understands Stripe, GitHub, Svix / Standard Webhooks, Shopify, Slack, Paddle and Twilio. Docs: /docs. Machine-readable reference: /llms.txt.
Check that you verify the original request bytes before parsing JSON. Re-serializing a payload, changing whitespace, adding a newline to the secret, choosing the wrong credential or using the wrong digest encoding can all change the signature. Paste the raw body and signature headers into the debugger to test these differences.
The browser debugger performs signature diagnosis locally using Web Crypto and does not send your signing secret to an API. Captured requests are stored on the server, so do not send secrets to your capture URL. The separate MCP diagnosis tool runs server-side when an agent deliberately supplies a secret.
Each endpoint expires after 24 hours and retains at most 200 requests. Stored bodies are truncated at 64KB, and requests over 1MB are rejected. Anyone with the endpoint URL can read its captures. Download a request as JSON before expiry if you need a local copy, and review it for sensitive data before sharing.
Yes. Connect to the MCP server at https://hooks.bot/mcp without an account or API key. An agent can create an endpoint, wait for a webhook, read captures and diagnose a signature. The documentation explains the tools and HTTP API.