StatusCake MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

StatusCake MCP by usefulapi is answering right now. Last checked 11 min ago. It exposes 21 tools. Last commit 10 Oct 2026.

Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks.

Uptime history 13 days of history

13 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

121 ms

Response time

average over 24h

Stars

last commit 10 Oct 2026

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day

7 Oct a tool changed version

30 Sep a tool changed version2 times that day

and 4 more, back to 30 September 2026

Nothing serious here today

Today is the operative word: we check StatusCake MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add statuscake --transport http https://statuscake.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "statuscake": {
      "url": "https://statuscake.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.statuscake]
url = "https://statuscake.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "statuscake": {
      "url": "https://statuscake.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "statuscake": {
      "url": "https://statuscake.usefulapi.io/mcp"
    }
  }
}

Available tools 21

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

statuscake

statuscake_create_heartbeat_check

Create a heartbeat (push) check for a cron job or worker: it goes down if StatusCake is not pinged within `period` seconds. Returns the new id as data.new_id; fetch it with statuscake_get_heartbeat_check to get the ping URL. StatusCake: POST /heartbeat.

statuscake_create_maintenance_window

Schedule a maintenance window that silences alerts for the given uptime checks (by id and/or tag). start_at/end_at are RFC3339; only the date and time are used and are read as local time in `timezone`. At least one of tests or tags is required. Only works on accounts using the newer maintenance-windows feature. StatusCake: POST /maintenance-windows.

statuscake_create_ssl_check

Start monitoring a site's SSL certificate for expiry and problems. Returns the new id as data.new_id. StatusCake: POST /ssl.

statuscake_create_uptime_check

Start monitoring a URL, host or IP. Returns the new check's id as data.new_id. Faster check rates and some regions depend on the plan. StatusCake: POST /uptime.

statuscake_get_heartbeat_check

Fetch one heartbeat check in full, including its ping URL, period, status and when it last received a ping. StatusCake: GET /heartbeat/{test_id}.

statuscake_get_maintenance_window

Fetch one maintenance window by id. StatusCake: GET /maintenance-windows/{window_id}.

statuscake_get_pagespeed_history

Past runs of one pagespeed check — load time (ms), file size (kb), request count, throttling and the saved HAR file location. StatusCake: GET /pagespeed/{test_id}/history.

statuscake_get_ssl_check

Fetch one SSL certificate check in full — expiry, issuer, cipher, scores, flags and any mixed-content resources found. StatusCake: GET /ssl/{test_id}.

statuscake_get_uptime_check

Fetch one uptime check in full — settings, current status, last test time, next location and the monitoring servers it runs on. StatusCake: GET /uptime/{test_id}.

statuscake_get_uptime_history

Individual test runs for one uptime check — when, from which location, the status code and the response time (ms). Newest first; follow links.next (or pass before) to page back. StatusCake: GET /uptime/{test_id}/history.

statuscake_get_uptime_periods

The up and down periods of one uptime check — when each started and ended and how long it lasted (ms). The direct answer to 'how long was it down?'. StatusCake: GET /uptime/{test_id}/periods.

statuscake_list_contact_groups

List contact groups — who gets alerted: email addresses, mobile numbers, integration ids and ping URL. Use their ids in a check's contact_groups. StatusCake: GET /contact-groups.

statuscake_list_heartbeat_checks

List heartbeat (push) checks — jobs that must ping a StatusCake URL within a period — with their status, period and ping URL. StatusCake: GET /heartbeat.

statuscake_list_maintenance_windows

List maintenance windows (scheduled alert silences) with their start/end, timezone, repeat interval, state and the checks or tags they cover. Only works on accounts using the newer maintenance-windows feature. StatusCake: GET /maintenance-windows.

statuscake_list_pagespeed_checks

List pagespeed checks with their location, alert thresholds and latest stats (load time ms, page size kb, request count, latest issue). StatusCake: GET /pagespeed.

statuscake_list_pagespeed_locations

List StatusCake's pagespeed monitoring servers — region, IPs and status. StatusCake: GET /pagespeed-locations.

statuscake_list_ssl_checks

List SSL certificate checks with the certificate's validity window (valid_from/valid_until), issuer, cipher and score, and flags such as expired, broken, revoked or mixed content. StatusCake: GET /ssl.

statuscake_list_uptime_alerts

Alerts triggered by one uptime check — when, the status it changed to and the status code. StatusCake: GET /uptime/{test_id}/alerts.

statuscake_list_uptime_checks

List uptime checks with their current status (up/down), type, URL, check rate, tags and uptime percentage. Filter by status or tags. StatusCake: GET /uptime.

statuscake_list_uptime_locations

List StatusCake's uptime monitoring servers — region, region code, IPv4/IPv6 and status. Use region codes in a check's regions; use the IPs for firewall allowlists. StatusCake: GET /uptime-locations.

statuscake_update_uptime_check

Change an uptime check's settings. Only the fields you pass are changed; list fields (tags, contact_groups, regions, dns_ips) are REPLACED, and an empty list clears them. Pass paused=true to pause a check and paused=false to resume it. StatusCake: PUT /uptime/{test_id}.

Endpoints

URL	Transport	State	Latency	Checked
https://statuscake.usefulapi.io/mcp	streamable-http	answering	100 ms	11 min ago

Alternatives to StatusCake MCP by usefulapi

same job, measured the same way

updown.io MCP by usefulapi

by usefulapi

Check updown.io uptime checks, downtimes, response metrics and status pages, and create checks.

14 tools answering

Instatus MCP by usefulapi

by usefulapi

Manage status pages: components, incidents and maintenances; set live component status.

14 tools answering

Better Stack MCP by usefulapi

by usefulapi

Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

9 tools answering

StatusPal MCP by usefulapi

by usefulapi

Read status-page status, services, incidents and metrics; create, update and publish incidents.

11 tools answering

Uptimely

by getuptimely

Uptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry.

answering

UptyBots

by uptybots

Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks

37 installs/wk 15 tools answering

Checkly MCP by usefulapi

by usefulapi

Query Checkly synthetic monitoring — checks, statuses, results, alerts, reporting and dashboards.

22 tools answering

Vantaj

by vantaj

Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.

13 tools answering

StatusCake MCP by usefulapi — questions

Answers built from our own checks of this server.

What can StatusCake MCP by usefulapi do?

It exposes 21 tools, read directly from the server on our last check. Among them: statuscake_create_heartbeat_check, statuscake_create_maintenance_window, statuscake_create_ssl_check, statuscake_create_uptime_check, statuscake_get_heartbeat_check, statuscake_get_maintenance_window and 15 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is StatusCake MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 121 ms. The bar chart above shows every period we have measured.

How do I connect StatusCake MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does StatusCake MCP by usefulapi need an API key?

No. StatusCake MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 21 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is StatusCake MCP by usefulapi?

It answers our handshake in 121 ms on average, which is faster than 78% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is StatusCake MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.