Remote dead-man switch service that lets an assistant arm, ping and inspect heartbeat monitors for cron jobs and AI agents.
What you can do
Create and arm new heartbeat monitors, receiving a secret key and a ping URL the job must call after each run
Record successful runs by pinging a monitor, or explicitly mark a run as failed so the monitor goes down and alerts fire
List monitors on the instance with their current status (new, up, late, down)
Inspect one monitor's full state: status, 30-day uptime, schedule, last ping, alert config and recent event history
Submit endpoint check results for self-check monitors, where alerts fire on status changes
When to use it
Useful when you want an assistant to set up or maintain uptime monitoring for scheduled jobs, cron tasks or agent runs, and to check whether those jobs have stopped reporting in.
Requirements
A remote MCP endpoint at golemreach.com over streamable HTTP; no account, environment variables or headers are declared. Each monitor's secret key is the credential used for private ping and fail URLs.
Before you install
The secret key is the only credential for a monitor and should be kept private. Monitor names are globally unique and every monitor gets a public status page, so names and statuses are visible to anyone. Pinging and failure recording change monitor state and can trigger alerts.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.aniripsaretro-max%2Fgolemreach-heartbeat/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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 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.
Parameterskeyrequiredendpoints
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.
Parameterskeyrequired
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.
Parameterskey
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.
Parameterskeyname
Version history
1
v0.4.0LatestSep 16, 2026
Score
75%
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.