get_status — Heartbeat — dead-man switch for cron jobs & AI agents MCP Tool Read-only
get_status
(get status) is one of 5 tools on the
Heartbeat — dead-man switch for cron jobs & AI agents
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_status from your client
- Claude Code Heartbeat — dead-man switch for cron jobs & AI agents get_status run in your project directory
- Claude Desktop Heartbeat — dead-man switch for cron jobs & AI agents get_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Heartbeat — dead-man switch for cron jobs & AI agents get_status ~/.cursor/mcp.json
- VS Code Heartbeat — dead-man switch for cron jobs & AI agents get_status .vscode/mcp.json
- Zed Heartbeat — dead-man switch for cron jobs & AI agents get_status ~/.config/zed/settings.json
- Windsurf Heartbeat — dead-man switch for cron jobs & AI agents get_status ~/.codeium/windsurf/mcp_config.json
- Cline Heartbeat — dead-man switch for cron jobs & AI agents get_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Heartbeat — dead-man switch for cron jobs & AI agents get_status ~/.gemini/settings.json
- Grok Heartbeat — dead-man switch for cron jobs & AI agents get_status .mcp.json (in your project root)
- ChatGPT Heartbeat — dead-man switch for cron jobs & AI agents get_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Heartbeat — dead-man switch for cron jobs & AI agents get_status Settings → Connectors → Add custom connector
- LangChain Heartbeat — dead-man switch for cron jobs & AI agents get_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http golemreach-heartbeat https://golemreach.com/heartbeat/mcp
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.