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 11 min ago. It exposes 5 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 52 days of history · worst day 18%
52 days agonow
100.0%
Uptime 24h
92 of 92 checks
5
Tools
read from the server
180 ms
Response time
average over 24h
open, no key
Access
streamable-http

What the code does

We have not read this server's code yet, 39 d 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 11 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 140 ms 11 min ago

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

same job, measured the same way
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
Agent Domains
by clize

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

178 installs/wk local only
Hookpulse
by hookpulse

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

24 tools answering
Datasieve
by gitwormq

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

39 installs/wk local only
LastPing
by lastping

AI agent monitoring: alerts when your agents fail, stall or need you

50 tools answering
PageCrawl
by pagecrawl

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

answering
Vivere
by vivere

Know when cron jobs and AI agents stop running: create monitors and check in from your agent.

7 tools answering
MCP Kafka
by dockndevai

Apache Kafka monitoring & management for AI agents (with consumer lag) — governed.

74 installs/wk local only

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 92 of 92 checks got a reply (100.0%), average response time 180 ms. The bar chart above shows every period we have measured.
Is Heartbeat — dead-man switch for cron jobs & AI agents still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
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 180 ms on average, which is faster than 67% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.