mcpbeat Sign in

Heartbeat — dead-man switch for cron jobs & AI agents MCP Server

answering

Heartbeat — dead-man switch for cron jobs & AI agents is answering right now. Last checked 3 min ago. It exposes 5 tools. Last commit 26 Aug 2026.

Dead-man switch monitors for cron & AI agents with dependency-cascade alerts. No account needed.

Uptime history 6 days of history · worst day 18%
6 days agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
189 ms
Response time
average over 24h
1
Stars
last commit 26 Aug 2026

What the code does

We read the source, 13 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a database query by concatenation packages/assets/src/creatures.ts:1297
    const drop = 2 + Math.sin(t * 9 + pose.f * 2.1) * 2.2 + n * 3;
Runs an external command tools/shell-tour.mjs:145
  const child = spawn(process.execPath, ['packages/server/dist/main.js'], {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add golemreach-heartbeat --transport http https://golemreach.com/heartbeat/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "golemreach-heartbeat": {
      "url": "https://golemreach.com/heartbeat/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.golemreach-heartbeat]
url = "https://golemreach.com/heartbeat/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "golemreach-heartbeat": {
      "url": "https://golemreach.com/heartbeat/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "golemreach-heartbeat": {
      "url": "https://golemreach.com/heartbeat/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

heartbeat
create_heartbeat
Arm a new dead-man switch monitor. Returns the key plus a ping_url your job must hit after every run. No account needed. Names are globally unique on this instance and each name gets a PUBLIC status page; the secret key is the only credential — keep it.
heartbeats
list_heartbeats
List monitors on this Heartbeat instance with current status (new/up/late/down). Names and statuses are public by design — every monitor has a public status page. Pass your secret key to also include that monitor's private ping/fail URLs in the result.
ping
ping_heartbeat
Record one successful run for a monitor (same as GETting https://golemreach.com/heartbeat/ping/<key>). Call this every time your job runs. For kind=selfcheck monitors pass an 'endpoints' array of {"name","status_code","cf_mitigated","tls_ms"} objects instead — alerts fire on trusted->challenged / recovery transitions only.
record
record_failure
Explicitly mark a run as FAILED for a monitor (same as GET https://golemreach.com/heartbeat/fail/<key>). The monitor goes DOWN immediately and alerts fire.
status
get_status
Full current state of one monitor: status, 30-day uptime %, schedule, last ping, alert config, recent event history and its public URLs. Look up by name OR by your secret key; key lookups additionally return the private ping/fail URLs.

Endpoints

URLTransportStateLatencyChecked
https://golemreach.com/heartbeat/mcp streamable-http answering 188 ms 3 min ago

Alternatives to Heartbeat — dead-man switch for cron jobs & AI agents

same job, measured the same way
A
AIS Agent Flight Recorder — dead-man alerts & resume for AI agents
by aislabs

Dead-man switch for AI agents & cron jobs: heartbeat with state capsule, alerts + resume links

5 tools answering
D
Heartbeat Monitor
by workers-cronping-oren-cronping

Dead-man's-switch for cron jobs & AI agents. Import a crontab to arm one silent-miss alert per job.

7 tools answering
Agent Domains
by clize

Domains your AI agent can buy, point and monitor, with four-layer health checks and alerts.

local only
Datasieve
by gitwormq

On-chain watches, web-page monitors, dead-man switches, cron, and agent coordination, paid via x402.

68 installs/wk local only
PageCrawl
by pagecrawl

Monitor web pages for changes with AI-powered change detection, diffs, and alerts.

answering
I
Ground Truth - Fresh Evidence for AI Agents
by anish632

Keep AI answers fresh with free source previews, scheduled monitoring, evidence history, and alerts.

19 tools answering
Betterstack
by usefulapi

Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

9 tools answering
LastPing
by lastping

Monitoring that agents set up for themselves — cron jobs, CI/CD pipelines and AI agent runs.

answering

Heartbeat — dead-man switch for cron jobs & AI agents — questions

Answers built from our own checks of this server.

What can Heartbeat — dead-man switch for cron jobs & AI agents do?
It exposes 5 tools, read directly from the server on our last check. Among them: create_heartbeat, get_status, list_heartbeats, ping_heartbeat, record_failure. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Heartbeat — dead-man switch for cron jobs & AI agents working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 189 ms. The bar chart above shows every period we have measured.
How do I connect Heartbeat — dead-man switch for cron jobs & AI agents?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Heartbeat — dead-man switch for cron jobs & AI agents need an API key?
No. Heartbeat — dead-man switch for cron jobs & AI agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Heartbeat — dead-man switch for cron jobs & AI agents?
It answers our handshake in 189 ms on average, which is faster than 74% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Heartbeat — dead-man switch for cron jobs & AI agents open source?
Yes — written in TypeScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.