hookpulse
Know when a job stops or a site goes down after the agent exits. Free monitors; paid extra coverage.
使うべきか
品質と安全性
検出事項(2)
- LOWapi_index 内
- LOWstatus_feed_url 内
ツール定義とプロトコルへの準拠に関する自動分析に基づいています。
コンテキストコスト
これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。
インストール
ワンクリックインストール
これを `claude_desktop_config.json` ファイルに追加してください:
{
"mcpServers": {
"hookpulse": {
"url": "https://hookpulse.net/mcp"
}
}
}リモートエンドポイント
https://hookpulse.net/mcpstreamable-httpできること
ツール一覧
ツール(29)
🟢list_plans
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`.
入力スキーマ
{
"type": "object",
"properties": {}
}🟢buy_plan(plan)
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.
入力スキーマ
{
"type": "object",
"properties": {
"plan": {
"type": "string",
"enum": [
"starter",
"team",
"business"
],
"description": "`starter` (40 more monitors, up to 50), `team` (90 more monitors, up to 100), `business` (490 more monitors, up to 500)"
}
},
"required": [
"plan"
]
}🔴cancel_plan(accept_data_removal)
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.
入力スキーマ
{
"type": "object",
"properties": {
"accept_data_removal": {
"type": "boolean",
"const": true,
"description": "Must be `true`: you accept losing what the plan added."
}
},
"required": [
"accept_data_removal"
]
}🟢api_index
Full index of the HookPulse API.
入力スキーマ
{
"type": "object",
"properties": {}
}🟢health
Read service liveness before using HookPulse. Returns the health response; does not check a monitor.
入力スキーマ
{
"type": "object",
"properties": {}
}🟡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.
入力スキーマ
{
"type": "object",
"properties": {}
}🟢list_endpoints(guest_token)
Lists the guest's/session's endpoints.
入力スキーマ
{
"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."
}
},
"required": [
"guest_token"
]
}🟡create_endpoint(guest_token, name, interval_sec, cron, paused_until, ...)
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.
入力スキーマ
{
"type": "object",
"properties": {
"guest_token": {
"type": "string",
"description": "Existing owner token, if available."
},
"name": {
"type": "string",
"description": "how you will recognise the routine in an alert; required, trimmed, max 80 chars, punctuation alone is rejected"
},
"interval_sec": {
"type": "number",
"description": "Tolerated silence, in seconds. Below the free minimum, it costs."
},
"cron": {
"type": "string",
"description": "five-field cron, e.g. 0 3 * * *"
},
"paused_until": {
"type": "string",
"description": "maintenance window end (UTC ISO), max 30 days ahead"
},
"tz": {
"type": "string",
"description": "IANA time zone for cron, default UTC"
},
"grace_sec": {
"type": "number",
"description": "tolerance after the scheduled time, default 90, min 30"
},
"max_duration_sec": {
"type": "number",
"description": "ceiling for an open run in seconds, 60..86400; null or 0 turns it off"
},
"alert_repeat_sec": {
"type": "number",
"description": "gap before the same incident alerts again, 3600..2592000; null keeps the 86400 default"
},
"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)."
}
},
"required": [
"name"
]
}🟡create_site(guest_token, check, name, interval_sec, paused_until, ...)
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.
入力スキーマ
{
"type": "object",
"properties": {
"guest_token": {
"type": "string",
"description": "Existing owner token, if available."
},
"check": {
"type": "object",
"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)",
"properties": {
"url": {
"type": "string",
"description": "Public HTTP or HTTPS URL to check."
},
"method": {
"type": "string",
"description": "HTTP method: GET or HEAD."
},
"expect_status": {
"type": "string",
"description": "Accepted status code or range, for example 200 or 200-399. Default: 200-399."
},
"keyword": {
"type": "string",
"description": "Text that the returned page must contain."
},
"timeout_ms": {
"type": "number",
"description": "Request timeout in milliseconds, from 1000 to 30000."
}
},
"required": [
"url"
]
},
"name": {
"type": "string",
"description": "how you will recognise the site in an alert; default: its host"
},
"interval_sec": {
"type": "number",
"description": "seconds between checks, default 300"
},
"paused_until": {
"type": "string",
"description": "maintenance window end (UTC ISO), max 30 days ahead"
},
"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."
},
"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)."
}
},
"required": [
"check"
]
}🟢check_site(id, guest_token)
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.
入力スキーマ
{
"type": "object",
"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."
}
},
"required": [
"id",
"guest_token"
]
}🟢list_sites(guest_token)
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.
入力スキーマ
{
"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."
}
},
"required": [
"guest_token"
]
}🟢import_crontab(guest_token, crontab, apply)
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.
入力スキーマ
{
"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."
},
"crontab": {
"type": "string",
"description": "the crontab text"
},
"apply": {
"type": "string",
"description": "\"1\" to create the monitors"
}
},
"required": [
"guest_token",
"crontab"
]
}🟢get_endpoint(id, token, guest_token)
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.
入力スキーマ
{
"type": "object",
"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."
}
},
"required": [
"id"
]
}🔴delete_endpoint(guest_token, id)
Removes the owner's endpoint.
入力スキーマ
{
"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."
},
"id": {
"type": "string",
"description": "ID of the monitor to deactivate."
}
},
"required": [
"guest_token",
"id"
]
}🟢list_events(id, token, guest_token)
Latest ingest pings.
入力スキーマ
{
"type": "object",
"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."
}
},
"required": [
"id"
]
}🟢ping_ingest(id)
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.
入力スキーマ
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Monitor ID, from `Monitor.ingest_url`."
}
},
"required": [
"id"
]
}🟢signal_start(id)
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.
入力スキーマ
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Monitor ID, from `Monitor.ingest_url`."
}
},
"required": [
"id"
]
}🟢signal_fail(id)
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.
入力スキーマ
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Monitor ID, from `Monitor.ingest_url`."
}
},
"required": [
"id"
]
}🟢signal_exit_code(id, exit_code)
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.
入力スキーマ
{
"type": "object",
"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."
}
},
"required": [
"id",
"exit_code"
]
}🟢ingest_key(guest_token)
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.
入力スキーマ
{
"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."
}
}
}🔴ingest_key_rotate(guest_token)
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.
入力スキーマ
{
"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."
}
}
}🟢ping_slug(ingestKey, slug)
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.
入力スキーマ
{
"type": "object",
"properties": {
"ingestKey": {
"type": "string",
"description": "Ingest key, from `GET /api/ingest-key`."
},
"slug": {
"type": "string",
"description": "Name of the job; it becomes the monitor name."
}
},
"required": [
"ingestKey",
"slug"
]
}🟢signal_slug(ingestKey, slug, signal)
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.
入力スキーマ
{
"type": "object",
"properties": {
"ingestKey": {
"type": "string",
"description": "Ingest key, from `GET /api/ingest-key`."
},
"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"
}
},
"required": [
"ingestKey",
"slug",
"signal"
]
}🟢pricing
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`).
入力スキーマ
{
"type": "object",
"properties": {}
}🟢status_feed_url(guest_token)
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.
入力スキーマ
{
"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."
}
}
}🔴status_feed_rotate(guest_token)
Rotates the status feed token; the previous URL stops working.
入力スキーマ
{
"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."
}
}
}🟢list_templates
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.
入力スキーマ
{
"type": "object",
"properties": {}
}🟡contact(name, email, message, whatsapp, prefer_whatsapp, ...)
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.
入力スキーマ
{
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "What to call the person writing."
},
"email": {
"type": "string",
"description": "Where to reply."
},
"message": {
"type": "string",
"description": "What you want to say."
},
"whatsapp": {
"type": "string",
"description": "Optional reply number with country code, such as +5561999999999."
},
"prefer_whatsapp": {
"type": "boolean",
"description": "Request a WhatsApp reply. Requires whatsapp."
},
"tipo": {
"type": "string",
"enum": [
"patrocinio",
"parceria",
"anuncio",
"consultoria"
],
"description": "Proposal: `patrocinio`, `parceria`, `anuncio` or `consultoria`. Turns on the fields below."
},
"empresa": {
"type": "string",
"description": "Who is proposing, when it is a company."
},
"site": {
"type": "string",
"description": "Website of who is proposing."
},
"orcamento": {
"type": "string",
"enum": [
"ate_100",
"100_500",
"500_2000",
"2000_mais",
"a_combinar",
"ate_2000",
"2000_5000",
"5000_10000",
"10000_mais",
"nao_sei"
],
"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`."
},
"espaco": {
"type": "array",
"items": {
"type": "string"
},
"description": "Placement ids from `GET /api/partners`, up to 6."
},
"duracao": {
"type": "string",
"enum": [
"30",
"90",
"365"
],
"description": "Exposure in days: `30`, `90` or `365`."
},
"pagamento": {
"type": "string",
"enum": [
"usdc",
"deposito",
"a_combinar"
],
"description": "`usdc`, `deposito` or `a_combinar`."
},
"projeto": {
"type": "string",
"enum": [
"llm_privado",
"voz",
"dados_sensiveis",
"gpu",
"integracao",
"outro"
],
"description": "Consulting: the kind of project (`llm_privado`, `voz`, `dados_sensiveis`, `gpu`, `integracao` or `outro`)."
},
"prazo": {
"type": "string",
"enum": [
"agora",
"1_mes",
"1_3_meses",
"explorando"
],
"description": "Consulting: when to start (`agora`, `1_mes`, `1_3_meses` or `explorando`)."
},
"formato": {
"type": "string",
"enum": [
"projeto",
"mensal",
"assessoria"
],
"description": "Consulting: `projeto` (per scope), `mensal` (monthly) or `assessoria` (advisory)."
},
"pais": {
"type": "string",
"description": "Consulting: the country of the person asking."
},
"fuso": {
"type": "string",
"description": "Consulting: the IANA time zone, such as `America/New_York`."
},
"horarios": {
"type": "array",
"items": {
"type": "string"
},
"description": "Consulting: up to 3 times for the call, `YYYY-MM-DDTHH:MM` in that time zone."
}
},
"required": [
"name",
"email",
"message"
]
}🟢get_api_x402_check(url, method, expect_status, keyword, timeout_ms)
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.
入力スキーマ
{
"type": "object",
"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`."
},
"expect_status": {
"type": "string",
"description": "What counts as up: `200-399` by default, a range `a-b` or one code."
},
"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."
}
},
"required": [
"url"
],
"additionalProperties": false
}推奨プロンプト
get_endpointget_endpointlist_endpointslist_endpointslist_endpointsget_endpointコミュニティ
エビデンス