Menu
List downtime incidents and fetch per-incident checker locations, IPs, logs, and traceroute data.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Modify an existing UptimeRobot monitor — rename, change URL/interval, swap alert contacts, retag, tweak HTTP/keyword/API/heartbeat settings, and toggle SSL or domain reminders.
Choose between monitor groups and tags for organizing monitors — group membership is opaque and write-only over MCP, so tags are usually the better default.
Create and publish a public status page from monitors, groups, or tags, and manage announcements (incident, maintenance, info notices) on it.
Pause (or resume) many UptimeRobot monitors at once — by tag, search term, or state — around a deployment or maintenance window.
End-to-end incident workflow — find what's down, diagnose it, pause flapping monitors, and verify recovery.
Schedule one-off or recurring maintenance windows that suppress alerts for planned downtime, as an alternative to bulk-pause.
| name | incidents |
| description | List downtime incidents and fetch per-incident checker locations, IPs, logs, and traceroute data. |
| tags | ["incidents","downtime","logs","traceroute","uptimerobot"] |
Preflight — read first. If you cannot see any
uptimerobot:*MCP tools in your tool list, invoke theuptimerobot:setupskill 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.
Two tools:
list-incidents — paginated incidents across the account or for one monitor.get-incident-details — checker locations, IPs, logs, traceroute for one incident.{
"timeRange": "7d",
"limit": 25
}
Parameters:
timeRange — "24h" / "7d" / "30d" (1h–90d), or ISO 8601 interval "2024-01-01T00:00:00Z/2024-01-31T23:59:59Z". Defaults to "7d".monitorId — optional, restrict to one monitor.cursor, limit — pagination (follow the instructions field for the next call).{
"monitorId": 800123456,
"timeRange": "30d"
}
{
"timeRange": "2025-04-01T00:00:00Z/2025-04-15T23:59:59Z"
}
{ "incidentId": "inc_abcdef1234567890" }
Note: incidentId is a string, not a number.
Response includes:
Use this to answer "why did this go down?" — show the user the checker locations first, then the error types, then (if asked) the verbose logs.
incidentId. It's always a string.list-incidents is paginated. Loop with the cursor from instructions until hasMore: false.incidentIds. Always source them from list-incidents.stats — for aggregated downtime minutes across a time range.manage-monitors — to pause a flapping monitor after confirming incidents.