Heartbeat — dead-man switch for cron jobs & AI agents MCP server
io.github.aniripsaretro-max/golemreach-heartbeataniripsaretro-maxstreamable-httpv0.4.0Scanned
Dead-man switch monitors for cron & AI agents with dependency-cascade alerts. No account needed.
5 tools: 2 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 2
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Heartbeat — dead-man switch for cron jobs & AI agents MCP server can do
The Heartbeat — dead-man switch for cron jobs & AI agents MCP server is published by the GitHub account aniripsaretro-max. It has 5 tools. It can create or change data (2 tools: create_heartbeat and record_failure), but cannot delete data. 3 tools only read.
1 tool brings in text other people can write (ping_heartbeat); 2 tools can send data out of your system (create_heartbeat and ping_heartbeat).
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 0.4.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 2Claude Code: ask
create_heartbeatArm a new dead-man switch monitor.Can send data out1 finding
Why it is in this group
- The name "create_heartbeat" says "create": a word for a change.
What it can reach
- outboundThe input takes a URL (input.target_url): a request to a URL can carry data to whoever runs it.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...status page; the secret key is the only credential — keep it."
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 3Show 3 read-only tools
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>).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "ping_heartbeat" says "ping": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.endpoints), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.endpoints): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:02 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://golemreach.com/.well-known/oauth-protected-resource/heartbeat/mcp
- Authorization servers
- https://golemreach.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://golemreach.com/heartbeat/mcp: tools/list returned 5 tools to an anonymous client, including create_heartbeat (write), record_failure (write)
Posture changes
- Oct 29, 2026
- RFC 9728 protected resource metadata: none to https://golemreach.com/.well-known/oauth-protected-resource/heartbeat/mcp
- Authorization servers: none to https://golemreach.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Findings
Matches of fixed checks, with the text they matched.
- Infocreate_heartbeat
The description mentions "credential".
What this check looks forMatched text
description: "...status page; the secret key is the only credential — keep it."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://golemreach.com/.well-known/oauth-protected-resource/heartbeat/mcp; Authorization servers: none -> https://golemreach.com; Dynamic client registration: not observe…View diff
- RFC 9728 protected resource metadata: none to https://golemreach.com/.well-known/oauth-protected-resource/heartbeat/mcp
- Authorization servers: none to https://golemreach.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
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/mcpclaude mcp add --transport http golemreach-heartbeat https://golemreach.com/heartbeat/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__golemreach-heartbeat__list_heartbeats",
"mcp__golemreach-heartbeat__get_status"
],
"ask": [
"mcp__golemreach-heartbeat__create_heartbeat",
"mcp__golemreach-heartbeat__ping_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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as golemreach-heartbeat. Review it before you use it.
Capability tags behind 2 rules
- mcp__golemreach-heartbeat__create_heartbeat outbound
- mcp__golemreach-heartbeat__ping_heartbeat untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.aniripsaretro-max/golemreach-heartbeat/verify?hash=5f4088c08d1370acffa176eec1c1c8f55b63e24faa9ec27a1f96729e717d753e" | jq -e '.changed == false'Pinned hash 5f4088c08d13, from Nov 16, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.aniripsaretro-max/golemreach-heartbeat/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.aniripsaretro-max/golemreach-heartbeat)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:23 UTC.
Heartbeat — dead-man switch for cron jobs & AI agents MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Heartbeat — dead-man switch for cron jobs & AI agents MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Heartbeat — dead-man switch for cron jobs & AI agents MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Heartbeat — dead-man switch for cron jobs & AI agents MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Heartbeat — dead-man switch for cron jobs & AI agents MCP server have?
- 5 tools: 2 write, 3 read. create_heartbeat, record_failure, ping_heartbeat, list_heartbeats and get_status.
Does the Heartbeat — dead-man switch for cron jobs & AI agents MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Heartbeat — dead-man switch for cron jobs & AI agents MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_heartbeat and ping_heartbeat.
Has the Heartbeat — dead-man switch for cron jobs & AI agents MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.