HookPulse
Voting openCron and webhook heartbeat monitoring with alerts
The top 3 with at least 3 votes when the week closes win a dated place badge and a permanent followed link. First place also gets the rail ad for the following week, free.
From the maker
Cron job and webhook heartbeat monitoring (dead-man's switch) with alerts when a check-in stops. Built by Wendel Pereira (WRP).
How to connect
Streamable HTTP endpoint:
https://hookpulse.net/mcp
What we found when we connected
Verified 2026-10-26 | 24 tools | responded in 1022ms
- Protocol revision
- 2025-06-18
- Server identified itself as
- HookPulse c68ad1e8
- Tools exposed
- 24
- Tool descriptions
- present
- tools/list round trip
- 1022ms
- Tested
- 2026-10-26 12:47 UTC
The 24 tools it exposed
Every name below came back from this server's own tools/list response on the date above. So did each description, parameter list and label like "read-only": they are the server describing itself. We did not call any of them.
-
api_index read-only
Full index of the HookPulse API.
-
health read-only
Liveness.
-
create_guest
Creates 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-only
Lists the guest's/session's endpoints.
Parameters: guest_token (required)
-
create_endpoint reaches outside services
Create 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… more Create 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. With `check` the monitor is a site: HookPulse calls `check.url` every `interval_sec` (default 300) and alerts when it goes down — two failed checks in a row, one minute apart, from a server whose own connection is proven — and when it answers again. `{"check":{"url":"https://example.com/"}}` is enough; the name defaults to the host. A site has no `cron`, no `max_duration_sec` and no ingest URL. This res [shortened] less
Parameters: guest_token (required), name (required), interval_sec, cron, paused_until, tz, grace_sec, max_duration_sec, alert_repeat_sec, tags, alert_to, alert_url
Show the other 19 tools Hide the other 19 tools
-
create_site reaches outside services
Monitor a website: HookPulse calls check.url every interval_sec (default 300) and alerts when it goes down and when it is back. With `check` the monitor is a… more Monitor a website: HookPulse calls check.url every interval_sec (default 300) and alerts when it goes down and when it is back. With `check` the monitor is a site: HookPulse calls `check.url` every `interval_sec` (default 300) and alerts when it goes down — two failed checks in a row, one minute apart, from a server whose own connection is proven — and when it answers again. `{"check":{"url":"https://example.com/"}}` is enough; the name defaults to the host. A site has no `cron`, no `max_duration_sec` and no ingest URL. This response is the only one that shows the monitor's `token` and the `te [shortened] less
Parameters: guest_token (required), check (required), name, interval_sec, paused_until, tags, alert_to, alert_url
-
check_site reaches outside services
Check 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… more Check 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, without an alert — you are looking at it. After that, the state and the alerts come from the check that runs every minute. less
Parameters: id (required), guest_token (required)
-
list_sites read-only
The state of every site you monitor (up, down, waiting, paused), with the last check.
Parameters: guest_token (required)
-
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… more 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. The body is the crontab itself, as `text/plain`. Without `?apply=1` **nothing is written**: you get the proposal — what would become a monitor, what was ignored and why, and what still fits in the free tier. With `apply=1` it is all or nothing, under the same rules as `POST /api/endpoints`. Comments, variables and `@reboot` are ignored (there is no way to know when to expect a reboot); `@daily` and friends become the [shortened] less
Parameters: guest_token (required), crontab (required), apply
-
get_endpoint read-only
Status 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… more Status 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 that `next_expected_at` says when the next run is due. less
Parameters: id (required), token, guest_token
-
delete_endpoint destructive idempotent
Removes the owner's endpoint.
Parameters: guest_token (required), id (required)
-
list_events read-only
Latest ingest pings.
Parameters: id (required), token, guest_token
-
ping_ingest read-only
Simulates the cron: GET on /in/:id. No credential on purpose — the caller is a cron, and the ID is already the secret.
Parameters: id (required)
-
signal_start read-only
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. `start`… more 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. `start` is not proof of life: it does not move `last_event_at` and does not clear the miss counter, so a routine that starts and hangs still becomes a miss at the right time. The next success closes the run and records `last_duration_ms` — pass `?rid=` on both ends when runs can overlap, or the duration is measured against the wrong start. With `max_duration_sec` set on the monitor, a run left open past that ceiling alerts with `reason: "too_long [shortened] less
Parameters: id (required)
-
signal_fail read-only
Record 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… more Record 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 running. The ingest never sends e-mail and never calls out — it records `alert_pending` and the cron turns it into an alert with `reason: "fail"` within 5 minutes, under the same one-per-24h cap. Works by GET or POST. less
Parameters: id (required)
-
signal_exit_code read-only
The 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… more The 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 code and leave the failure for the cron. less
Parameters: id (required), exit_code (required)
-
ingest_key read-only
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… more 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. One key per owner. The key survives signing in: the crontab you deployed keeps working. less
Parameters: guest_token
-
ingest_key_rotate destructive idempotent
Rotates 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.
Parameters: guest_token
-
ping_slug read-only
Create a monitor on its first check-in. The same slug uses the same monitor. A rejected creation writes no monitor or event. The slug becomes the monitor name… more Create a monitor on its first check-in. The same slug uses the same monitor. A rejected creation writes no monitor or event. The slug becomes the monitor name and its identity: the same slug always means the same monitor, so a retry never creates a second one. Normalised to lowercase, `[a-z0-9-]`, 40 chars. Works by GET or POST. less
Parameters: ingestKey (required), slug (required)
-
signal_slug read-only
Send 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`… more Send 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 the ingest key: the job sends its name, not the monitor id. The first signal of a new name creates the monitor, with the same rules and the same `cron`, `tz` and `grace_sec` as the plain ping by name. less
Parameters: ingestKey (required), slug (required), signal (required)
-
status_feed_url read-only
Public 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… more Public 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. less
Parameters: guest_token
-
status_feed_rotate destructive idempotent
Rotates the status feed token; the previous URL stops working.
Parameters: guest_token
-
list_templates read-only
Ingest 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… more Ingest 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 only the field they read. less
-
contact
Write to the people behind the product: a question, or a sponsorship/partnership/advertising proposal. One route for a question and for a sponsorship… more Write to the people behind the product: a question, or a sponsorship/partnership/advertising proposal. One route for a question and for a sponsorship, partnership or ad proposal (`tipo`, with the placements of `GET /api/partners`). One message every 10 seconds per network: one that arrives sooner waits its turn and then goes out — no error. The message reaches the team by e-mail, with `email` as the reply address. For voice, send multipart/form-data: `dados` is this JSON (up to 32 KiB), and `audio` is one WebM, Ogg or M4A audio file (up to 2 MB). Audio can replace message. The browser records [shortened] less
Parameters: name (required), email (required), message (required), whatsapp, prefer_whatsapp, tipo, empresa, site, orcamento, espaco, duracao, pagamento, projeto, prazo, formato, pais, fuso, horarios
Anything above describes one moment on the date shown. We do not re-test on a schedule, so nothing here says what this server is doing now. We have not audited its code, its data handling or its permissions, and this is not a safety rating.
Comments
What readers said about this product. Comments are people's own opinions and are not part of anything we checked.
Sign in to comment. Same account that votes.
Comments are written by readers, not by us, and we do not endorse them. Nothing here is held back or approved first: a comment goes up when it is posted, and you can edit or delete your own at any time. Report anything illegal or abusive with the link on each comment, or by email from our contact page if you do not have an account.