MCP server

Hookpulse Official

net.hookpulse/hookpulse

Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools

Dead-man switch for cron and webhooks: ingest URL, miss detection, alerts and a status feed.

Website Source

At a glance

Type

MCP server

Publisher

hookpulse.net (verified by the MCP Registry)

Status

Working at last check

Tools

24

Token cost

About 4,823 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

claude mcp add --transport http hookpulse https://hookpulse.net/mcp

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.hookpulse]
url = "https://hookpulse.net/mcp"

Gemini CLI

{"mcpServers":{"hookpulse":{"httpUrl":"https://hookpulse.net/mcp"}}}

Cursor

{"mcpServers":{"hookpulse":{"url":"https://hookpulse.net/mcp"}}}

VS Code

{"servers":{"hookpulse":{"type":"http","url":"https://hookpulse.net/mcp"}}}

Antigravity

agy mcp add hookpulse https://hookpulse.net/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"hookpulse","server_url":"https://hookpulse.net/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"hookpulse","server_url":"https://hookpulse.net/mcp"}

Tools

• api_index ~34 tokens
  Full index of the HookPulse API.
• check_site ~163 tokens
  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
• contact ~874 tokens
  Write to the people behind the product: a question, or a sponsorship/partnership/advertising proposal. One route for a question and for a sponsorship, partnership or ad proposal (`tipo`, with the placements of `GET /api/partners`). One message every 10 seconds per network: one that arrives sooner wa
• create_endpoint ~702 tokens
  Create a monitor for a routine. Use cron, tz and grace_sec for a schedule, or interval_sec for a fixed check-in interval. Set max_duration_sec to detect an open run that exceeds its time limit. With `check` the monitor is a site: HookPulse calls `check.url` every `interval_sec` (default 300) and ale
• create_guest ~66 tokens
  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.
• create_site ~678 tokens
  Monitor a website: HookPulse calls check.url every interval_sec (default 300) and alerts when it goes down and when it is back. With `check` the monitor is a site: HookPulse calls `check.url` every `interval_sec` (default 300) and alerts when it goes down — two failed checks in a row, one minute apa
• delete_endpoint Deletes data · ~74 tokens
  Removes the owner's endpoint.
• get_endpoint ~156 tokens
  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.
• health ~27 tokens
  Liveness.
• import_crontab ~308 tokens
  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
• ingest_key ~109 tokens
  Returns (minting the first time) the key for /in/<key>/<slug>, where a ping creates its own monitor inside the free tier. Instruments a whole fleet with no setup call per job. One key per owner. The key survives signing in: the crontab you deployed keeps working.
• ingest_key_rotate ~89 tokens
  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.
• list_endpoints ~54 tokens
  Lists the guest's/session's endpoints.
• list_events ~90 tokens
  Latest ingest pings.
• list_sites ~66 tokens
  The state of every site you monitor (up, down, waiting, paused), with the last check.
• list_templates ~96 tokens
  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.
• ping_ingest ~86 tokens
  Simulates the cron: GET on /in/:id. No credential on purpose — the caller is a cron, and the ID is already the secret.
• ping_slug ~184 tokens
  Create a monitor on its first check-in. The same slug uses the same monitor. A rejected creation writes no monitor or event. The slug becomes the monitor name and its identity: the same slug always means the same monitor, so a retry never creates a second one. Normalised to lowercase, `[a-z0-9-]`, 4
• signal_exit_code ~160 tokens
  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.
• signal_fail ~177 tokens
  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_pend
• signal_slug ~241 tokens
  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
• signal_start ~240 tokens
  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
• status_feed_rotate ~54 tokens
  Rotates the status feed token; the previous URL stops working.
• status_feed_url ~95 tokens
  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.

Browse

• Website monitoring
• Email
• Team chat
• Advertising

Related MCP servers

• Mockbird
  Mock REST APIs, fake OAuth2/OIDC provider, uptime monitors + heartbeats, live badge/QR images.
• Heartbeat — dead-man switch for cron jobs & AI agents
  Dead-man switch monitors for cron & AI agents with dependency-cascade alerts. No account needed.
• Vigil — an outside witness for AI agents
  Agent leases, signed receipts, watchdogs, and optional paid source-verification evidence.
• ZenVault
  Wake-ups, webhook inboxes, TTL memory, watches and human approval for agents. Paid per call.
• AIS Agent Flight Recorder — dead-man alerts & resume for AI agents
  Dead-man switch for AI agents & cron jobs: heartbeat with state capsule, alerts + resume links
• Paw Pulse
  Heartbeat and tokens/sec monitoring for self-hosted LLM servers (Ollama etc.), with down alerts.
• TunnelMind Data API
  Tracker / Sigil / Cross-lens — every TunnelMind Data API operation as one MCP surface.
• sebbi.pro - the proof layer for AI
  Score, seal and prove AI decisions in Bitcoin, plus 755 compliance checks, free to verify.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/net.hookpulse/hookpulse.svg)](https://aptlynx.net/servers/net.hookpulse/hookpulse)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents