Mmcp.market

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

by aniripsaretro-max·io.github.aniripsaretro-max/golemreach-heartbeat·v0.4.0

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

C57/100grade C
What users say
No reviews yet
Be the first
Safety scan
C57/100

full report

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Heartbeat — dead-man switch for cron jobs & AI agents yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Heartbeat — dead-man switch for cron jobs & AI agents tools (5, 1 write)

write = sends, deletes, buys or posts
  • create_heartbeatwrite actionFree

    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.

  • get_statusFree

    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.

  • list_heartbeatsFree

    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_heartbeatFree

    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_failureFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-21 · same rubric, same numbers if you re-run it

1 high
  • Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 975ms20/20
  • Tool poisoning5 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
  • Maintenancerepository not readable: repo not found3/15
  • Maintainer identityno repository or website to verify2/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 57/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install directly

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

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

Is Heartbeat — dead-man switch for cron jobs & AI agents MCP server safe?
With care: it is graded C, so read the findings first (57/100). Read the Heartbeat — dead-man switch for cron jobs & AI agents safety report
How do I install Heartbeat — dead-man switch for cron jobs & AI agents?
It runs remotely at golemreach.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Heartbeat — dead-man switch for cron jobs & AI agents need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Heartbeat — dead-man switch for cron jobs & AI agents maintained?
The latest release is v0.4.0.
Is Heartbeat — dead-man switch for cron jobs & AI agents up?
100% of our last 19 checks got an answer. We check remote servers about four times a day.

More from aniripsaretro-max