Okokumo
MCP server by okokumo · mcp
Okokumo monitors infrastructure. A check is one monitor, of one type: - http: requests url every interval_seconds and evaluates its assertions. - heartbeat: waits for the customer's own job to call its ping_url; down when silent longer than interval_seconds + grace_seconds. - cron: a heartbeat whose deadline follows cron_expression (5 fields) evaluated in cron_timezone (IANA zone, default UTC), plus grace_seconds. - tls: certificate validity and expiry of an https:// url. domain: registration expiry of a domain name (url holds the bare domain). All durations are in SECONDS. A check goes down after failure_threshold consecutive failed executions (default 2); state is up, down or unknown (not checked yet). A paused check (enabled false) is not monitored and never alerts. Alerts go to the organization's alert channels. A check with an empty channel list alerts EVERY channel of the organization (default routing); set_check_channels narrows it. The status page lists components and incident…
Endpoint: https://app.okokumo.com/mcp
Verification: observed. Source: crawl.
Capabilities (18)
- create_check
- create_incident
- get_account
- get_check
- get_check_channels
- get_check_stats
- get_status_page
- list_channels
- list_check_alerts
- list_check_transitions
- list_checks
- list_incidents
- pause_check
- post_incident_update
- resume_check
- set_check_channels
- update_check
- update_incident