Developer · Local MCP server
hookline.org
Hookline MCP - create webhook endpoints, inspect requests, and validate payloads from AI agents.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
org.hookline/mcp- Version
- 0.9.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-20
- Updated
- 2026-08-20
- Publisher
- org.hookline
- Namespace
- Namespace verified by the MCP Registry via the domain hookline.org · how
- Repository
- github.com/hookline-org/mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @hookline/mcp | 0.9.1 | stdio |
How to connect hookline.org
hookline.org runs locally from a Node.js package published to the npm registry: @hookline/mcp version 0.9.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @hookline/mcp@0.9.1. It reads the environment variable HOOKLINE_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@hookline/mcp@0.9.1"
],
"env": {
"HOOKLINE_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. 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 |
|---|---|
| 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 |
| HookdenWebhook capture bins for agents: get a URL, wait for webhooks, set replies, verify signatures. | Remote · HTTPLive check: ✓ handshake |
| 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 |
| Hookwarden - Webhook IntegrityWebhook signature-verification audit. Stripe, GitHub, Shopify, Twilio +17. Local. Deterministic. | Local · stdio |