Menu
Create a PORT monitor that opens a TCP connection to a host:port and alerts when the port is not accepting connections.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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-port-monitor |
| description | Create a PORT monitor that opens a TCP connection to a host:port and alerts when the port is not accepting connections. |
| tags | ["monitoring","port","tcp","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 to check that a specific TCP port is open on a host — databases, SSH, SMTP, custom services, etc.
Tool: create-monitor
Required params: friendlyName, type: "PORT", url (host or IP, no scheme), port (1–65535).
{
"friendlyName": "Postgres primary",
"type": "PORT",
"url": "db.example.com",
"port": 5432
}
timeout — how long to wait for the TCP handshake (1–60s).interval, responseTimeThreshold, assignedAlertContacts, tagNames, maintenanceWindowsIds.config.ipVersion — IPv4 or IPv6.SMTP over IPv4:
{
"friendlyName": "Mail relay",
"type": "PORT",
"url": "smtp.example.com",
"port": 25,
"timeout": 15,
"interval": 300
}
SSH with alert contacts:
{
"friendlyName": "Bastion SSH",
"type": "PORT",
"url": "bastion.example.com",
"port": 22,
"assignedAlertContacts": [
{ "alertContactId": "10", "threshold": 0, "recurrence": 0 }
],
"tagNames": ["infra", "security"]
}
https://host:443 as url. Split into url: "host" and port: 443.port as a string. It must be an integer 1–65535.port outside the valid range (e.g. 0 or 70000). The server rejects with -29001.HTTP or KEYWORD.Call get-monitor-details to confirm host + port were stored.
create-udp-monitor — for UDP services (DNS, NTP, QUIC, game servers).create-ping-monitor — for reachability without a specific port.