Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks. For web and IT teams who monitor sites and cron jobs with StatusCake. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"statuscake": {
"url": "https://statuscake.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"statuscake": {
"type": "http",
"url": "https://statuscake.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The AI lists uptime checks by status or tag, then reads the up and down periods, test runs with status code and response time, and alerts of a check.
statuscake_list_uptime_checks statuscake_get_uptime_periods statuscake_get_uptime_history statuscake_list_uptime_alerts
The AI lists SSL checks with valid-until date, issuer and flags such as expired, broken, revoked or mixed content, and sorts them by expiry.
statuscake_list_ssl_checks statuscake_get_ssl_check
The AI lists pagespeed checks with the latest load time, page size and request count and reads the history of one check.
statuscake_list_pagespeed_checks statuscake_get_pagespeed_history
The AI lists heartbeat checks with their status and period, and reads one to see when it last received a ping and what its ping URL is.
statuscake_list_heartbeat_checks statuscake_get_heartbeat_check
The AI creates an uptime check for a URL, host or IP, an SSL check, or a heartbeat check for a cron job. It can look up the contact groups to alert.
Changes data · statuscake_create_uptime_check statuscake_create_ssl_check statuscake_create_heartbeat_check statuscake_list_contact_groups
The AI pauses or resumes an uptime check, changes its settings, or schedules a maintenance window that silences alerts for checks or tags.
Changes data · statuscake_update_uptime_check statuscake_create_maintenance_window statuscake_list_maintenance_windows
The login page asks for your StatusCake API key.
Create or copy one in the StatusCake app under Account → API Keys. Your key is used only to call the StatusCake API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your StatusCake API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the StatusCake connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
statuscake_list_uptime_checks | read | 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_get_uptime_check | read | Get one 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 | read | Get uptime check 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 | read | Get uptime check up/down 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_uptime_alerts | read | List uptime check 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_ssl_checks | read | 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_get_ssl_check | read | Get one 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_list_pagespeed_checks | read | 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_get_pagespeed_history | read | Get pagespeed check 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_list_heartbeat_checks | read | 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_get_heartbeat_check | read | Get one 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_list_contact_groups | read | 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_maintenance_windows | read | 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_get_maintenance_window | read | Get one maintenance window Fetch one maintenance window by id. StatusCake: GET /maintenance-windows/{window_id}. |
statuscake_list_uptime_locations | read | List uptime monitoring 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_list_pagespeed_locations | read | List pagespeed monitoring locations List StatusCake's pagespeed monitoring servers — region, IPs and status. StatusCake: GET /pagespeed-locations. |
statuscake_create_uptime_check | write | Create an 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_update_uptime_check | write | Update an 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}. |
statuscake_create_ssl_check | write | Create an 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_heartbeat_check | write | Create a 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 | write | Create a 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_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
statuscake_request_feature | Request a missing feature Tell usefulapi that the user needs something the StatusCake tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
statuscake_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on StatusCake (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
statuscake_cancel_subscription | Cancel the Pro subscription Cancel the caller's StatusCake Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run statuscake_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this StatusCake server only. Subscribe with statuscake_upgrade (it returns a Stripe Checkout link). Cancel any time with statuscake_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running statuscake_upgrade before then undoes the cancel. Or write to [email protected].
Find checks that are down and see how long. Check SSL certificates for expiry and problems. Review page load time and size. Check that cron jobs and workers still ping in. Start monitoring a site, certificate or cron job. Update uptime checks or schedule maintenance windows. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by StatusCake. The server calls the StatusCake API with your own StatusCake access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your StatusCake API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your StatusCake API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the StatusCake API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in StatusCake.
Yes, if you approve it. 5 of the 21 StatusCake tools can create or change data. The other 16 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this StatusCake server only. Cancel any time: Pro then runs to the end of the paid period. Run statuscake_usage_status to see how many calls you used.
Ask the AI to run statuscake_upgrade: it returns a Stripe Checkout link. To cancel, run statuscake_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with statuscake_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.