HookReplay.dev
hookVM
Webhook.site
ngrok
Hooklistener
Webhooks.cc
RequestBin
Webhook Relay
Emisar.dev
Emisar is the last MCP server youโll need to install: a Zero-Trust gateway connecting Claude, Cursor, ChatGPT, and any AI agent to your infrastructure. One server handles production access, debugging, alerts, and internal operations, with new capabilities added as packs. Agents can inspect real production state, debug what they shipped, and help resolve incidents. Safe reads run automatically; policy allows, blocks, or routes risky actions for approval. No SSH keys, VPNs, remote shells, or standing shell access โ and every call is recorded.
HookReplay.dev Emisar.devNo features have been listed yet.
HookReplay.dev's answer
Still early โ just launched. Currently used by indie developers and small teams debugging Stripe and Shopify integrations. No big logos yet. Focused on building a great product first.
Emisar.dev's answer:
HookReplay.dev's answer
With ngrok, every code change means triggering another webhook. Add a log? Trigger again. Set a breakpoint? Too late, it timed out. Trigger again. With HookReplay, you trigger once. Then replay 100 times while you debug. Same webhook. Same payload. Unlimited attempts to get your code right. That's not a small difference โ it's hours saved per debugging session.
Emisar.dev's answer:
Choose emisar when you want an agent to keep investigating and handling routine operations without handing it SSH credentials or supervising every call. Compared with raw shell access, copy-paste workflows, or one-off MCP servers, emisar provides reviewed action contracts, host-level enforcement, risk-based policy, scoped access, approvals, pack integrity checks, and a durable audit trail. It is built specifically for governed infrastructure access rather than generic automation.
HookReplay.dev's answer
Developers who integrate third-party webhooks Stripe, Shopify, GitHub, Twilio, Paddle, etc. Basically anyone who's ever clicked "Send test webhook" more times than they'd like to admit.
Emisar.dev's answer:
emisar is for SRE, DevOps, platform engineering, infrastructure, and security teams that want AI agents to inspect and operate production systems. It is especially relevant to teams managing multiple Linux hosts, clusters, databases, cloud services, or regulated environments where unrestricted shell access and incomplete audit records are unacceptable.
HookReplay.dev's answer
11pm on a Sunday. A customer's Stripe payment went through, but their subscription wasn't created. I needed to debug the webhook handler. Set up ngrok. Triggered a test payment. Added a log statement. Triggered again. Set a breakpoint โ webhook timed out before I could step through. Triggered again. Changed the URL in Stripe because ngrok restarted. Triggered again. Three hours later, I found a typo in my event type check. I remember thinking: I just re-triggered the same webhook 40+ times. Why can't I just capture it once and replay it until I find the bug? That's the moment HookReplay was born. The tool I wished existed that night.
Emisar.dev's answer:
Founder Andrii Dryga spent a decade working as a CTO, full-stack engineer, SRE, and DevOps engineer. He experienced the cost of running the wrong command on the wrong cluster, while also seeing AI solve operational problems in seconds. emisar grew from the need to preserve both truths: AI agents are useful, and production access must remain bounded. Its answer is to give agents a reviewed catalog of operations instead of a blank terminal.
HookReplay.dev's answer
ASP.NET Core for the backend, PostgreSQL for storage, WebSockets for real-time forwarding to the CLI. The CLI is built in .NET and distributed via npm โ runs on macOS, Windows, and Linux. Nothing fancy. Boring tech that works.
Emisar.dev's answer:
The hosted control plane and operator interface use Elixir, Phoenix, LiveView, PostgreSQL, and Tailwind CSS. The host runner and MCP bridge are written in Go. Action packs use YAML and JSON Schema, while production infrastructure is managed with Terraform on Google Cloud. The system communicates through MCP, OAuth 2.1, TLS, and WebSockets.
HookReplay.dev's answer
Three things most webhook tools don't do: 1- Replay the same webhook unlimited times 2- Edit payloads before replaying (test edge cases) 3- Keep a full history of every webhook received HookReplay does all three, plus real-time forwarding like ngrok.
Emisar.dev's answer:
emisar lets AI agents work on real infrastructure without giving them a shell. Agents choose from a finite catalog of typed, versioned actions. Policy decides what runs, what requires approval, and what is denied, while an outbound-only runner verifies the action again on the host. New capabilities arrive as packs behind the same MCP integration, and every request is recorded in both a searchable audit trail and a tamper-evident host journal. [
hookVM - Receive, deliver, and debug webhooks with reliability, observability, and developer-first tooling.
Webhook.site - Instantly generate a free, unique URL and email address to test, inspect, and automate (with a visual workflow editor and scripts) incoming HTTP requests and emails.
ngrok - ngrok enables secure introspectable tunnels to localhost webhook development tool and debugging tool.
Hooklistener - The developer-friendly webhook inspector with real-time team collaboration, request replay, and permanent history.
Webhooks.cc - Capture and inspect webhooks in real time. Send signed provider test webhooks, forward to localhost with the CLI, test in CI with the SDK, and debug faster with MCP.
RequestBin - RequestBin.com gives you a URL that collects requests you send to it so you can inspect them in a...