القائمة
Create a KEYWORD monitor that fetches a URL and alerts when a given keyword appears (or is missing) in the response body.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف 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-keyword-monitor |
| description | Create a KEYWORD monitor that fetches a URL and alerts when a given keyword appears (or is missing) in the response body. |
| tags | ["monitoring","keyword","content-check","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 cares not just that an endpoint returns a 200, but that a specific string is present (login page has "Sign in") or absent (homepage is not showing "502 Bad Gateway"). For structured JSON assertions, prefer create-api-monitor instead.
Tool: create-monitor
Required params: friendlyName, type: "KEYWORD", url (full URL), keywordValue, keywordType.
{
"friendlyName": "Login page shows Sign in",
"type": "KEYWORD",
"url": "https://app.example.com/login",
"keywordValue": "Sign in",
"keywordType": "ALERT_NOT_EXISTS"
}
keywordType:
ALERT_NOT_EXISTS — alert when the keyword disappears (expected content missing → down).ALERT_EXISTS — alert when the keyword appears (error string present → down).All HTTP-monitor params are supported: httpMethodType, authType, httpUsername, httpPassword, followRedirections, checkSSLErrors, timeout, interval, sslExpirationReminder, domainExpirationReminder, responseTimeThreshold, assignedAlertContacts, tagNames, maintenanceWindowsIds.
KEYWORD-specific:
keywordCaseType — 0 for case-sensitive (default), 1 for case-insensitive.{
"friendlyName": "Homepage not erroring",
"type": "KEYWORD",
"url": "https://www.example.com/",
"keywordValue": "Internal Server Error",
"keywordType": "ALERT_EXISTS",
"keywordCaseType": 1,
"interval": 60,
"assignedAlertContacts": [
{ "alertContactId": "10", "threshold": 0, "recurrence": 0 }
]
}
keywordType — it is required.keywordCaseType: 1 for insensitive.keywordValue longer than 500 chars is rejected.httpMethodType is HEAD, the keyword check will not work as expected.Call get-monitor-details to confirm keywordValue, keywordType, and keywordCaseType are stored correctly.
create-http-monitor — if only status code matters.create-api-monitor — for JSON/XML response assertions.