The Heartbeat — dead-man switch for cron jobs & AI agents MCP server,
connected in one click.
Dead-man switch monitors for cron & AI agents with dependency-cascade alerts. No account needed. Connect the official Heartbeat — dead-man switch for cron jobs & AI agents MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Add Heartbeat — dead-man switch for cron jobs & AI agents to your AI in one minute
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http heartbeat-dead-man-switch-for-cron-jobs-ai-agent https://golemreach.com/heartbeat/mcpRun in your terminal, then restart Claude Code.
Heartbeat — dead-man switch for cron jobs & AI agents · https://golemreach.com/heartbeat/mcp
What your AI can do with Heartbeat — dead-man switch for cron jobs & AI agents
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “create_heartbeat”: 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.”
“Use “ping_heartbeat”: Record one successful run for a monitor (same as GETting https://golemreach.com/heartbeat/ping/<key>). Call this every time your job runs. F.”
“Use “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 a.”
“Use “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.”
How secure is the Heartbeat — dead-man switch for cron jobs & AI agents MCP server?
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Heartbeat — dead-man switch for cron jobs & AI agents holds up.
Official endpoint
Operated by Heartbeat — dead-man switch for cron jobs & AI agents (golemreach.com) at its documented MCP endpoint — not a third-party mirror or community re-host.
No sign-in needed
This server only exposes public data — no account and no credentials are involved when you connect.
Scanned before it goes live
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
Watched for drift
If Heartbeat — dead-man switch for cron jobs & AI agents adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Connected in three steps
Connect your gate
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Pick Heartbeat — dead-man switch for cron jobs & AI agents
Choose Heartbeat — dead-man switch for cron jobs & AI agents in the gate directory. No sign-in needed.
Use it anywhere
Heartbeat — dead-man switch for cron jobs & AI agents's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
The actual tools Heartbeat — dead-man switch for cron jobs & AI agents exposes
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
create_heartbeat — 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
ping_heartbeat — Record one successful run for a monitor (same as GETting https://golemreach.com/heartbeat/ping/<key>). Call this every time your job runs. F
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 a
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
get_status — Full current state of one monitor: status, 30-day uptime %, schedule, last ping, alert config, recent event history and its public URLs. Loo
Who runs the Heartbeat — dead-man switch for cron jobs & AI agents MCP server?
The Heartbeat — dead-man switch for cron jobs & AI agents MCP server at a glance
https://golemreach.com/heartbeat/mcpQuestions, answered
Is there an official Heartbeat — dead-man switch for cron jobs & AI agents MCP server?
Yes — Heartbeat — dead-man switch for cron jobs & AI agents operates its own remote MCP server at golemreach.com. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
How do I connect Heartbeat — dead-man switch for cron jobs & AI agents to Claude or ChatGPT?
Add gate's gateway URL to your AI client once, then pick Heartbeat — dead-man switch for cron jobs & AI agents in the directory. No account or sign-in is needed. From then on, Heartbeat — dead-man switch for cron jobs & AI agents's tools are available in every client you've connected to gate.
Do I need to host anything?
No. Heartbeat — dead-man switch for cron jobs & AI agents runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
Is the Heartbeat — dead-man switch for cron jobs & AI agents MCP server safe to connect?
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Is it free?
Yes — you can get started with gate for free and connect Heartbeat — dead-man switch for cron jobs & AI agents in minutes. No credit card required.
Connect more than just Heartbeat — dead-man switch for cron jobs & AI agents
Every server below works through the same gateway URL — connect once, add tools anytime.
Squarespace DomainsDesignView →Set up Heartbeat — dead-man switch for cron jobs & AI agents in: Claude · Claude Code · ChatGPT · Cursor · VS Code
Give your AI Heartbeat — dead-man switch for cron jobs & AI agents — safely.
One URL. All MCPs. Full control. Free to start.
Get started free