Developer · Remote MCP server
Hookden
Webhook capture bins for agents: get a URL, wait for webhooks, set replies, verify signatures.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.pages.hookden/hookden- Version
- 1.3.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-31
- Updated
- 2026-08-31
- Publisher
- dev.pages.hookden
- Namespace
- Namespace verified by the MCP Registry via the domain hookden.pages.dev or a parent domain of it · how
- Website
- hookden.pages.dev
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://hookden.pages.dev/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 200)
- Handshake
- hookden 1.3.0 · protocol 2025-06-18
- Tools discovered
- 7:
create_bin,list_captures,get_capture,wait_for_capture,send_test_webhook,set_response,verify_signature - Checked on
- 2026-10-05
How to connect Hookden
Hookden is a remote MCP server: there is nothing to install. Its endpoint is https://hookden.pages.dev/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 |
|---|---|
| honesty-mcpMCP server exposing 11 honesty-SDK kits (grounding, trust, audit, corroboration) as agent tools. | Local · stdio |
| HoneycheckBefore buying a token on Arc, test whether it can be sold back. Free, or 1-5c a call over x402. | Local · stdio |
| 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 |
| hookline.orgHookline MCP - create webhook endpoints, inspect requests, and validate payloads from AI agents. | Local · stdio |
| HooklistenerWebhook, email, WebSocket and tunnel testing for AI agents: capture, wait, verify, replay. | Remote · HTTPLive check: sign-in required |
| 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 |