listHeartbeats
Get status check history for all monitors.
How to use it
listHeartbeats is exposed by the MCP Uptime Kuma MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the listHeartbeats tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
Install MCP Uptime Kuma
npx -p @davidfuchs/mcp-uptime-kuma mcp-uptime-kuma-get-jwt http://localhost:3001 admin mypasswordOther tools in MCP Uptime Kuma (27)
Filter by active (true) or inactive (false) monitors
Create a new notification channel.
Create a new tag that can be assigned to monitors.
Schedule a new maintenance window.
Create a new monitor (requires name and type at minimum).
Permanently delete a monitor and all its heartbeat history.
Permanently delete a notification channel.
Permanently delete a tag (removes it from all monitors).
Get status check history for a specific monitor.
List all scheduled maintenance windows.
Get detailed configuration for a specific monitor by ID.
Get a quick overview of all monitors with their current status. Supports filtering.
Get Uptime Kuma server settings.
Space-separated keywords for fuzzy matching against monitor pathNames
Get the full list of all monitors with configurations. Supports filtering.
Get all available monitor types supported by Uptime Kuma.
List all configured notification channels (Slack, Discord, email, webhooks, etc.).
List all configured status pages.
List all tags defined in Uptime Kuma.
Filter by maintenance mode status
Pause a monitor to stop performing checks.
Resume a paused monitor to restart checks.
(getMonitorSummary only): Heartbeat status ("0"=DOWN, "1"=UP, "2"=PENDING, "3"=MAINTENANCE)
Tag name and optional value, comma-separated (e.g., "production", "env=staging")
Monitor type(s), comma-separated (e.g., "http", "http,ping,dns")
Update an existing monitor's configuration.
Update an existing notification channel.