statuscake

Tools

21 tools: 16 read-only, 0 change data, 5 high risk (delete, pay, send or run code).

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 6,013 tokens of tool definitions and a 534 ms handshake.

• high riskstatuscake_create_uptime_checkStart 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.
• high riskstatuscake_update_uptime_checkChange 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}.
• high riskstatuscake_create_ssl_checkStart monitoring a site's SSL certificate for expiry and problems. Returns the new id as data.new_id. StatusCake: POST /ssl.
• high riskstatuscake_create_heartbeat_checkCreate 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.
• high riskstatuscake_create_maintenance_windowSchedule 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-w...
• read-onlystatuscake_list_uptime_checksList uptime checks with their current status (up/down), type, URL, check rate, tags and uptime percentage. Filter by status or tags. StatusCake: GET /uptime.
• read-onlystatuscake_get_uptime_checkFetch 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}.
• read-onlystatuscake_get_uptime_historyIndividual 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.
• read-onlystatuscake_get_uptime_periodsThe 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.
• read-onlystatuscake_list_uptime_alertsAlerts triggered by one uptime check - when, the status it changed to and the status code. StatusCake: GET /uptime/{test_id}/alerts.
• read-onlystatuscake_list_ssl_checksList 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.
• read-onlystatuscake_get_ssl_checkFetch one SSL certificate check in full - expiry, issuer, cipher, scores, flags and any mixed-content resources found. StatusCake: GET /ssl/{test_id}.
• read-onlystatuscake_list_pagespeed_checksList pagespeed checks with their location, alert thresholds and latest stats (load time ms, page size kb, request count, latest issue). StatusCake: GET /pagespeed.
• read-onlystatuscake_get_pagespeed_historyPast 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.
• read-onlystatuscake_list_heartbeat_checksList heartbeat (push) checks - jobs that must ping a StatusCake URL within a period - with their status, period and ping URL. StatusCake: GET /heartbeat.
• read-onlystatuscake_get_heartbeat_checkFetch one heartbeat check in full, including its ping URL, period, status and when it last received a ping. StatusCake: GET /heartbeat/{test_id}.
• read-onlystatuscake_list_contact_groupsList 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.
• read-onlystatuscake_list_maintenance_windowsList 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.
• read-onlystatuscake_get_maintenance_windowFetch one maintenance window by id. StatusCake: GET /maintenance-windows/{window_id}.
• read-onlystatuscake_list_uptime_locationsList 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.
• read-onlystatuscake_list_pagespeed_locationsList StatusCake's pagespeed monitoring servers - region, IPs and status. StatusCake: GET /pagespeed-locations.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-05, 534 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-062026-10-05

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Developer tools and code, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/statuscake.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/statuscake.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=statuscake.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/statuscake.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/statuscake.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=statuscake.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.