create-udp-monitor

Create a UDP monitor

Preflight — read first. If you cannot see any uptimerobot:* MCP tools in your tool list, invoke the uptimerobot:setup skill 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).

Minimal call

{
  "friendlyName": "Game server lobby",
  "type": "UDP",
  "url": "lobby.example.com",
  "port": 27015
}

Common optional params

• 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.

Example with payload and keyword

{
  "friendlyName": "Custom UDP health",
  "type": "UDP",
  "url": "udp.example.com",
  "port": 9999,
  "config": {
    "udp": {
      "payload": "PING",
      "packetLossThreshold": 20
    }
  },
  "keywordValue": "PONG",
  "timeout": 5,
  "interval": 120
}

Common mistakes

• Using UDP for a TCP service (HTTP, databases, SSH). Use PORT.
• Setting keywordValue when the service does not echo data. You'll get false downtime.
• Forgetting port — UDP requires an explicit port.
• Assuming NAT'd or stateful-firewalled services will respond. UDP has no connection; many networks silently drop packets.

After creation