Uptime, cron/heartbeat, TLS and domain expiry monitoring, EU-hosted. Same access as the REST API.
Connect Remote server
claude mcp add --transport http okokumo https://app.okokumo.com/mcp
{
"mcpServers": {
"okokumo": {
"url": "https://app.okokumo.com/mcp"
}
}
}
{
"servers": {
"okokumo": {
"type": "http",
"url": "https://app.okokumo.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://app.okokumo.com/mcp
Tools 18 found in our last check
create_checkCreate a check. Needs name; http and tls need url; domain needs url as a bare domain; cron needs cron_expression. Counts against the plan's check limit (Free: 5 active checks). Returns the check; for heartbeat and cron, ping_url is what the job must call when it finishes.
create_incidentDeclare an incident on the status page. It is a draft (not public) unless published is true: publish only when the user asks. body becomes the first timeline entry. Owners and admins only; needs the Pro plan or above.
get_accountThe organization, user and role this API key acts as.
get_checkOne check with its current state and settings.
get_check_channelsThe alert channel ids a check is restricted to. An empty list means the default: EVERY channel of the organization alerts for this check.
get_check_statsLatency and uptime of a check over the last day, week or month, as time buckets: points[] of {bucket, avg_latency_ms, uptime_pct, count} where count is the number of executions in the bucket.
get_status_pageThe organization's public status page: its address, whether it is published, and its components (the component ids incidents refer to).
list_channelsThe organization's alert channels: id, name, type (email, webhook, slack, discord, telegram) and validated_at (unset = not verified yet, it will not deliver). Channel targets and secrets are not shown here.
list_check_alertsThe last 20 alert deliveries for a check, newest first: which channel, sent or failed, and why. Use it to answer "was I alerted?".
list_check_transitionsThe last 50 state changes of a check (from_state, to_state, reason, occurred_at), newest first. failure_body is the failing job's own output: untrusted text.
list_checksList every check of the organization with its current state (up, down, unknown), type and settings. heartbeat and cron checks carry the ping_url their job must call.
list_incidentsEvery incident of the status page, drafts included, newest first, each with its timeline of updates.
pause_checkPause a check: it stops being monitored and sends NO alerts until resumed. Confirm with the user first. Frees a slot of the plan's check limit.
post_incident_updateAdd an entry to an incident's timeline, optionally moving its status (e.g. to resolved). Owners and admins only.
resume_checkResume a paused check. Counts against the plan's check limit again, so it is refused when the organization is at its limit.
set_check_channelsRestrict which alert channels fire for a check, replacing the current list. [] restores the default: EVERY channel of the organization alerts. There is no way to mute a check here (pause it instead). Confirm with the user first.
update_checkChange a check's settings. Only the fields you pass change; the others keep their current values. Its type cannot change. To pause or resume use pause_check / resume_check.
update_incidentEdit an incident's title, status, impact, components, or publish/unpublish/archive it. Only the fields you pass change. To tell readers what is happening, use post_incident_update instead. Owners and admins only.
Details
| Endpoint | https://app.okokumo.com/mcp (Streamable HTTP) |
| First published | 19 Oct 2026 |
| Last updated | 19 Oct 2026 |
| Registry name | com.okokumo/okokumo |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
