Hookpulse is an MCP server with 22 tools an agent can call, among them api_index, billing, contact. It answers at https://hookpulse.net/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Dead-man switch for cron and webhooks: ingest URL, miss detection, alerts and a status feed.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
api_index | Full index of the HookPulse API. |
billing | Free plan, x402 prices and the trial offer: sign-up with a confirmed e-mail = 90 days without the usage paywall (`trial` field; with a session it shows the state). |
contact | Support. Agent without captcha → 402 $0.10 x402. After the 1st message: 429 + Retry-After (backoff). Inputs: name, email, message, tipo, empresa, site |
create_endpoint | Creates a dead-man endpoint. Use cron+tz+grace_sec for a real schedule (mutually exclusive with interval_sec) or interval_sec for plain silence detection. max_duration_sec alerts when a run opened by /in/:id/start hangs. May return 402 x402 Inputs: guest_token, name, interval_sec, cron, paused_until, tz |
create_guest | Creates a guest token hp_… |
delete_endpoint | Removes the owner's endpoint. Inputs: guest_token, id |
get_endpoint | Status of one endpoint (use the endpoint token if you have it). Inputs: id, token, guest_token |
health | Liveness. |
import_crontab | Reads a crontab and proposes one monitor per scheduled line. Without apply=1 nothing is written; the proposal says what was ignored and why. Passwords in the command are redacted. Inputs: guest_token, crontab, apply |
ingest_key | Returns (minting the first time) the key for /in/<key>/<slug>, where a ping creates its own monitor inside the free tier. Instruments a whole fleet with no setup call per job. Inputs: guest_token |
ingest_key_rotate | Rotates the ingest key; the previous one stops creating monitors. Existing ones keep working. Inputs: guest_token |
list_endpoints | Lists the guest's/session's endpoints. Inputs: guest_token |
list_events | Latest ingest pings. Inputs: id, token, guest_token |
list_templates | Ingest snippets and the JSON HookPulse POSTs on a miss. |
ping_ingest | Simulates the cron: GET on /in/:id. Inputs: id |
ping_slug | Ping that creates its own monitor on the first hit. Same slug = same monitor; 402 when the free tier is full, and then nothing is written. Inputs: ingestKey, slug |
pricing | Current public prices and free allowances; no charge. |
signal_exit_code | The shell exit status: 0 behaves like a ping, 1-255 record the code as a failure. Inputs: id, exit_code |
signal_fail | Says the run FAILED. The ingest never sends e-mail: the 5-minute cron turns it into an alert with reason `fail`, under the same one-per-24h cap. Inputs: id |
signal_start | Says the run STARTED. Does not clear the dead-man clock: a routine that starts and hangs still becomes a miss. The next success records the duration. Inputs: id |
status_feed_rotate | Rotates the status feed token; the previous URL stops working. Inputs: guest_token |
status_feed_url | Public URL (JSON and RSS) with the status of all the owner's endpoints. Inputs: guest_token |
Every block below points at https://hookpulse.net/mcp. Pick your client and copy.
claude mcp add --transport http hookpulse https://hookpulse.net/mcp
{
"mcpServers": {
"hookpulse": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://hookpulse.net/mcp"]
}
}
}{
"mcpServers": {
"hookpulse": {
"url": "https://hookpulse.net/mcp"
}
}
}{
"servers": {
"hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
}{
"context_servers": {
"hookpulse": {
"url": "https://hookpulse.net/mcp"
}
}
}{
"mcpServers": {
"hookpulse": {
"serverUrl": "https://hookpulse.net/mcp"
}
}
}{
"mcpServers": {
"hookpulse": {
"url": "https://hookpulse.net/mcp"
}
}
}name: Hookpulse
version: 0.0.1
schema: v1
mcpServers:
- name: Hookpulse
type: streamable-http
url: https://hookpulse.net/mcp{
"mcpServers": {
"hookpulse": {
"httpUrl": "https://hookpulse.net/mcp"
}
}
}{
"mcpServers": {
"hookpulse": {
"type": "http",
"url": "https://hookpulse.net/mcp"
}
}
}{
"mcpServers": {
"hookpulse": {
"url": "https://hookpulse.net/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fhookpulse.net%2Fmcp&type=streamable_http&id=hookpulse&name=Hookpulse
It answered our last check on 24 October 2026 in 635 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by hookpulse.net and served from hookpulse.net, the vendor's own domain: https://hookpulse.net/mcp.
22, as returned by the server's own tools/list on 22 September 2026: api_index, billing, contact, create_endpoint, create_guest, delete_endpoint, get_endpoint, health, and 14 more.
It answered our last check on 24 October 2026 in 635 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://hookpulse.net/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: net.hookpulse. Endpoint host: hookpulse.net. ARD identifier: urn:air:net.hookpulse:mcp:hookpulse.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.