mocop
Browse · Docs · Guide · Analyze

uptimex

MCP server by UptimeX · mcp

UptimeX watches the uptime of URLs. Use these tools to manage the user's monitors for them. To create a monitor you need at least a url. Optional fields: name (defaults to the host), method (HEAD by default; auto-switches to GET when content_rules are set), interval_sec (plan minimum: 300s free / 60s pro), expect_status (exact code; omit for any 2xx/3xx), content_rules (up to 4 body checks), request_headers (up to 4, for auth), request_body (write methods only — checks run on a schedule, so point writes at test data or a dedicated test route, never real customer writes), fail_threshold, recover_threshold. Fill missing details from the conversation, the user's memory/context, or by asking one or two concise questions — prefer sensible defaults over interrogating. A bare URL is enough to start. Call list_monitors first to avoid duplicates. Briefly confirm what you'll add before creating, and report the resulting status afterward. You can also update_monitor (partial edits, incl. enabl…

Endpoint: https://api.uptimex.co/mcp

Verification: observed. Source: crawl.

Capabilities (6)

  • list_monitors
  • create_monitor
  • update_monitor
  • delete_monitor
  • test_monitor
  • register-monitor
About · Contact · Privacy