Heartbeat — dead-man switch for cron jobs & AI agents
REMOTE · GOLEMREACH.COM · SCANNED SEP 24
Dead-man switch monitors for cron & AI agents with dependency-cascade alerts. No account needed.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 883 tokens (~176/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Heartbeat — dead-man switch for cron jobs & AI agents MCP server?
Heartbeat — dead-man switch for cron jobs & AI agents is a hosted endpoint at https://golemreach.com/heartbeat/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · golemreach.com
claude mcp add --transport http aniripsaretro-max-golemreach-heartbeat 'https://golemreach.com/heartbeat/mcp'
{
"mcpServers": {
"aniripsaretro-max-golemreach-heartbeat": {
"url": "https://golemreach.com/heartbeat/mcp"
}
}
} {
"servers": {
"aniripsaretro-max-golemreach-heartbeat": {
"type": "http",
"url": "https://golemreach.com/heartbeat/mcp"
}
}
} [mcp_servers.aniripsaretro-max-golemreach-heartbeat] url = "https://golemreach.com/heartbeat/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aniripsaretro-max-golemreach-heartbeat": {
"type": "remote",
"url": "https://golemreach.com/heartbeat/mcp",
"enabled": true
}
}
} openclaw mcp add aniripsaretro-max-golemreach-heartbeat --url 'https://golemreach.com/heartbeat/mcp' --transport streamable-http
mcp_servers:
aniripsaretro-max-golemreach-heartbeat:
url: "https://golemreach.com/heartbeat/mcp" {
"McpServers": {
"aniripsaretro-max-golemreach-heartbeat": {
"Transport": "http",
"Url": "https://golemreach.com/heartbeat/mcp"
}
}
} assistant mcp add aniripsaretro-max-golemreach-heartbeat -t streamable-http -u 'https://golemreach.com/heartbeat/mcp'
{
"mcpServers": {
"aniripsaretro-max-golemreach-heartbeat": {
"type": "http",
"url": "https://golemreach.com/heartbeat/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://golemreach.com/heartbeat/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=golemreach.com | CN=YE2,O=Let's Encrypt,C=US | 8 Aug 2026 | 6 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 68274504b488120a0212a289cdf1fcd447e |
| SANs: golemreach.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of golemreach.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| golemreach.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://golemreach.com/heartbeat/mcp | Verified | 200 | |
| http (plaintext) | http://golemreach.com/heartbeat/mcp | HTTPS enforced | 308 | https://golemreach.com/heartbeat/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_heartbeat ~295
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.
| Name | Type | Req | Description |
|---|---|---|---|
| depends_on | array | – | parent monitor names and/or gate:<gate-name> entries (max 5). When a parent is DOWN or a gate parent is HALT this monitor becomes DEGRADED-BY-UPSTREAM: notified once, own silence paging suppressed un… |
| grace_s | integer | – | extra seconds of slack before DOWN (0-86400) |
| kind | string | – | push = you ping us; pull = we probe target_url every min(period_s,60)s; selfcheck = your box runs our egress-trust probe script and POSTs verdict reports to the ping URL |
| name | string | yes | unique name, 1-40 chars [A-Za-z0-9_.-] |
| pass_key | string | – | Pro pass key from a $5 USDC payment (optional; skips rate limits) |
| period_s | integer | – | expected seconds between pings (60-86400) |
| target_url | string | – | public http(s) URL to probe (pull only) |
| webhook_url | string | – | public http(s) URL that receives UP/DOWN alerts (optional) |
No output schema declared.
No examples provided.
get_status ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | monitor key (private lookup; also returns ping/fail URLs) |
| name | string | – | monitor name (public lookup) |
No output schema declared.
No examples provided.
list_heartbeats ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | optional monitor key; adds the private ping_url/fail_url for that one monitor |
No output schema declared.
No examples provided.
ping_heartbeat ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoints | array | – | selfcheck monitors only: one object per probed surface, e.g. {"name":"claude-session","status_code":200,"cf_mitigated":false,"tls_ms":230} |
| key | string | yes | monitor key returned by create_heartbeat |
No output schema declared.
No examples provided.
record_failure ~51
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
No output schema declared.
No examples provided.
What is the Heartbeat — dead-man switch for cron jobs & AI agents MCP server?
Heartbeat — dead-man switch for cron jobs & AI agents is an MCP server listed in the public MCP registry as io.github.aniripsaretro-max/golemreach-heartbeat. Dead-man switch monitors for cron & AI agents with dependency-cascade alerts. No account needed. This page covers its hosted endpoint (https://golemreach.com/heartbeat/mcp).
Is the Heartbeat — dead-man switch for cron jobs & AI agents MCP server safe to use?
Heartbeat — dead-man switch for cron jobs & AI agents scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Heartbeat — dead-man switch for cron jobs & AI agents MCP server expose?
Heartbeat — dead-man switch for cron jobs & AI agents exposes 5 tools: create_heartbeat, ping_heartbeat, record_failure, list_heartbeats, get_status. Their descriptions and schemas cost roughly 665 tokens of context every time the server is loaded.
Does the Heartbeat — dead-man switch for cron jobs & AI agents MCP server require authentication?
No. We connected to Heartbeat — dead-man switch for cron jobs & AI agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Heartbeat — dead-man switch for cron jobs & AI agents MCP server still maintained?
Heartbeat — dead-man switch for cron jobs & AI agents is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.