ai

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.

Create a free UptimeRobot HTTPS uptime monitor for someone using ONLY their email, no UptimeRobot account, no API key, and no MCP/OAuth. The agent calls an unauthenticated proof-of-work-gated API; the owner confirms with one click in an activation email. Use when a user wants monitoring but is not signed in to UptimeRobot and has no API key, the zero-setup path.

Conventions and gotchas for every UptimeRobot MCP tool call — monitor types, URL formats, HEARTBEAT URL handling, discovery-before-writes, pagination, time ranges, error codes, and output style. Use whenever you call any uptimerobot:* tool.

Handle UptimeRobot MCP errors — codes, meanings, retry policy, and user-facing recovery suggestions.

List monitors, fetch details, and pause or resume monitors in UptimeRobot.

Connect and authenticate the UptimeRobot MCP server (OAuth via mcp-remote), OR diagnose why `uptimerobot:*` MCP tools aren't visible in the current session. Invoke this skill any time you cannot see UptimeRobot tools, before telling the user the MCP is misconfigured — Step 0 detects the most common case (server already connected, tools loaded after session start) and resolves it without re-authenticating. Also invoke on `-31001` auth errors or first-time setup.

Create an API monitor that calls an HTTP endpoint and runs up to five JSON/header assertions combined with AND/OR logic; alerts when assertions fail.

Create a DNS monitor that resolves records for a domain and alerts when they change or the DNS server does not respond.

Create a HEARTBEAT monitor (cron/job monitor) that expects the target to ping a generated URL on a schedule; alerts when expected pings stop arriving.

Create an HTTP monitor in UptimeRobot to check that a URL returns a successful response on an interval.

Create a KEYWORD monitor that fetches a URL and alerts when a given keyword appears (or is missing) in the response body.

Create a PING monitor that sends ICMP echo requests to a hostname or IP and alerts on packet loss / timeout.

Create a PORT monitor that opens a TCP connection to a host:port and alerts when the port is not accepting connections.

Create a UDP monitor that sends a UDP packet to a host:port and optionally checks the response keyword or packet-loss threshold.

List downtime incidents and fetch per-incident checker locations, IPs, logs, and traceroute data.

List the alert-contact integrations configured on the UptimeRobot account so you can attach them to new or existing monitors.

Generate a one-shot health snapshot — monitor counts by state, which are currently down, recent incident count, and total downtime — useful as a daily brief or ad-hoc check.

Generate a per-monitor SLA report for a time range — uptime percentage, total downtime, and incident count per monitor — formatted as Markdown for sharing in Confluence, Slack, or post-mortem docs.

Query aggregated monitor statistics (up/down/paused counts, uptime percentage) and per-monitor response-time time series.