All-in-one monitoring for uptime, servers, incidents & status pages. Manage it all from AI chat.
Scored across 25 tools
Most tools have distinct resource+action targets, but retrieval tools overlap: list_monitors, read_monitor_status, and read_uptime_statistics all surface monitor health data, while read_incidents, list_recent_outages, and get_incident_details cover incident history with subtle scope differences. Descriptions help, but an agent could still hesitate between the read/list/get variants.
All tool names use snake_case with a verb_noun structure, which is predictable. The main inconsistency is the mix of retrieval verbs (get_, list_, read_) for similar operations, but this is a minor deviation rather than a chaotic pattern.
Twenty-five tools is heavy for this server and includes several closely related read/status operations. The breadth across monitors, incidents, servers, alerts, and status pages justifies many tools, but the surface feels somewhat inflated and could be consolidated.
Monitor lifecycle coverage is strong (create, update, delete, pause, resume, search, test), and incident handling includes acknowledge/resolve. However, notification channels only support listing/reading/testing with no create/update/delete, and status pages can be listed/updated but not created or deleted, leaving notable configuration gaps.
Marks an open incident as acknowledged and attaches an AI diagnostic note. Use this tool when you have reviewed an active incident and want to let the team know it is being investigated.
Note: This tool does not resolve the incident, it only acknowledges it.
Inputs: id, note, incident_id.
Creates a new monitor inside Monitor Hub.
Supports: • HTTP • HTTPS • API • Ping • TCP Port • Keyword Monitoring
Use this tool whenever a user wants to monitor a website, API, server, endpoint, IP address or service.
Returns the newly created monitor and its initial monitoring status.
Inputs: name (required), url, body, type, +6 more.
Permanently removes monitoring and deletes its historical metrics.
Use only when the user explicitly requests the deletion of a monitor, as this action is irreversible and deletes all associated monitoring history and data.
Inputs: id, monitor_id.
Returns incident timeline, outage duration, recovery time, failure reason, affected monitor, and timestamps.
Useful when Claude needs to investigate the root cause of an outage or read historical logs for a specific downtime event.
Inputs: id (required).
Retrieves full diagnostic configuration, headers, assertion settings, and last check time for a specific monitor.
Inputs: monitor_id (required).
Returns historical uptime events, incidents, and outages for a specific monitor ID.
Useful for checking the long-term reliability of a specific website or server over time.
Inputs: id (required), limit.
Fetches historical CPU %, RAM %, Disk %, and Network telemetry metrics for a server agent over a specified time window.
Inputs: agent_id (required), hours.
Lists all HTTP, TCP, Ping, and Keyword monitors for the user along with current status and uptime stats.
Inputs: status, category.
Lists configured alert webhooks (Slack, Discord, Telegram, Email) and alert trigger settings with sensitive tokens redacted.
Inputs: no named parameters.
Summarizes downtime events over a specified number of days along with outage duration in minutes and root cause explanations.
Inputs: days.
Lists user public status page configurations and public URLs.
Inputs: no named parameters.
Pauses uptime checking for a specified monitor ID.
Use this tool when a user explicitly requests to stop monitoring a website temporarily (e.g. during maintenance).
Inputs: id, monitor_id.
Fetches recent alert log entries and delivery notifications across email, Slack, Discord, and Telegram channels.
Inputs: limit.
Retrieves active and recent outage incidents including start time, resolution time, and AI-generated root cause analysis.
Inputs: limit.
Provides a high-level health overview (total count, up count, down count, warning count, overall uptime percentage, average response time).
Inputs: no named parameters.
Lists connected physical/virtual server agents, hostnames, OS types, public/private IPs, and dynamic heartbeat status (up, down, pending).
Inputs: status.
Calculates 24-hour uptime SLA percentages and average latency statistics across all monitors.
Inputs: no named parameters.
Marks an ongoing incident as resolved and updates root cause analysis details.
Use this tool when you have diagnosed an incident and want to close it, specifying what steps were taken to fix the issue.
Inputs: id, root_cause, incident_id.
Resolves an active warning sign on a monitored server agent.
Closes open warning incidents for the server, restores the agent status to "up" (operational), and clears firing threshold alarms.
Use this tool when you have diagnosed high CPU, RAM, or disk warnings and resolved the underlying server load.
Inputs: id, agent_id, server_id.
Resumes active uptime monitoring for a paused monitor ID.
Use this tool when a user explicitly requests to resume monitoring a website or API.
Inputs: id, monitor_id.
Searches monitors by target URL, keyword, or name.
Inputs: query (required).
Runs an instant live HTTP/ping probe test against any website or API URL.
Measures exact response time (latency), HTTP status code, response headers, and response snippet without creating a monitor.
Use this tool to verify endpoint reachability, test latency, check SSL/TLS responses, or diagnose an ongoing outage.
Inputs: url, body, method, target, +1 more.
Triggers a synthetic test alert to verify notification channels (email, webhooks, Slack, Discord).
Use this tool when a user wants to test if their alerting setup is working correctly.
Inputs: message, monitor_id.
Updates configuration for an existing monitor (name, target URL, interval, HTTP method, headers, expected status code).
Use this tool when a user wants to edit or reconfigure a monitor.
Inputs: id, url, body, name, +7 more.
Updates public status page configuration and slug for the user workspace.
Use this tool when a user wants to rename or update their public status page URL.
Inputs: slug (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Manage uptime monitors and incidents and search logs, metrics and traces from an AI assistant.
Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.
Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.
Uptime monitoring from your AI assistant: what is down, Incidents, and your Monitors.
Add one secure layer between your agents and this server.
