net.hookpulse/hookpulse
REMOTE · HOOKPULSE.NET
Know when a job stops or a site goes down after the agent exits. Free monitors; paid extra coverage.
Available components
Last scanned (13 hours ago)
Scores higher than 72% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_endpoint). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5369 tokens (~185/item across 29 items; 29 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "signal_slug" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 0
- Server version: 2eb364ef → 59fb6587 functional
- 20 Nov 26 0
- Server version: cc77c70e → 2eb364ef functional
- 19 Nov 26 0
- Server version: 1a301ea6 → cc77c70e functional
- 18 Nov 26 0
- Server version: 9ae8286a → 1a301ea6 functional
- 17 Nov 26 0
- Server version: 350519f4 → 9ae8286a functional
- 16 Nov 26 0
- Server version: fdf6d958 → 350519f4 functional
- 15 Nov 26 +6
- Stability: fail → pass ▲ security
- Server version: ef1ee6a8 → fdf6d958 functional
- 14 Nov 26 0
- Server version: e255e2c2 → ef1ee6a8 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://hookpulse.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hookpulse.net | CN=YE2,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 53d032a66fd16ad666364b93ae7e3b5f1bb |
| SANs: hookpulse.net, www.hookpulse.net | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hookpulse.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| hookpulse.net. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hookpulse.net/mcp | Verified | 200 | |
| http (plaintext) | http://hookpulse.net/mcp | HTTPS enforced | 301 | https://hookpulse.net/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
api_index API index ~16
Full index of the HookPulse API.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
buy_plan Buy plan ~233
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.
| Name | Type | Req | Description |
|---|---|---|---|
| plan | string | yes | `starter` (40 more monitors, up to 50), `team` (90 more monitors, up to 100), `business` (490 more monitors, up to 500) |
No output schema declared.
No examples provided.
cancel_plan Cancel plan ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_data_removal | boolean | yes | Must be `true`: you accept losing what the plan added. |
No output schema declared.
No examples provided.
check_site Check site ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | yes | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
| id | string | yes | ID of the site monitor, from `Monitor.id`. |
No output schema declared.
No examples provided.
contact Contact ~652
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.
| Name | Type | Req | Description |
|---|---|---|---|
| duracao | string | – | Exposure in days: `30`, `90` or `365`. |
| string | yes | Where to reply. | |
| empresa | string | – | Who is proposing, when it is a company. |
| espaco | array | – | Placement ids from `GET /api/partners`, up to 6. |
| formato | string | – | Consulting: `projeto` (per scope), `mensal` (monthly) or `assessoria` (advisory). |
| fuso | string | – | Consulting: the IANA time zone, such as `America/New_York`. |
| horarios | array | – | Consulting: up to 3 times for the call, `YYYY-MM-DDTHH:MM` in that time zone. |
| message | string | yes | What you want to say. |
| name | string | yes | What to call the person writing. |
| 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`. |
| pais | string | – | Consulting: the country of the person asking. |
| prazo | string | – | Consulting: when to start (`agora`, `1_mes`, `1_3_meses` or `explorando`). |
| prefer_whatsapp | boolean | – | Request a WhatsApp reply. Requires whatsapp. |
| projeto | string | – | Consulting: the kind of project (`llm_privado`, `voz`, `dados_sensiveis`, `gpu`, `integracao` or `outro`). |
| site | string | – | Website of who is proposing. |
| tipo | string | – | Proposal: `patrocinio`, `parceria`, `anuncio` or `consultoria`. Turns on the fields below. |
| string | – | Optional reply number with country code, such as +5561999999999. |
No output schema declared.
No examples provided.
create_endpoint Create endpoint ~444
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_repeat_sec | number | – | gap before the same incident alerts again, 3600..2592000; null keeps the 86400 default |
| 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). |
| cron | string | – | five-field cron, e.g. 0 3 * * * |
| grace_sec | number | – | tolerance after the scheduled time, default 90, min 30 |
| guest_token | string | – | Existing owner token, if available. |
| interval_sec | number | – | Tolerated silence, in seconds. Below the free minimum, it costs. |
| max_duration_sec | number | – | ceiling for an open run in seconds, 60..86400; null or 0 turns it off |
| name | string | yes | how you will recognise the routine in an alert; required, trimmed, max 80 chars, punctuation alone is rejected |
| paused_until | string | – | maintenance window end (UTC ISO), max 30 days ahead |
| tags | array | – | up to 8 tags to group the monitor; lower-cased, [a-z0-9._-], max 32 chars each |
| tz | string | – | IANA time zone for cron, default UTC |
No output schema declared.
No examples provided.
create_guest Create guest ~41
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_site Create site ~379
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
| check | object | yes | 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) |
| guest_token | string | – | Existing owner token, if available. |
| interval_sec | number | – | seconds between checks, default 300 |
| name | string | – | how you will recognise the site in an alert; default: its host |
| paused_until | string | – | maintenance window end (UTC ISO), max 30 days ahead |
| 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`… |
No output schema declared.
No examples provided.
delete_endpoint Delete endpoint ~56
Removes the owner's endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | yes | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
| id | string | yes | ID of the monitor to deactivate. |
No output schema declared.
No examples provided.
get_api_x402_check Get API X402 check ~248
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expect_status | string | – | What counts as up: `200-399` by default, a range `a-b` or one code. |
| keyword | string | – | Text that must be in the first 64 KB of the page; it forces `GET`. |
| method | string | – | `GET` (default) or `HEAD`. |
| timeout_ms | integer | – | 1000 to 30000, default 10000. |
| url | string | yes | The address to call: http or https, public, without user or password. |
No output schema declared.
No examples provided.
get_endpoint Get endpoint ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | – | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
| id | string | yes | Monitor ID, from `Monitor.id`. |
| token | string | – | endpoint token (query) |
No output schema declared.
No examples provided.
health Health ~27
Read service liveness before using HookPulse. Returns the health response; does not check a monitor.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
import_crontab Import crontab ~447
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apply | string | – | "1" to create the monitors |
| crontab | string | yes | the crontab text |
| guest_token | string | yes | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
No output schema declared.
No examples provided.
ingest_key Ingest key ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | – | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
No output schema declared.
No examples provided.
ingest_key_rotate Ingest key rotate ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | – | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
No output schema declared.
No examples provided.
list_endpoints List endpoints ~47
Lists the guest's/session's endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | yes | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
No output schema declared.
No examples provided.
list_events List events ~75
Latest ingest pings.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | – | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
| id | string | yes | ID of the monitor. |
| token | string | – | Monitor token, alternative to the `X-Hook-Token` header. |
No output schema declared.
No examples provided.
list_plans List plans ~64
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`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sites List sites ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | yes | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
No output schema declared.
No examples provided.
list_templates List templates ~64
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ping_ingest Ping ingest ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor ID, from `Monitor.ingest_url`. |
No output schema declared.
No examples provided.
ping_slug Ping slug ~299
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ingestKey | string | yes | Ingest key, from `GET /api/ingest-key`. |
| slug | string | yes | Name of the job; it becomes the monitor name. |
No output schema declared.
No examples provided.
pricing Pricing ~108
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`).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
signal_exit_code Signal exit code ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exit_code | number | yes | Exit status, 0 to 255. Outside that range it is a 400. |
| id | string | yes | Monitor ID, from `Monitor.ingest_url`. |
No output schema declared.
No examples provided.
signal_fail Signal fail ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor ID, from `Monitor.ingest_url`. |
No output schema declared.
No examples provided.
signal_slug Signal slug ~177
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ingestKey | string | yes | Ingest key, from `GET /api/ingest-key`. |
| signal | string | yes | start, fail, or the exit code 0 to 255 |
| slug | string | yes | Name of the job; it becomes the monitor name. |
No output schema declared.
No examples provided.
signal_start Signal start ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor ID, from `Monitor.ingest_url`. |
No output schema declared.
No examples provided.
status_feed_rotate Status feed rotate ~52
Rotates the status feed token; the previous URL stops working.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | – | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
No output schema declared.
No examples provided.
status_feed_url Status feed URL ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| guest_token | string | – | Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources. |
No output schema declared.
No examples provided.
How do I install the net.hookpulse/hookpulse MCP server?
net.hookpulse/hookpulse is a hosted endpoint at https://hookpulse.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hookpulse.net
claude mcp add --transport http net-hookpulse-hookpulse 'https://hookpulse.net/mcp'
What is the net.hookpulse/hookpulse MCP server?
net.hookpulse/hookpulse is an MCP server listed in the public MCP registry as net.hookpulse/hookpulse. Know when a job stops or a site goes down after the agent exits. Free monitors; paid extra coverage. This page covers its hosted endpoint (https://hookpulse.net/mcp).
Is the net.hookpulse/hookpulse MCP server safe to use?
net.hookpulse/hookpulse scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the net.hookpulse/hookpulse MCP server expose?
net.hookpulse/hookpulse exposes 29 tools: list_plans, buy_plan, cancel_plan, api_index, health, and 24 more. Their descriptions and schemas cost roughly 4,832 tokens of context every time the server is loaded.
Does the net.hookpulse/hookpulse MCP server require authentication?
No. We connected to net.hookpulse/hookpulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the net.hookpulse/hookpulse MCP server still maintained?
net.hookpulse/hookpulse is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the net.hookpulse/hookpulse MCP server?
VerifyMCP ran 13 checks on net.hookpulse/hookpulse, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.