Developer · Local MCP server
Hooksense
Webhook & callback layer for AI agents: create a URL, wait_for_callback, and verify over MCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ozers/hooksense- Version
- 0.2.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-06
- Updated
- 2026-07-06
- Publisher
- ozers (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ozers) · how
- Repository
- github.com/ozers/hooksense-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @hooksense/mcp | 0.2.1 | stdio |
How to connect Hooksense
Hooksense runs locally from a Node.js package published to the npm registry: @hooksense/mcp version 0.2.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 @hooksense/mcp@0.2.1. It reads these environment variables: HOOKSENSE_TOKEN (required, secret) and HOOKSENSE_API; set them 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": {
"hooksense": {
"command": "npx",
"args": [
"-y",
"@hooksense/mcp@0.2.1"
],
"env": {
"HOOKSENSE_TOKEN": "<secret>",
"HOOKSENSE_API": "<value>"
}
}
}
}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 |
|---|---|
| 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 |
| 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 |
| 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 |
| Horry County Construction LeadsLive Horry County construction leads for low-voltage, networking, security, AV, POS, and electrical. | Remote · HTTPLive check: ✓ handshake |
| HosakaCompany facts for AI agents: which vendors a company uses, proven from DNS. Paid in USDC. | Local · stdio |