This product was not featured by Product Hunt yet.
It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).

Product Thumbnail

Webhook Catcher

The MCP-native webhook catcher for AI builders

Developer Tools
Visit WebsiteSee on Product Hunt

Hunted byAnjuman RajAnjuman Raj

• New in v2: your AI agent reads captures over MCP, so Claude Code or Cursor can debug the failing webhook for you • Instantly create disposable webhook URLs — no sign-up • Inspect every payload and customise responses • Watch requests land live, then replay or forward to localhost • Free forever — spend less time debugging, more time building

Top comment

Hey Product Hunt 👋 I built Webhook Catcher because webhooks kept making me feel stupid. Every time I wired up Stripe, Clerk, or GitHub, something wouldn't fire — and I could never tell whose fault it was. Did the provider not send it, or did my handler break? The only way to find out was to deploy a console.log, trigger the event again, and squint at the logs. A deploy per print statement. It's 2026 and debugging a webhook still felt like doing it blindfolded. So I built the tool I wanted: mint a URL in seconds (no sign-up), and watch every request land live — headers, payload, all of it. Replay any request to your localhost, edited or as-is. See exactly what Stripe actually sent, not what the docs claim it sends. For v2, I added the part I care about most: your AI agent can now read your webhooks. - If you write code: there's a token-scoped REST API, so you can pull captures straight into your scripts, tests, and CI. - If you build with an agent — Claude Code, Cursor, or you're a vibe coder who ships with AI and isn't totally sure what a webhook even is — there's a built-in MCP server. Connect it once and your agent reads the failing request itself and fixes your handler. You don't have to understand the payload. Your AI does. That last part is why I built v2. The people who struggle most with webhooks are often the ones building with AI for the first time — and they're exactly the ones who shouldn't have to become webhook experts just to ship a payment flow. It's free. No account, no pricing, no "premium beta." Secret headers are redacted before anything is stored, and captures auto-delete after 30 days. I'd love your feedback — especially: what's the webhook that's wasted the most of your life? — Anjuman

Comment highlights

How does the MCP integration actually work under the hood — does the agent pull captures on demand or stream them as they come in?

How does the MCP integration actually expose the captured payloads to my agent, and does it stream in real time or only when I explicitly ask it to check for new requests?

how does the MCP integration handle auth when my AI agent pulls in captures — is that gated behind a paid plan or open from the start?

finally something that lets claude look at my failing webhooks directly through MCP, absolute game changer

does the MCP integration actually let the agent modify or just read the captured payloads, and are there any caps on request volume since it's free forever?

Finally something that lets me spin up a webhook endpoint in seconds without signing up for yet another service. The MCP integration is genuinely useful, my Claude Code agent pulled the payload straight in and pointed me to the auth bug in seconds.

how does the MCP integration actually work under the hood, does my agent need any specific setup to start reading the captures or does it just connect automatically

Finally something that makes webhook debugging not painful. The MCP integration actually works, had Claude Code walk through a Stripe payload and spot my missing event filter in under a minute. Being able to forward to localhost without yet another signup is a nice bonus.

Fired off a test webhook and saw the payload in seconds, zero setup was honestly kind of shocking. The MCP bit is clever too, got Cursor to walk through what went wrong without me copy-pasting anything.

How does the MCP integration actually work under the hood, does Claude Code need to spin up its own server to talk to the captures or is there a hosted endpoint I point it at?

About Webhook Catcher on Product Hunt

The MCP-native webhook catcher for AI builders

Webhook Catcher was submitted on Product Hunt and earned 8 upvotes and 15 comments, placing #75 on the daily leaderboard. • New in v2: your AI agent reads captures over MCP, so Claude Code or Cursor can debug the failing webhook for you • Instantly create disposable webhook URLs — no sign-up • Inspect every payload and customise responses • Watch requests land live, then replay or forward to localhost • Free forever — spend less time debugging, more time building

Webhook Catcher was featured in Developer Tools (515.9k followers) on Product Hunt. Together, these topics include over 76.1k products, making this a competitive space to launch in.

Who hunted Webhook Catcher?

Webhook Catcher was hunted by Anjuman Raj. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.

Want to see how Webhook Catcher stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.