Integration

StatusCake integration

StatusCake is a website and server monitoring service. Create, update, pause and delete uptime checks (HTTP, HEAD, TCP, DNS, SMTP, SSH, PING), heartbeat (push) checks, pagespeed checks and SSL certificate checks; read a check's run history, up and down periods and alerts; manage the contact groups that receive alerts and schedule maintenance windows that silence them; list the monitoring locations and their IPs. Every route of the public v1 API is exposed. Authentication is an API token from the StatusCake account panel, sent as a Bearer token in the Authorization header. Free accounts are limited to 60 requests per minute, and every account to 5 per second.

Connect StatusCake How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in StatusCake.Built from the 36 StatusCake tools below, on the connection you add once.

What you can do with StatusCake

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Contact group, 5 operations

create_contact_groupCreate contact groupPOSTCreates a contact group, the set of people and integrations StatusCake alerts when a check attached to it goes down. Returns the new group id in data.new_id.
delete_contact_groupDelete contact groupDELETEDeletes a contact group by id. Answers with no content on success.
get_contact_groupGet contact groupGETReturns one contact group by id: its name, email addresses, mobile numbers, integration ids and ping URL.
list_contact_groupsList contact groupsGETLists the contact groups of the account, one page at a time: each group has its id, name, email addresses, mobile numbers, integration ids and ping URL. Contact group ids are what the contact_groups field of every check expects.
update_contact_groupUpdate contact groupPUTUpdates a contact group: only the fields sent are changed. A list field sent replaces the whole list. Answers with no content on success.

Heartbeat check, 5 operations

create_heartbeat_checkCreate heartbeat checkPOSTCreates a heartbeat (push) check: StatusCake gives it a unique URL that your job or server must call at least once every period seconds, otherwise the check goes down and its contact groups are alerted. Returns the new check id in data.new_id.
delete_heartbeat_checkDelete heartbeat checkDELETEDeletes a heartbeat check by id. Answers with no content on success.
get_heartbeat_checkGet heartbeat checkGETReturns one heartbeat check by id, including the url to ping, its period, status (up or down), uptime percentage, tags and contact groups.
list_heartbeat_checksList heartbeat checksGETLists the heartbeat checks of the account, optionally filtered by status (up or down) or tags. A heartbeat check expects your system to ping its URL at least once every period seconds and is considered down otherwise.
update_heartbeat_checkUpdate heartbeat checkPUTUpdates a heartbeat check: only the fields sent are changed (set paused to true to pause it). Answers with no content on success.

Maintenance window, 5 operations

create_maintenance_windowCreate maintenance windowPOSTSchedules a maintenance window pausing alerts for the uptime checks in tests or matching tags (at least one of the two needed). start_at and end_at are local time in timezone; repeat_interval makes it recur. Returns the new window id in data.new_id.
delete_maintenance_windowDelete maintenance windowDELETEDeletes a maintenance window by id. Answers with no content on success.
get_maintenance_windowGet maintenance windowGETReturns one maintenance window by id: name, start and end, timezone, repeat interval, state, and the checks and tags it covers.
list_maintenance_windowsList maintenance windowsGETLists the maintenance windows of the account, optionally filtered by state (active, paused or pending). During a window, alerts are not sent for the uptime checks it covers. Only works on accounts that use the newer version of maintenance windows.
update_maintenance_windowUpdate maintenance windowPUTUpdates a maintenance window: only the fields sent are changed. Answers with no content on success.

Pagespeed check, 5 operations

create_pagespeed_checkCreate pagespeed checkPOSTCreates a pagespeed check that loads website_url from one region every check_rate seconds and alerts when the page gets slower, bigger or smaller than the thresholds you set. Returns the new check id in data.new_id.
delete_pagespeed_checkDelete pagespeed checkDELETEDeletes a pagespeed check by id. Answers with no content on success.
get_pagespeed_checkGet pagespeed checkGETReturns one pagespeed check by id, with its thresholds, location and latest stats (load time, file size, request count, latest issue).
list_pagespeed_checksList pagespeed checksGETLists the pagespeed checks of the account, one page at a time, each with its latest load time, page size and request count.
update_pagespeed_checkUpdate pagespeed checkPUTUpdates a pagespeed check: only the fields sent are changed. Answers with no content on success.

