Menu
Create a DNS monitor that resolves records for a domain and alerts when they change or the DNS server does not respond.
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-dns-monitor |
| description | Create a DNS monitor that resolves records for a domain and alerts when they change or the DNS server does not respond. |
| tags | ["monitoring","dns","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 confirm a DNS server is answering queries for a domain and/or that specific record values (A, AAAA, MX, TXT, NS, CNAME, etc.) haven't drifted from the expected set.
Tool: create-monitor
Required params: friendlyName, type: "DNS", url (domain, no scheme).
{
"friendlyName": "example.com DNS",
"type": "DNS",
"url": "example.com"
}
port — DNS server port. Defaults to 53 if omitted.config.dnsRecords — object mapping record type to expected values. The monitor alerts when live values diverge.interval, timeout, assignedAlertContacts, tagNames, maintenanceWindowsIds.{
"friendlyName": "example.com records",
"type": "DNS",
"url": "example.com",
"config": {
"dnsRecords": {
"A": ["93.184.216.34"],
"MX": ["0 mail.example.com."]
}
},
"interval": 300,
"assignedAlertContacts": [
{ "alertContactId": "10", "threshold": 0, "recurrence": 0 }
]
}
url as https://example.com — DNS monitors take a bare domain.port without understanding that it targets a DNS server listening on that port (not a monitored service port). Leave it out unless the user explicitly runs DNS on a custom port.HTTP in addition for that.Call get-monitor-details to confirm stored records and port.
create-http-monitor — to also check the service behind the DNS name.update-monitor — retune interval, alert contacts, and tags on an existing DNS monitor. (Note: dnsRecords are set at creation and changing them requires creating a new monitor.)