incident-response

Incident response

Preflight — read first. If you cannot see any uptimerobot:* MCP tools in your tool list, invoke the uptimerobot:setup skill before doing anything else. Do not tell the user the MCP is misconfigured — setup's Step 0 detects the common case (server connected, tools loaded after session start) and resolves it without re-keying.

The full loop a user runs when something's on fire:

1. Find what's down (list-monitors with DOWN filter).
2. Pull incident details for the worst offenders (get-incident-details).
3. Optionally silence flapping monitors while the underlying issue is being fixed (update-monitor-status → PAUSED).
4. Log findings as you go with incident comments (requires the incident-comments plan feature).
5. After the fix, verify recovery with get-monitor-stats and/or get-response-times.

Use this when the user says "what's down?", "is production still broken?", "triage the alerts", or "show me the outage".

Step 1 — Find what's down

{ "filter": ["DOWN"], "limit": 50 }

Paginate until hasMore: false. Group the results by tag or friendly-name prefix before reporting — the user typically cares "what system is down", not "which individual checks are failing".

Also surface NOT_STARTED monitors on request — they're not actively monitored but show up in downtime reports.

Active-only view

To exclude paused and unstarted:

{ "filter": ["DOWN"], "limit": 50 }

(DOWN by itself excludes PAUSED / NOT_STARTED automatically.)

Step 2 — Pull recent incidents

For each down monitor that the user wants to dig into:

{ "monitorId": 800123456, "timeRange": "24h", "limit": 5 }

Returns a list of incidents (active and resolved). Note incidentId is a string.

Lead with the active (unresolved) incident, then show recently-resolved ones as flap history.

Step 3 — Diagnose one incident

{ "incidentId": "inc_abcdef1234567890" }

Returns:

• Per-checker probe results (location, IP, HTTP status, error kind, response body snippet).
• Traceroute hops where available.
• Start time, duration, and root-cause category if assigned.