Menu
Create a PING monitor that sends ICMP echo requests to a hostname or IP and alerts on packet loss / timeout.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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 | create-ping-monitor |
| description | Create a PING monitor that sends ICMP echo requests to a hostname or IP and alerts on packet loss / timeout. |
| tags | ["monitoring","ping","icmp","create","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.
Use when the user wants basic network reachability for a host. PING does not care about HTTP status or content — it just checks whether the host responds to ICMP within the timeout.
Tool: create-monitor
Required params: friendlyName, type: "PING", url (hostname or IP, no scheme).
{
"friendlyName": "Office gateway",
"type": "PING",
"url": "gw.example.com"
}
IP addresses work too:
{
"friendlyName": "VPN endpoint",
"type": "PING",
"url": "203.0.113.42"
}
interval, timeout, responseTimeThreshold, assignedAlertContacts, tagNames, maintenanceWindowsIds — same as HTTP.config.ipVersion — force IPv4 or IPv6. Defaults to auto.{
"friendlyName": "Public DNS v6",
"type": "PING",
"url": "2001:4860:4860::8888",
"config": { "ipVersion": "IPv6" },
"interval": 120
}
https://host.example.com — PING requires a bare hostname or IP. Strip the scheme and path.PORT monitor on a known open TCP port instead.Call get-monitor-details to confirm.
create-port-monitor — when ICMP is blocked but a TCP port is open.create-http-monitor — when the user has an HTTP(S) URL, not a bare host.