Set up uptime, SSL and heartbeat monitors, alert contacts and incidents for an All's Well team.
Scored across 11 tools
Most tools are clearly separated by resource and action: monitors, notification contacts, incidents, checks, and plan usage are distinct surfaces. The only minor overlap is between update-monitor and toggle-monitor, since both can affect monitor state, but the descriptions make toggle-monitor's pause/resume role clear.
All tool names use lowercase kebab-case with a predictable verb_noun pattern such as create-monitor, list-monitors, get-monitor, delete-monitor, and update-monitor. Compound nouns like notification-contact are handled consistently, and there are no mixed casing or verb-style deviations.
Eleven tools is well within the appropriate range for an uptime-monitoring server. The set covers monitor lifecycle, plan limits, incidents, recent checks, and alert contacts without excessive or redundant tools.
Core monitor CRUD and lifecycle operations are covered, including create, get, list, update, delete, toggle, and plan-limit checking. There are minor gaps around notification-contact lifecycle and incident management: contacts can be created and listed but not updated or deleted, and incidents are read-only.
Create an uptime monitor for the team. Call get-plan-usage first to confirm there is room and to find the shortest allowed interval. A heartbeat monitor returns the heartbeat_url your job must request after each run.
Inputs: name (required), type (required), check_interval_minutes (required), url, +12 more.
Create a notification contact (an alert destination). config holds the keys its type needs: {"email": "ops@example.com"} for email; {"webhook_url": "https://hooks.slack.com/..."} for slack or discord; {"url": "https://..."} for webhook; {"bot_token": "...", "chat_id": "-100123"} for telegram. Other keys are dropped.
Inputs: name (required), type (required), config (required), notify_on_down, +1 more.
Delete a monitor (soft delete; recoverable by an administrator).
Inputs: id (required).
Get one monitor by id, including status, SSL info, and 30-day uptime.
Inputs: id (required).
Return the team plan, monitor usage vs limit, and minimum check interval, so you avoid exceeding limits.
Inputs: no named parameters.
List recent incidents across the team monitors (open and resolved).
Inputs: no named parameters.
List all monitors for the current team with their current status.
Inputs: no named parameters.
List the team notification contacts (alert destinations) with their ids, so you can attach them to monitors.
Inputs: no named parameters.
List the most recent checks for a monitor (status, response time, error).
Inputs: monitor_id (required), limit.
Pause or resume a monitor (flips its active state).
Inputs: id (required).
Update a monitor. Only the fields you send change; send null to clear an optional field. The type cannot change. notification_contact_ids replaces the monitor's whole set of alert contacts.
Inputs: id (required), url, name, port, +12 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.
Uptime monitoring, status pages and on-call in one place. Create and tune monitors for HTTP, TCP, DNS, ping, TLS certificates, domain expiry, heartbeats and scripted browser logins. Run a check on demand, read uptime and response-time history, acknowledge and resolve incidents, post incident updates, schedule maintenance windows and edit public status pages. Read-only until you grant write access.
Uptime monitoring — monitors, incidents, heartbeats, maintenance windows, status page incidents
Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks.
Add one secure layer between your agents and this server.
