Developer · Remote MCP server
Hooklistener
Webhook, email, WebSocket and tunnel testing for AI agents: capture, wait, verify, replay.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.hooklistener/mcp- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-26
- Updated
- 2026-09-26
- Publisher
- com.hooklistener
- Namespace
- Namespace verified by the MCP Registry via the domain hooklistener.com · how
- Listed under
- Email MCP servers
- Website
- www.hooklistener.com/mcp
- Repository
- github.com/hooklistener/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.hooklistener.com/api/mcp | None |
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 to connect Hooklistener
Hooklistener is a remote MCP server: there is nothing to install. Its endpoint is https://app.hooklistener.com/api/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
| Server | Runs |
|---|---|
| HoneycombQuery Honeycomb observability data: traces, events, metrics, SLOs, triggers, and boards. | Remote · HTTPLive check: sign-in required |
| HoneyLabsHoneypot probe data: IP reputation, scanners, CVE probing, TLS and SSH fingerprints. | Remote · HTTPLive check: ✓ handshake |
| HookdenWebhook capture bins for agents: get a URL, wait for webhooks, set replies, verify signatures. | Remote · HTTPLive check: ✓ handshake |
| hookline.orgHookline MCP - create webhook endpoints, inspect requests, and validate payloads from AI agents. | Local · stdio |
| HookpulseDead-man switch for cron and webhooks: ingest URL, miss detection, alerts and a status feed. | Remote · HTTPLive check: ✓ handshake |
| HooksenseWebhook & callback layer for AI agents: create a URL, wait_for_callback, and verify over MCP. | Local · stdio |
| Hookwarden - Webhook IntegrityWebhook signature-verification audit. Stripe, GitHub, Shopify, Twilio +17. Local. Deterministic. | Local · stdio |
| horizOnDocs, live API tools and prompts for the horizOn game backend in Godot, Unity and Unreal. | Local · stdio |