Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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

REMOTE · GOLEMREACH.COM

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

Available components

0 this week 78 Trust /100

Last scanned (12 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

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
Transport & Reachability100
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 3 Oct 26 0
    • Stability: 0.97 → pass security
  • 2 Oct 26 0
    • Stability: pass → 0.97 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 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 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA384 6f7646b0d4d3de9c80c93140f5e1ab2a2e8
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. DS published 19718 13 Verified
golemreach.com. No DS 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
MCP tools · 5 exposed · ~665 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
depends_onarray–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_sinteger–extra seconds of slack before DOWN (0-86400)
kindstring–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
namestringyesunique name, 1-40 chars [A-Za-z0-9_.-]
pass_keystring–Pro pass key from a $5 USDC payment (optional; skips rate limits)
period_sinteger–expected seconds between pings (60-86400)
target_urlstring–public http(s) URL to probe (pull only)
webhook_urlstring–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.

NameTypeReqDescription
keystring–monitor key (private lookup; also returns ping/fail URLs)
namestring–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.

NameTypeReqDescription
keystring–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.

NameTypeReqDescription
endpointsarray–selfcheck monitors only: one object per probed surface, e.g. {"name":"claude-session","status_code":200,"cf_mitigated":false,"tls_ms":230}
keystringyesmonitor 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.

NameTypeReqDescription
keystringyes–

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http aniripsaretro-max-golemreach-heartbeat 'https://golemreach.com/heartbeat/mcp'
Common questions

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 78 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Heartbeat — dead-man switch for cron jobs & AI agents MCP server?

VerifyMCP ran 12 checks on Heartbeat — dead-man switch for cron jobs & AI agents, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Heartbeat — dead-man switch for cron jobs & AI agents: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.