get_heartbeat_status — heartbeat monitor MCP Tool Read-only
get_heartbeat_status
(get heartbeat status) is one of 7 tools on the
heartbeat monitor
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_heartbeat_status from your client
- Claude Code heartbeat monitor get_heartbeat_status run in your project directory
- Claude Desktop heartbeat monitor get_heartbeat_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor heartbeat monitor get_heartbeat_status ~/.cursor/mcp.json
- VS Code heartbeat monitor get_heartbeat_status .vscode/mcp.json
- Zed heartbeat monitor get_heartbeat_status ~/.config/zed/settings.json
- Windsurf heartbeat monitor get_heartbeat_status ~/.codeium/windsurf/mcp_config.json
- Cline heartbeat monitor get_heartbeat_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI heartbeat monitor get_heartbeat_status ~/.gemini/settings.json
- Grok heartbeat monitor get_heartbeat_status .mcp.json (in your project root)
- ChatGPT heartbeat monitor get_heartbeat_status Settings → Connectors → Advanced → Developer mode
- Claude.ai heartbeat monitor get_heartbeat_status Settings → Connectors → Add custom connector
- LangChain heartbeat monitor get_heartbeat_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http heartbeat-monitor https://cronping.cronping-oren.workers.dev/mcpOther 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.