Agents Index

Hookpulse

Online

Know when a job stops or a site goes down after the agent exits. Free monitors; paid extra coverage.

Visit publisherConnectJSON

What it can do: 29 tools

  • list_plans read-onlyThe plans for sale, with price and term, and the account's active plan. Each purchase lasts 30 days, with no automatic renewal. Each purchase lasts 30 days, with no automatic renewal. Without an account or wallet credent
  • buy_planBuy a plan: starter (40 more monitors, up to 50), team (90 more monitors, up to 100), business (490 more monitors, up to 500). Each purchase lasts 30 days, with no automatic renewal. Answers 402 with the price; pay with
  • cancel_planCancel the active plan. Nothing else is charged; a purchase under 7 days and a paid period that has not started are refunded and end now, and the rest of the paid period stays active until keeps_until. Requires accept_da
  • api_index read-onlyFull index of the HookPulse API.
  • health read-onlyRead service liveness before using HookPulse. Returns the health response; does not check a monitor.
  • create_guestCreates a guest token hp_… Keep the token: without it there is no way back to the monitors, unless you have already tied them to an e-mail.
  • list_endpoints read-onlyLists the guest's/session's endpoints.
  • create_endpointCreate a monitor for a routine. Use cron, tz and grace_sec for a schedule, or interval_sec for a fixed check-in interval. Set max_duration_sec to detect an open run that exceeds its time limit. Without an owner token, cr
  • create_siteMonitor a website: HookPulse calls check.url every interval_sec (default 300) and alerts when it goes down and when it is back. Without an owner token, creation returns guest_token; keep it private. Read billing before a
  • check_siteCheck a site monitor now. One call every 10 seconds per destination host. One call every 10 seconds per destination host, for everyone: the button cannot hammer a site. The first state of a new site comes from here, with
  • list_sites read-onlyThe state of every site you monitor (up, down, waiting, paused), with the last check. The same answer is the snapshot of the live subscription (`/api/realtime/`): after it, every check arrives as an event, so a screen ne
  • import_crontabReads 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. The body is the crontab itself, as `text
  • get_endpoint read-onlyStatus of one endpoint (use the endpoint token if you have it). The monitor token only reads: it lets you put the state on a third-party dashboard without handing over the owner's credential. With a schedule it is here t
  • delete_endpointRemoves the owner's endpoint.
  • list_events read-onlyLatest ingest pings.
  • ping_ingest read-onlySimulates the cron: GET on /in/:id. No credential on purpose — the caller is a cron, and the ID is already the secret. It costs nothing and there is no quota per ping.
  • signal_start read-onlySays 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. `start` is not proof of life: it does not move `last_event_at` and doe
  • signal_fail read-onlyRecord a failed run. The next five-minute check sends the alert with reason fail. The monitor's alert_repeat_sec controls repeated alerts; the default is 24 hours. Failing is not proof of life either: the clock keeps run
  • signal_exit_code read-onlyThe shell exit status: 0 behaves like a ping, 1-255 record the code as a failure. `curl -fsS $ORIGIN/in/ID/$?` at the end of a script is the whole integration. `0` behaves exactly like a plain ping; 1 to 255 record the c
  • ingest_key read-onlyReturns (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. One key per owner. Point a whole fleet at `/
  • ingest_key_rotateRotates the ingest key; the previous one stops creating monitors. Existing ones keep working. Monitors already created keep working — rotating only revokes the power to create new ones.
  • ping_slug read-onlyCreate a monitor on its first check-in. The same slug uses the same monitor. Service and billing limits apply. A rejected creation writes no monitor or event. The slug becomes the monitor name and its identity: the same
  • signal_slug read-onlySend start, fail or an exit code by name, with the ingest key; the first signal of a new name creates its monitor. The same signals as `/in/:id/start`, `/in/:id/fail` and `/in/:id/:exit_code`, for a fleet that only knows
  • pricing read-onlyRead current free allowances, options with billing off, prices and the account's 7-day trial. E-mail alerts cost $0.10 once per additional monitor, even with a reused address. Check before creating the second monitor or
  • status_feed_url read-onlyPublic URL (JSON and RSS) with the status of all the owner's endpoints. The feed token only reads status: it does not create, change or delete. Whoever has the link sees the dashboard — treat it as a secret.
  • status_feed_rotateRotates the status feed token; the previous URL stops working.
  • list_templates read-onlyIngest snippets and the JSON HookPulse POSTs on a miss. It exists so nobody guesses the alert format: `miss_json` and `recovery_json` here are the same bodies that arrive at your `alert_url`. Slack and Discord receive on
  • contactWrite to the people behind the product: a question, or a sponsorship/partnership/advertising proposal. Free, no captcha and no payment; one message every 10 s per network (one that arrives sooner waits its turn). One rou
  • get_api_x402_checkChecks a URL once for an agent, paid per call: status, response time, keyword and TLS certificate, with no account and no monitor. One reading with the probe of the site monitors, and the certificate of an https address

Connect it

Claude Code
claude mcp add --transport http hookpulse https://hookpulse.net/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://hookpulse.net/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "hookpulse": {
      "url": "https://hookpulse.net/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "hookpulse": {
      "type": "http",
      "url": "https://hookpulse.net/mcp"
    }
  }
}

Questions

What does Hookpulse do?

Know when a job stops or a site goes down after the agent exits. Free monitors; paid extra coverage. It exposes 29 tools to AI assistants.

What tools does Hookpulse provide?

29 tools, including list_plans, buy_plan, cancel_plan, api_index, health, create_guest, list_endpoints, create_endpoint, create_site, check_site, list_sites, import_crontab….

How do I connect Hookpulse to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://hookpulse.net/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Hookpulse require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Hookpulse online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Hookpulse?

hookpulse.net. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Cloud & DevOps