Okokumo

com.okokumo/okokumoVersion 0.1.85

Uptime, cron/heartbeat, TLS and domain expiry monitoring, EU-hosted. Same access as the REST API.

Status

Responds146 msNov 14, 2026, 14:08 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:08 UTC
Latency: 146 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: EU hosting detected (detected, not a legal statement)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://app.okokumo.com/mcpResponds146 msNov 14, 2026, 14:08 UTC

No sign-in

Claude Code

claude mcp add --transport http okokumo https://app.okokumo.com/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: okokumo
Remote MCP server URL: https://app.okokumo.com/mcp

Cursor

{
  "mcpServers": {
    "okokumo": {
      "url": "https://app.okokumo.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"okokumo","type":"http","url":"https://app.okokumo.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

18 tools

Tools of Okokumo
	Description		Read-only	Idempotent	Open world
`create_check`Create 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 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.	No	No	No	No
`create_incident`Declare 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.	Declare 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.	No	No	No	No
`get_account`The organization, user and role this API key acts as.	The organization, user and role this API key acts as.	Not declared	Yes	Yes	No
`get_check`One check with its current state and settings.	One check with its current state and settings.	Not declared	Yes	Yes	No
`get_check_channels`The alert channel ids a check is restricted to. An empty list means the default: EVERY channel of the organization alerts for this check.	The alert channel ids a check is restricted to. An empty list means the default: EVERY channel of the organization alerts for this check.	Not declared	Yes	Yes	No
`get_check_stats`Latency 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.	Latency 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.	Not declared	Yes	Yes	No
`get_status_page`The organization's public status page: its address, whether it is published, and its components (the component ids incidents refer to).	The organization's public status page: its address, whether it is published, and its components (the component ids incidents refer to).	Not declared	Yes	Yes	No
`list_channels`The 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.	The 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.	Not declared	Yes	Yes	No
`list_check_alerts`The last 20 alert deliveries for a check, newest first: which channel, sent or failed, and why. Use it to answer "was I alerted?".	The last 20 alert deliveries for a check, newest first: which channel, sent or failed, and why. Use it to answer "was I alerted?".	Not declared	Yes	Yes	No
`list_check_transitions`The 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.	The 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.	Not declared	Yes	Yes	No
`list_checks`List 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 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.	Not declared	Yes	Yes	No
`list_incidents`Every incident of the status page, drafts included, newest first, each with its timeline of updates.	Every incident of the status page, drafts included, newest first, each with its timeline of updates.	Not declared	Yes	Yes	No
`pause_check`Pause 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.	Pause 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.	Yes	No	Yes	No
`post_incident_update`Add an entry to an incident's timeline, optionally moving its status (e.g. to resolved). Owners and admins only.	Add an entry to an incident's timeline, optionally moving its status (e.g. to resolved). Owners and admins only.	No	No	No	No
`resume_check`Resume a paused check. Counts against the plan's check limit again, so it is refused when the organization is at its limit.	Resume a paused check. Counts against the plan's check limit again, so it is refused when the organization is at its limit.	No	No	Yes	No
`set_check_channels`Restrict 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.	Restrict 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.	Yes	No	Yes	No
`update_check`Change 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.	Change 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.	Yes	No	Yes	No
`update_incident`Edit 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.	Edit 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.	Yes	No	Yes	No

Details

Registry status: Active
Published: Oct 19, 2026
Updated: Oct 19, 2026
Website: https://okokumo.com/mcp?mtm_campaign=mcp-registry⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): Cloud and infrastructureSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing