Terminal
Terminal/Skill
Create a UDP monitor that sends a UDP packet to a host:port and optionally checks the response keyword or packet-loss threshold.
By UptimeRobot
Works with
npx skills add uptimerobot/ai --skill create-udp-monitorPreflight — 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 for UDP-based services — DNS (as a generic UDP check, not the DNS record monitor), NTP, QUIC, game servers, custom UDP endpoints. For TCP, use PORT instead.
Tool: create-monitor
Required params: friendlyName, type: "UDP", url (host or IP, no scheme), port (1–65535).
{
"friendlyName": "Game server lobby",
"type": "UDP",
"url": "lobby.example.com",
"port": 27015
}
config.udp.payload — UDP payload to send. Some services only respond to specific probe bytes.config.udp.packetLossThreshold — number. Packet-loss percentage above which the monitor is considered down.keywordValue — expected substring in the response payload. Leave off if the service echoes anything or you only care about reachability.config.ipVersion — IPv4 / IPv6.timeout, interval, responseTimeThreshold, assignedAlertContacts, tagNames, maintenanceWindowsIds.{
"friendlyName": "Custom UDP health",
"type": "UDP",
"url": "udp.example.com",
"port": 9999,
"config": {
"udp": {
"payload": "PING",
"packetLossThreshold": 20
}
},
"keywordValue": "PONG",
"timeout": 5,
"interval": 120
}
PORT.keywordValue when the service does not echo data. You'll get false downtime.port — UDP requires an explicit port.Call get-monitor-details to confirm stored port, config.udp, and any keywordValue.
create-port-monitor — for TCP.create-ping-monitor — when you only need reachability.