Skip to content

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

by aniripsaretro-max · remote · no sign-in to list tools · v0.4.0 · published by GitHub user aniripsaretro-max

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

Changes · 2
CompareRegistry entry

5 tools: 2 change things and 3 only read.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http golemreach-heartbeat https://golemreach.com/heartbeat/mcp

Findings

Matches of fixed checks, with the text they matched.

1 info

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 2Claude Code: ask
  • create_heartbeatArm a new dead-man switch monitor.1 finding

    Why it is in this group

    • The name "create_heartbeat" says "create": a word for a change.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...status page; the secret key is the only credential — keep it."

      What this check looks for
    Description, as the server wrote it
    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.
  • record_failureExplicitly mark a run as FAILED for a monitor (same as GET https://golemreach.com/heartbeat/fail/<key>).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 3Claude Code: allow
  • get_statusFull current state of one monitor: status, 30-day uptime %, schedule, last ping, alert config, recent event history and its public URLs.No findings

    Why it is in this group

    • The name "get_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • list_heartbeatsList monitors on this Heartbeat instance with current status (new/up/late/down).No findings

    Why it is in this group

    • The name "list_heartbeats" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • ping_heartbeatRecord one successful run for a monitor (same as GETting https://golemreach.com/heartbeat/ping/<key>).No findings

    Why it is in this group

    • The name "ping_heartbeat" says "ping": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http golemreach-heartbeat https://golemreach.com/heartbeat/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__golemreach-heartbeat__ping_heartbeat",
      "mcp__golemreach-heartbeat__list_heartbeats",
      "mcp__golemreach-heartbeat__get_status"
    ],
    "ask": [
      "mcp__golemreach-heartbeat__create_heartbeat",
      "mcp__golemreach-heartbeat__record_failure"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as golemreach-heartbeat. Review it before you use it.