Ssl check, 5 operations

create_ssl_checkCreate ssl checkPOSTCreates an SSL certificate check on an https:// URL, inspected every check_rate seconds, alerting at the three day counts in alert_at before expiry and optionally on broken certificates or mixed content. Returns the new check id in data.new_id.
delete_ssl_checkDelete ssl checkDELETEDeletes an SSL check by id. Answers with no content on success.
get_ssl_checkGet ssl checkGETReturns one SSL check by id: certificate status and score, cipher, issuer, valid_from and valid_until dates, mixed content found, and the alert settings.
list_ssl_checksList ssl checksGETLists the SSL certificate checks of the account, one page at a time, each with the certificate status, expiry date (valid_until), issuer and scores.
update_ssl_checkUpdate ssl checkPUTUpdates an SSL check: only the fields sent are changed. Answers with no content on success.

Uptime check, 5 operations

create_uptime_checkCreate uptime checkPOSTCreates an uptime check of type HTTP, HEAD, TCP, DNS, SMTP, SSH or PING on website_url, run every check_rate seconds from the chosen regions, alerting its contact groups when it goes down. Returns the new check id in data.new_id.
delete_uptime_checkDelete uptime checkDELETEDeletes an uptime check by id. Answers with no content on success.
get_uptime_checkGet uptime checkGETReturns one uptime check by id with its full configuration, current status, uptime percentage, last test time and the servers it runs from.
list_uptime_checksList uptime checksGETLists the uptime checks of the account, optionally filtered by status (up or down) or tags, with each check's type, URL, check rate, status and uptime percentage.
update_uptime_checkUpdate uptime checkPUTUpdates an uptime check: only the fields sent are changed (set paused to true to pause it). The check type cannot be changed. Answers with no content on success.

Pagespeed location, 1 operation

list_pagespeed_locationsList pagespeed locationsGETLists the servers that run pagespeed checks, with their region, region code, status and IP addresses. A region code from here is the value create_pagespeed_check expects in region.

Pagespeed result, 1 operation

list_pagespeed_check_historyList pagespeed check historyGETReturns the recent runs of a pagespeed check: for each run its time, load time, page size, request count, throttling and a link to the HAR file. Use before and after (UNIX timestamps) to page through older results; links.next points at the next page.

Uptime alert, 1 operation

list_uptime_check_alertsList uptime check alertsGETReturns the alerts an uptime check has triggered: each with its time, status (up or down) and the status code seen. Use before and after (UNIX timestamps) to page; links.next points at the next page.

Uptime location, 1 operation

list_uptime_locationsList uptime locationsGETLists the servers that run uptime checks, with their region, region code, status and IP addresses. Region codes from here are the values create_uptime_check expects in regions[]; the IPs are the ones to allow through a firewall.

Uptime period, 1 operation

list_uptime_check_periodsList uptime check periodsGETReturns the up and down periods of an uptime check: when each period started and ended, its duration and status. Useful to compute downtime. Use before and after (UNIX timestamps) to page; links.next points at the next page.

Uptime result, 1 operation

list_uptime_check_historyList uptime check historyGETReturns the recent runs of an uptime check: for each run its time, test location, response time in milliseconds and HTTP status code. Use before and after (UNIX timestamps) to page; links.next points at the next page.

Use StatusCake from Claude Code, Cursor or Codex

Connect StatusCake in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its StatusCake operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect StatusCake

Create your workspace
Sign up free. Nothing to install.
Connect StatusCake once
Add your StatusCake connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.