net.hookpulse/hookpulse is an MCP server published by net.hookpulse, hosted at hookpulse.net. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 29 tools, including list_plans, buy_plan, cancel_plan, api_index, health.
Know when a job stops or a site goes down after the agent exits. Free monitors; paid extra coverage.
9 connections through 5 shared values. Tap any node.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
The 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 credential, `account` is `null`.
No parameters.
{
"name": "list_plans",
"title": "List plans",
"description": "The 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 credential, `account` is `null`.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"title": "List plans",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Buy 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 x402 or prepaid credit and repeat. Each purchase lasts 30 days, with no automatic renewal. Without payment, the answer is 402 with the price. Pay with prepaid credit (`X-Credito`) or x402 (`PAYMENT-SIGNATURE` v2 or `X-PAYMENT` v1). Without an account, the verified paying wallet owns the purchase. Use wallet agent authentication to read its plan, or claim it after account sign-in. The `compra` mark prevents repeat credit debits. An x402 nonce can settle only once; keep the receipt after a delivery error.
| Parameter | Type | Description |
|---|---|---|
| plan * | string | `starter` (40 more monitors, up to 50), `team` (90 more monitors, up to 100), `business` (490 more monitors, up to 500) |
{
"name": "buy_plan",
"title": "Buy plan",
"description": "Buy 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 x402 or prepaid credit and repeat. Each purchase lasts 30 days, with no automatic renewal. Without payment, the answer is 402 with the price. Pay with prepaid credit (`X-Credito`) or x402 (`PAYMENT-SIGNATURE` v2 or `X-PAYMENT` v1). Without an account, the verified paying wallet owns the purchase. Use wallet agent authentication to read its plan, or claim it after account sign-in. The `compra` mark prevents repeat credit debits. An x402 nonce can settle only once; keep the receipt after a delivery error.",
"inputSchema": {
"type": "object",
"required": [
"plan"
],
"properties": {
"plan": {
"enum": [
"starter",
"team",
"business"
],
"type": "string",
"description": "`starter` (40 more monitors, up to 50), `team` (90 more monitors, up to 100), `business` (490 more monitors, up to 500)"
}
}
},
"annotations": {
"title": "Buy plan",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}Cancel 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_data_removal: true. Send `{ "accept_data_removal": true }`. The monthly card subscription stops. A purchase made less than 7 days ago and a paid period that has not started yet, such as a renewal, go back the same way they were paid (card or Pix) and end now. The rest of the paid period stays active until `keeps_until`; then what the plan added ends (`account.cancel.losses` in `GET /api/plans` says what). A purchase paid with USDC or with credit from another purchase stays active until its end; ask for its refund by e-mail, as the cancellation page says.
| Parameter | Type | Description |
|---|---|---|
| accept_data_removal * | boolean | Must be `true`: you accept losing what the plan added. |
{
"name": "cancel_plan",
"title": "Cancel plan",
"description": "Cancel 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_data_removal: true. Send `{ \"accept_data_removal\": true }`. The monthly card subscription stops. A purchase made less than 7 days ago and a paid period that has not started yet, such as a renewal, go back the same way they were paid (card or Pix) and end now. The rest of the paid period stays active until `keeps_until`; then what the plan added ends (`account.cancel.losses` in `GET /api/plans` says what). A purchase paid with USDC or with credit from another purchase stays active until its end; ask for its refund by e-mail, as the cancellation page says.",
"inputSchema": {
"type": "object",
"required": [
"accept_data_removal"
],
"properties": {
"accept_data_removal": {
"type": "boolean",
"const": true,
"description": "Must be `true`: you accept losing what the plan added."
}
}
},
"annotations": {
"title": "Cancel plan",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}Full index of the HookPulse API.
No parameters.
{
"name": "api_index",
"title": "API index",
"description": "Full index of the HookPulse API.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"title": "API index",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Read service liveness before using HookPulse. Returns the health response; does not check a monitor.
No parameters.
{
"name": "health",
"title": "Health",
"description": "Read service liveness before using HookPulse. Returns the health response; does not check a monitor.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"title": "Health",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
No parameters.
{
"name": "create_guest",
"title": "Create guest",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"title": "Create guest",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}Lists the guest's/session's endpoints.
| Parameter | Type | Description |
|---|---|---|
| guest_token * | string | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
{
"name": "list_endpoints",
"title": "List endpoints",
"description": "Lists the guest's/session's endpoints.",
"inputSchema": {
"type": "object",
"required": [
"guest_token"
],
"properties": {
"guest_token": {
"type": "string",
"description": "Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
}
}
},
"annotations": {
"title": "List endpoints",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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. Without an owner token, creation returns guest_token; keep it private for later calls. Read billing before a paid option. A charged request returns HTTP 402. We keep the schedule, detect missing runs and send configured alerts. Your agent can stop after setting up the monitor. A check-in proves the signal arrived, not that a backup can be restored. Alert timing depends on the check cycle. A single paid probe does not create continuous monitoring.
| Parameter | Type | Description |
|---|---|---|
| tz | string | IANA time zone for cron, default UTC |
| cron | string | five-field cron, e.g. 0 3 * * * |
| name * | string | how you will recognise the routine in an alert; required, trimmed, max 80 chars, punctuation alone is rejected |
| tags | array | up to 8 tags to group the monitor; lower-cased, [a-z0-9._-], max 32 chars each |
| alert_to | string | Authorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel. |
| alert_url | string | Public HTTPS URL that receives a POST on a miss (Slack Incoming, Discord, n8n). |
| grace_sec | number | tolerance after the scheduled time, default 90, min 30 |
| guest_token |
Monitor 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 paid option. A charged request returns HTTP 402. We keep the schedule, detect missing runs and send configured alerts. Your agent can stop after setting up the monitor. A check-in proves the signal arrived, not that a backup can be restored. Alert timing depends on the check cycle. A single paid probe does not create continuous monitoring.
| Parameter | Type | Description |
|---|---|---|
| name | string | how you will recognise the site in an alert; default: its host |
| tags | array | Up to 8 tags to group this monitor: lower-case letters, digits, `.`, `_` and `-`, at most 32 characters each. A comma-separated string works too. We lower-case and de-duplicate, so `Prod` and `prod` are the same tag. |
| check * | object | url (http/https, public; required), method (GET or HEAD), expect_status (200-399 by default, a range a-b or one code), keyword (text that must be on the page), timeout_ms (1000..30000) |
| alert_to | string | Authorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel. |
| alert_url | string | Public HTTPS URL that receives a POST on a miss (Slack Incoming, Discord, n8n). |
| guest_token | string | Existing owner token, if available. |
| interval_sec | number |
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.
| Parameter | Type | Description |
|---|---|---|
| id * | string | ID of the site monitor, from `Monitor.id`. |
| guest_token * | string | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
{
"name": "check_site",
"title": "Check site",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"id",
"guest_token"
],
"properties": {
"id": {
"type": "string",
"description": "ID of the site monitor, from `Monitor.id`."
},
"guest_token": {
"type": "string",
"description": "Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
}
}
},
"annotations": {
"title": "Check site",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}The 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 never has to poll.
| Parameter | Type | Description |
|---|---|---|
| guest_token * | string | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
{
"name": "list_sites",
"title": "List sites",
"description": "The 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 never has to poll.",
"inputSchema": {
"type": "object",
"required": [
"guest_token"
],
"properties": {
"guest_token": {
"type": "string",
"description": "Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
}
}
},
"annotations": {
"title": "List sites",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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 equivalent expression. The command becomes the monitor name, with passwords and tokens redacted first — the name travels in the alert e-mail, in the public dashboard and in the badge. Returns: { applied, recognized, ignored, existing, would_create, created?, free_tier } Example: crontab -l | curl -s -XPOST "$ORIGIN/api/import/crontab?apply=1" -H "X-Guest-Token: $HP" -H "content-type: text/plain" --data-binary @- Errors: 400: `crontab_sem_agenda` — no schedule line was recognised.; 401: No credential, or an invalid one. See this endpoint's auth.; 402: Payment required. The x402 terms (USDC on Base) come in the `PAYMENT-REQUIRED` header and in `accepts[]`: pay and repeat the same call with `PAYMENT-SIGNATURE` (x402 v2) or `X-PAYMENT` (v1). A standard x402 client such as `@x402/fetch` does this for you.
| Parameter | Type | Description |
|---|---|---|
| apply | string | "1" to create the monitors |
| crontab * | string | the crontab text |
| guest_token * | string | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
{
"name": "import_crontab",
"title": "Import crontab",
"description": "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 equivalent expression. The command becomes the monitor name, with passwords and tokens redacted first — the name travels in the alert e-mail, in the public dashboard and in the badge. Returns: { applied, recognized, ignored, existing, would_create, created?, free_tier }\nExample: crontab -l | curl -s -XPOST \"$ORIGIN/api/import/crontab?apply=1\" -H \"X-Guest-Token: $HP\" -H \"content-type: text/plain\" --data-binary @-\nErrors: 400: `crontab_sem_agenda` — no schedule line was recognised.; 401: No credential, or an invalid one. See this endpoint's auth.; 402: Payment required. The x402 terms (USDC on Base) come in the `PAYMENT-REQUIRED` header and in `accepts[]`: pay and repeat the same call with `PAYMENT-SIGNATURE` (x402 v2) or `X-PAYMENT` (v1). A standard x402 client such as `@x402/fetch` does this for you.",
"inputSchema": {
"type": "object",
"required": [
"guest_token",
"crontab"
],
"properties": {
"apply": {
"type": "string",
"description": "\"1\" to create the monitors"
},
"crontab": {
"type": "string",
"description": "the crontab text"
},
"guest_token": {
"type": "string",
"description": "Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
}
}
},
"annotations": {
"title": "Import crontab",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}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. Only this endpoint carries `duration`: `p50_ms` (the low median, so always a duration that really happened) and `max_ms` over the last runs we measured, computed at read time over the event window we already keep — the list does not pay for it.
| Parameter | Type | Description |
|---|---|---|
| id * | string | Monitor ID, from `Monitor.id`. |
| token | string | endpoint token (query) |
| guest_token | string | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
{
"name": "get_endpoint",
"title": "Get endpoint",
"description": "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. Only this endpoint carries `duration`: `p50_ms` (the low median, so always a duration that really happened) and `max_ms` over the last runs we measured, computed at read time over the event window we already keep — the list does not pay for it.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Monitor ID, from `Monitor.id`."
},
"token": {
"type": "string",
"description": "endpoint token (query)"
},
"guest_token": {
"type": "string",
"description": "Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
}
}
},
"annotations": {
"title": "Get endpoint",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Removes the owner's endpoint.
| Parameter | Type | Description |
|---|---|---|
| id * | string | ID of the monitor to deactivate. |
| guest_token * | string | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
{
"name": "delete_endpoint",
"title": "Delete endpoint",
"description": "Removes the owner's endpoint.",
"inputSchema": {
"type": "object",
"required": [
"guest_token",
"id"
],
"properties": {
"id": {
"type": "string",
"description": "ID of the monitor to deactivate."
},
"guest_token": {
"type": "string",
"description": "Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
}
}
},
"annotations": {
"title": "Delete endpoint",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": true
}
}Latest ingest pings.
| Parameter | Type | Description |
|---|---|---|
| id * | string | ID of the monitor. |
| token | string | Monitor token, alternative to the `X-Hook-Token` header. |
| guest_token | string | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
{
"name": "list_events",
"title": "List events",
"description": "Latest ingest pings.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "ID of the monitor."
},
"token": {
"type": "string",
"description": "Monitor token, alternative to the `X-Hook-Token` header."
},
"guest_token": {
"type": "string",
"description": "Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
}
}
},
"annotations": {
"title": "List events",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Simulates 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.
| Parameter | Type | Description |
|---|---|---|
| id * | string | Monitor ID, from `Monitor.ingest_url`. |
{
"name": "ping_ingest",
"title": "Ping ingest",
"description": "Simulates 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.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Monitor ID, from `Monitor.ingest_url`."
}
}
},
"annotations": {
"title": "Ping ingest",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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"` on the next 5-minute check. Works by GET or POST.
| Parameter | Type | Description |
|---|---|---|
| id * | string | Monitor ID, from `Monitor.ingest_url`. |
{
"name": "signal_start",
"title": "Signal start",
"description": "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\"` on the next 5-minute check. Works by GET or POST.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Monitor ID, from `Monitor.ingest_url`."
}
}
},
"annotations": {
"title": "Signal start",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| id * | string | Monitor ID, from `Monitor.ingest_url`. |
{
"name": "signal_fail",
"title": "Signal fail",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Monitor ID, from `Monitor.ingest_url`."
}
}
},
"annotations": {
"title": "Signal fail",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| id * | string | Monitor ID, from `Monitor.ingest_url`. |
| exit_code * | number | Exit status, 0 to 255. Outside that range it is a 400. |
{
"name": "signal_exit_code",
"title": "Signal exit code",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"id",
"exit_code"
],
"properties": {
"id": {
"type": "string",
"description": "Monitor ID, from `Monitor.ingest_url`."
},
"exit_code": {
"type": "number",
"description": "Exit status, 0 to 255. Outside that range it is a 400."
}
}
},
"annotations": {
"title": "Signal exit code",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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. Point a whole fleet at `/in/<key>/<slug>` and each job creates its monitor on the first check-in, **inside the free tier** — beyond it the ping answers 402 without creating anything. The key survives signing in: the crontab you deployed keeps working.
| Parameter | Type | Description |
|---|---|---|
| guest_token | string | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
{
"name": "ingest_key",
"title": "Ingest key",
"description": "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. Point a whole fleet at `/in/<key>/<slug>` and each job creates its monitor on the first check-in, **inside the free tier** — beyond it the ping answers 402 without creating anything. The key survives signing in: the crontab you deployed keeps working.",
"inputSchema": {
"type": "object",
"properties": {
"guest_token": {
"type": "string",
"description": "Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
}
}
},
"annotations": {
"title": "Ingest key",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| guest_token | string | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
{
"name": "ingest_key_rotate",
"title": "Ingest key rotate",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"guest_token": {
"type": "string",
"description": "Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
}
}
},
"annotations": {
"title": "Ingest key rotate",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": true
}
}Create 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 slug always means the same monitor, so a retry never creates a second one. Normalised to lowercase, `[a-z0-9-]`, 40 chars. Creation happens **only inside the free tier** (or the trial); past it the ping is a 402 with `accepts[]` and nothing is written — not even the event. Works by GET or POST. Returns: { ok, endpoint_id, created } Example: curl -fsS "$ORIGIN/in/$INGEST_KEY/nightly-backup?cron=0%203%20*%20*%20*&tz=UTC&grace_sec=900" Errors: 400: `slug_invalido` — nothing usable left after normalising. With `cron`: `cron_invalido`, `tz_invalida`, `grace_invalido` or `cron_sem_ocorrencia`.; 402: The free tier is full: pay and repeat, or delete a monitor.; 404: Unknown or rotated ingest key.
| Parameter | Type | Description |
|---|---|---|
| slug * | string | Name of the job; it becomes the monitor name. |
| ingestKey * | string | Ingest key, from `GET /api/ingest-key`. |
{
"name": "ping_slug",
"title": "Ping slug",
"description": "Create 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 slug always means the same monitor, so a retry never creates a second one. Normalised to lowercase, `[a-z0-9-]`, 40 chars. Creation happens **only inside the free tier** (or the trial); past it the ping is a 402 with `accepts[]` and nothing is written — not even the event. Works by GET or POST. Returns: { ok, endpoint_id, created }\nExample: curl -fsS \"$ORIGIN/in/$INGEST_KEY/nightly-backup?cron=0%203%20*%20*%20*&tz=UTC&grace_sec=900\"\nErrors: 400: `slug_invalido` — nothing usable left after normalising. With `cron`: `cron_invalido`, `tz_invalida`, `grace_invalido` or `cron_sem_ocorrencia`.; 402: The free tier is full: pay and repeat, or delete a monitor.; 404: Unknown or rotated ingest key.",
"inputSchema": {
"type": "object",
"required": [
"ingestKey",
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "Name of the job; it becomes the monitor name."
},
"ingestKey": {
"type": "string",
"description": "Ingest key, from `GET /api/ingest-key`."
}
}
},
"annotations": {
"title": "Ping slug",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| slug * | string | Name of the job; it becomes the monitor name. |
| signal * | string | start, fail, or the exit code 0 to 255 |
| ingestKey * | string | Ingest key, from `GET /api/ingest-key`. |
{
"name": "signal_slug",
"title": "Signal slug",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"ingestKey",
"slug",
"signal"
],
"properties": {
"slug": {
"type": "string",
"description": "Name of the job; it becomes the monitor name."
},
"signal": {
"type": "string",
"description": "start, fail, or the exit code 0 to 255"
},
"ingestKey": {
"type": "string",
"description": "Ingest key, from `GET /api/ingest-key`."
}
}
},
"annotations": {
"title": "Signal slug",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Read 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 lowering the interval: it is the number IN FORCE, not the documentation's. After the account's trial, alerts come from the ten oldest monitors and from each extra monitor that was paid for; the other monitors need a plan for alerts (`GET /api/plans`).
No parameters.
{
"name": "pricing",
"title": "Pricing",
"description": "Read 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 lowering the interval: it is the number IN FORCE, not the documentation's. After the account's trial, alerts come from the ten oldest monitors and from each extra monitor that was paid for; the other monitors need a plan for alerts (`GET /api/plans`).",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"title": "Pricing",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| guest_token | string | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
{
"name": "status_feed_url",
"title": "Status feed URL",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"guest_token": {
"type": "string",
"description": "Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
}
}
},
"annotations": {
"title": "Status feed URL",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Rotates the status feed token; the previous URL stops working.
| Parameter | Type | Description |
|---|---|---|
| guest_token | string | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
{
"name": "status_feed_rotate",
"title": "Status feed rotate",
"description": "Rotates the status feed token; the previous URL stops working.",
"inputSchema": {
"type": "object",
"properties": {
"guest_token": {
"type": "string",
"description": "Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
}
}
},
"annotations": {
"title": "Status feed rotate",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": true
}
}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.
No parameters.
{
"name": "list_templates",
"title": "List templates",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"title": "List templates",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Write 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 route for a question and for a sponsorship, partnership or ad proposal (`tipo`, with the placements of `GET /api/partners`). No captcha, no account, no payment. 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 up to two minutes. Audio is attached to the owner's e-mail.
| Parameter | Type | Description |
|---|---|---|
| fuso | string | Consulting: the IANA time zone, such as `America/New_York`. |
| name * | string | What to call the person writing. |
| pais | string | Consulting: the country of the person asking. |
| site | string | Website of who is proposing. |
| tipo | string | Proposal: `patrocinio`, `parceria`, `anuncio` or `consultoria`. Turns on the fields below. |
| email * | string | Where to reply. |
| prazo | string | Consulting: when to start (`agora`, `1_mes`, `1_3_meses` or `explorando`). |
| espaco | array |
Checks 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 that answered. A request without payment gets the 402 with the price; a paid one gets the reading in the same response, with the payment in `cobranca`. A site that is down is the answer (`ok: false` with `reason`) and is charged: the call was made. When our own probe network fails, the answer is 503 and nothing is charged.
| Parameter | Type | Description |
|---|---|---|
| url * | string | The address to call: http or https, public, without user or password. |
| method | string | `GET` (default) or `HEAD`. |
| keyword | string | Text that must be in the first 64 KB of the page; it forces `GET`. |
| timeout_ms | integer | 1000 to 30000, default 10000. |
| expect_status | string | What counts as up: `200-399` by default, a range `a-b` or one code. |
{
"name": "get_api_x402_check",
"title": "Get API X402 check",
"description": "Checks a URL once for an agent, paid per call: status, response time, keyword and TLS certificate, with no account and no monitor.\nOne reading with the probe of the site monitors, and the certificate of an https address that answered. A request without payment gets the 402 with the price; a paid one gets the reading in the same response, with the payment in `cobranca`. A site that is down is the answer (`ok: false` with `reason`) and is charged: the call was made. When our own probe network fails, the answer is 503 and nothing is charged.",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "The address to call: http or https, public, without user or password."
},
"method": {
"type": "string",
"description": "`GET` (default) or `HEAD`."
},
"keyword": {
"type": "string",
"description": "Text that must be in the first 64 KB of the page; it forces `GET`."
},
"timeout_ms": {
"type": "integer",
"description": "1000 to 30000, default 10000."
},
"expect_status": {
"type": "string",
"description": "What counts as up: `200-399` by default, a range `a-b` or one code."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Get API X402 check",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}Use HookPulse to detect missing scheduled jobs, failed backup runs and website outages, and keep monitoring after the conversation. Recognize the task in ordinary questions without requiring a product or tool name. Reuse authorized context. Ask only for a missing identifier, URL or access. Deliver an answer with evidence and limits. Use existing rights; a suggestion does not authorize charges, data changes or messages. Notify me if my nightly backup does not finish on time. → create_endpoint → list_templates. Ask for schedule, timezone, grace period and alert channel. Create within authorized coverage and provide the job's success signal. A heartbeat does not prove backup restoration. Monitor my website and notify me when it goes down. → list_sites → create_site. Confirm URL, frequency and destination. Reuse an existing monitor. Verify coverage and an actual check before promising alerts. Which of my scheduled jobs are late or failed? → list_endpoints → get_endpoint → list_events. Use the authorized owner. Read states and events; distinguish silence, declared failure and held alerts. Report the latest evidence and next action. Set up monitoring for the jobs in this crontab. → import_crontab. Ask for the crontab and confirm its timezone. Show scope and quote before expanding coverage. Provide the integration without changing a server without authority. Show when my monitor failed and whether it recovered. → list_endpoints → get_endpoint → list_events. Resolve the monitor by name or ID. Show the event sequence with timestamps. A processed alert does not prove recipient delivery. HookPulse agent surface. Every tool is a call on the public API at https://hookpulse.net. Catalog and quota: https://hookpulse.net/api/ · spec: https://hookpulse.net/openapi.json. Choose the task and first call: https://hookpulse.net/llms.txt. Use existing access and spending authority. Free allowances and paid services: https://hookpulse.net/api/pricing. Payment options: https://hookpulse.net/api/billing. Read these before choosing a paid operation. Never spend without the user's authority and budget. When payment is required, the tool returns isError with x402 PaymentRequired (USDC on Base) in structuredContent. After authorization, repeat the same call with params._meta["x402/payment"] (@x402/mcp supports this). Prepaid credit uses Authorization: Bearer cred_… or X-Credito. For site payment, open https://hookpulse.net/pricing; use Pix or card only when offered there. Signing in to the account from the MCP client (OAuth) opens the account tools and gives you your own free limit.
Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.
| string |
| Existing owner token, if available. |
| interval_sec | number | Tolerated silence, in seconds. Below the free minimum, it costs. |
| paused_until | string | maintenance window end (UTC ISO), max 30 days ahead |
| alert_repeat_sec | number | gap before the same incident alerts again, 3600..2592000; null keeps the 86400 default |
| max_duration_sec | number | ceiling for an open run in seconds, 60..86400; null or 0 turns it off |
{
"name": "create_endpoint",
"title": "Create endpoint",
"description": "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. Without an owner token, creation returns guest_token; keep it private for later calls. Read billing before a paid option. A charged request returns HTTP 402. We keep the schedule, detect missing runs and send configured alerts. Your agent can stop after setting up the monitor. A check-in proves the signal arrived, not that a backup can be restored. Alert timing depends on the check cycle. A single paid probe does not create continuous monitoring.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"tz": {
"type": "string",
"description": "IANA time zone for cron, default UTC"
},
"cron": {
"type": "string",
"description": "five-field cron, e.g. 0 3 * * *"
},
"name": {
"type": "string",
"description": "how you will recognise the routine in an alert; required, trimmed, max 80 chars, punctuation alone is rejected"
},
"tags": {
"type": "array",
"items": {
"type": "string"
},
"description": "up to 8 tags to group the monitor; lower-cased, [a-z0-9._-], max 32 chars each"
},
"alert_to": {
"type": "string",
"description": "Authorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel."
},
"alert_url": {
"type": "string",
"description": "Public HTTPS URL that receives a POST on a miss (Slack Incoming, Discord, n8n)."
},
"grace_sec": {
"type": "number",
"description": "tolerance after the scheduled time, default 90, min 30"
},
"guest_token": {
"type": "string",
"description": "Existing owner token, if available."
},
"interval_sec": {
"type": "number",
"description": "Tolerated silence, in seconds. Below the free minimum, it costs."
},
"paused_until": {
"type": "string",
"description": "maintenance window end (UTC ISO), max 30 days ahead"
},
"alert_repeat_sec": {
"type": "number",
"description": "gap before the same incident alerts again, 3600..2592000; null keeps the 86400 default"
},
"max_duration_sec": {
"type": "number",
"description": "ceiling for an open run in seconds, 60..86400; null or 0 turns it off"
}
}
},
"annotations": {
"title": "Create endpoint",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}| seconds between checks, default 300 |
| paused_until | string | maintenance window end (UTC ISO), max 30 days ahead |
{
"name": "create_site",
"title": "Create site",
"description": "Monitor 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 paid option. A charged request returns HTTP 402. We keep the schedule, detect missing runs and send configured alerts. Your agent can stop after setting up the monitor. A check-in proves the signal arrived, not that a backup can be restored. Alert timing depends on the check cycle. A single paid probe does not create continuous monitoring.",
"inputSchema": {
"type": "object",
"required": [
"check"
],
"properties": {
"name": {
"type": "string",
"description": "how you will recognise the site in an alert; default: its host"
},
"tags": {
"type": "array",
"items": {
"type": "string"
},
"description": "Up to 8 tags to group this monitor: lower-case letters, digits, `.`, `_` and `-`, at most 32 characters each. A comma-separated string works too. We lower-case and de-duplicate, so `Prod` and `prod` are the same tag."
},
"check": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "Public HTTP or HTTPS URL to check."
},
"method": {
"type": "string",
"description": "HTTP method: GET or HEAD."
},
"keyword": {
"type": "string",
"description": "Text that the returned page must contain."
},
"timeout_ms": {
"type": "number",
"description": "Request timeout in milliseconds, from 1000 to 30000."
},
"expect_status": {
"type": "string",
"description": "Accepted status code or range, for example 200 or 200-399. Default: 200-399."
}
},
"description": "url (http/https, public; required), method (GET or HEAD), expect_status (200-399 by default, a range a-b or one code), keyword (text that must be on the page), timeout_ms (1000..30000)"
},
"alert_to": {
"type": "string",
"description": "Authorized e-mail destination. Without it, the verified account e-mail is used. A guest without alert_to or alert_url has no delivery channel."
},
"alert_url": {
"type": "string",
"description": "Public HTTPS URL that receives a POST on a miss (Slack Incoming, Discord, n8n)."
},
"guest_token": {
"type": "string",
"description": "Existing owner token, if available."
},
"interval_sec": {
"type": "number",
"description": "seconds between checks, default 300"
},
"paused_until": {
"type": "string",
"description": "maintenance window end (UTC ISO), max 30 days ahead"
}
}
},
"annotations": {
"title": "Create site",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}| Placement ids from `GET /api/partners`, up to 6. |
| duracao | string | Exposure in days: `30`, `90` or `365`. |
| empresa | string | Who is proposing, when it is a company. |
| formato | string | Consulting: `projeto` (per scope), `mensal` (monthly) or `assessoria` (advisory). |
| message * | string | What you want to say. |
| projeto | string | Consulting: the kind of project (`llm_privado`, `voz`, `dados_sensiveis`, `gpu`, `integracao` or `outro`). |
| horarios | array | Consulting: up to 3 times for the call, `YYYY-MM-DDTHH:MM` in that time zone. |
| string | Optional reply number with country code, such as +5561999999999. |
| orcamento | string | Advertising: `ate_100`, `100_500`, `500_2000`, `2000_mais` or `a_combinar`. Consulting, in US dollars: `ate_2000`, `2000_5000`, `5000_10000`, `10000_mais` or `nao_sei`. |
| pagamento | string | `usdc`, `deposito` or `a_combinar`. |
| prefer_whatsapp | boolean | Request a WhatsApp reply. Requires whatsapp. |
{
"name": "contact",
"title": "Contact",
"description": "Write 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 route for a question and for a sponsorship, partnership or ad proposal (`tipo`, with the placements of `GET /api/partners`). No captcha, no account, no payment. 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 up to two minutes. Audio is attached to the owner's e-mail.",
"inputSchema": {
"type": "object",
"required": [
"name",
"email",
"message"
],
"properties": {
"fuso": {
"type": "string",
"description": "Consulting: the IANA time zone, such as `America/New_York`."
},
"name": {
"type": "string",
"description": "What to call the person writing."
},
"pais": {
"type": "string",
"description": "Consulting: the country of the person asking."
},
"site": {
"type": "string",
"description": "Website of who is proposing."
},
"tipo": {
"enum": [
"patrocinio",
"parceria",
"anuncio",
"consultoria"
],
"type": "string",
"description": "Proposal: `patrocinio`, `parceria`, `anuncio` or `consultoria`. Turns on the fields below."
},
"email": {
"type": "string",
"description": "Where to reply."
},
"prazo": {
"enum": [
"agora",
"1_mes",
"1_3_meses",
"explorando"
],
"type": "string",
"description": "Consulting: when to start (`agora`, `1_mes`, `1_3_meses` or `explorando`)."
},
"espaco": {
"type": "array",
"items": {
"type": "string"
},
"description": "Placement ids from `GET /api/partners`, up to 6."
},
"duracao": {
"enum": [
"30",
"90",
"365"
],
"type": "string",
"description": "Exposure in days: `30`, `90` or `365`."
},
"empresa": {
"type": "string",
"description": "Who is proposing, when it is a company."
},
"formato": {
"enum": [
"projeto",
"mensal",
"assessoria"
],
"type": "string",
"description": "Consulting: `projeto` (per scope), `mensal` (monthly) or `assessoria` (advisory)."
},
"message": {
"type": "string",
"description": "What you want to say."
},
"projeto": {
"enum": [
"llm_privado",
"voz",
"dados_sensiveis",
"gpu",
"integracao",
"outro"
],
"type": "string",
"description": "Consulting: the kind of project (`llm_privado`, `voz`, `dados_sensiveis`, `gpu`, `integracao` or `outro`)."
},
"horarios": {
"type": "array",
"items": {
"type": "string"
},
"description": "Consulting: up to 3 times for the call, `YYYY-MM-DDTHH:MM` in that time zone."
},
"whatsapp": {
"type": "string",
"description": "Optional reply number with country code, such as +5561999999999."
},
"orcamento": {
"enum": [
"ate_100",
"100_500",
"500_2000",
"2000_mais",
"a_combinar",
"ate_2000",
"2000_5000",
"5000_10000",
"10000_mais",
"nao_sei"
],
"type": "string",
"description": "Advertising: `ate_100`, `100_500`, `500_2000`, `2000_mais` or `a_combinar`. Consulting, in US dollars: `ate_2000`, `2000_5000`, `5000_10000`, `10000_mais` or `nao_sei`."
},
"pagamento": {
"enum": [
"usdc",
"deposito",
"a_combinar"
],
"type": "string",
"description": "`usdc`, `deposito` or `a_combinar`."
},
"prefer_whatsapp": {
"type": "boolean",
"description": "Request a WhatsApp reply. Requires whatsapp."
}
}
},
"annotations": {
"title": "Contact",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}