Model Context Protocol server for Rollbar
Nothing to run from here
Statuscake is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
21
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usefulapi-statuscake-mcp https://statuscake.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# statuscake_list_uptime_checks, statuscake_get_uptime_check, statuscake_get_uptime_history and 18 more
Statuscake costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http usefulapi-statuscake-mcp https://statuscake.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Only checks currently in this state. |
| tags | string | no | Comma-separated tags; only checks carrying these tags are returned. |
| matchany | boolean | no | With tags: return checks matching ANY of the tags instead of ALL of them. |
| nouptime | boolean | no | Skip calculating uptime percentages (faster for large accounts). |
| page | integer | no | Page of results, starting at 1. |
| limit | integer | no | Results per page, 1-100 (default 25). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| test_id | string | yes | The uptime check id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| test_id | string | yes | The uptime check id. |
| limit | integer | no | Results per page, 1-100 (default 25). |
| before | integer | no | Only results before this UNIX timestamp (seconds). Use it with links.next to page back in time. |
| after | integer | no | Only results after this UNIX timestamp (seconds). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| test_id | string | yes | The uptime check id. |
| limit | integer | no | Results per page, 1-100 (default 25). |
| before | integer | no | Only results before this UNIX timestamp (seconds). Use it with links.next to page back in time. |
| after | integer | no | Only results after this UNIX timestamp (seconds). |
Alerts triggered by one uptime check — when, the status it changed to and the status code. StatusCake: GET /uptime/{test_id}/alerts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| test_id | string | yes | The uptime check id. |
| limit | integer | no | Results per page, 1-100 (default 25). |
| before | integer | no | Only results before this UNIX timestamp (seconds). Use it with links.next to page back in time. |
| after | integer | no | Only results after this UNIX timestamp (seconds). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page of results, starting at 1. |
| limit | integer | no | Results per page, 1-100 (default 25). |
Fetch one SSL certificate check in full — expiry, issuer, cipher, scores, flags and any mixed-content resources found. StatusCake: GET /ssl/{test_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| test_id | string | yes | The SSL check id. |
List pagespeed checks with their location, alert thresholds and latest stats (load time ms, page size kb, request count, latest issue). StatusCake: GET /pagespeed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page of results, starting at 1. |
| limit | integer | no | Results per page, 1-100 (default 25). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| test_id | string | yes | The pagespeed check id. |
| limit | integer | no | Results per page, 1-100 (default 25). |
| before | integer | no | Only results before this UNIX timestamp (seconds). Use it with links.next to page back in time. |
| after | integer | no | Only results after this UNIX timestamp (seconds). |
List heartbeat (push) checks — jobs that must ping a StatusCake URL within a period — with their status, period and ping URL. StatusCake: GET /heartbeat.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Only checks currently in this state. |
| tags | string | no | Comma-separated tags; only checks carrying these tags are returned. |
| matchany | boolean | no | With tags: return checks matching ANY of the tags instead of ALL of them. |
| nouptime | boolean | no | Skip calculating uptime percentages (faster for large accounts). |
| page | integer | no | Page of results, starting at 1. |
| limit | integer | no | Results per page, 1-100 (default 25). |
Fetch one heartbeat check in full, including its ping URL, period, status and when it last received a ping. StatusCake: GET /heartbeat/{test_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| test_id | string | yes | The heartbeat check id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page of results, starting at 1. |
| limit | integer | no | Results per page, 1-100 (default 25). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | Only windows in this state. |
| page | integer | no | Page of results, starting at 1. |
| limit | integer | no | Results per page, 1-100 (default 25). |
Fetch one maintenance window by id. StatusCake: GET /maintenance-windows/{window_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| window_id | string | yes | The maintenance window id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| region_code | string | no | Only servers in this region code. |
List StatusCake's pagespeed monitoring servers — region, IPs and status. StatusCake: GET /pagespeed-locations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| location | string | no | Only servers in this country, as an ISO 3166-1 alpha-2 code, e.g. GB. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Name of the check. |
| test_type | string | yes | Check type: HTTP, HEAD, TCP, DNS, SMTP, SSH or PING. |
| website_url | string | yes | URL, FQDN or IP address to check. |
| check_rate | number | yes | Seconds between checks: 0, 30, 60, 300, 900, 1800, 3600 or 86400. |
| contact_groups | array | no | Contact group ids to alert (see statuscake_list_contact_groups). An empty list clears them. |
| tags | array | no | Tags for the check. An empty list clears them. |
| paused | boolean | no | true to pause the check (stops running and alerting), false to resume. |
| timeout | integer | no | Seconds to wait for the first byte, 5-75 (default 15). |
| trigger_rate | integer | no | Minutes to wait before sending an alert, 0-60 (default 0). |
| confirmation | integer | no | Number of confirmation servers that must agree before alerting, 0-3 (default 2). |
| regions | array | no | Region codes to run the check from (see statuscake_list_uptime_locations). |
| find_string | string | no | String to look for in the response; the check is down if not found. |
| do_not_find | boolean | no | Invert find_string: the check is down if the string IS present. |
| include_header | boolean | no | Include response headers in the find_string search. |
| follow_redirects | boolean | no | Follow redirects when testing (off by default). |
| final_endpoint | string | no | Where the redirect chain should end (with follow_redirects). |
| status_codes_csv | string | no | Comma-separated HTTP status codes that count as down, e.g. "500,502,503". |
| enable_ssl_alert | boolean | no | Alert when the site's SSL certificate is about to expire. |
| user_agent | string | no | Custom User-Agent sent with each check. |
| custom_header | string | no | JSON object string of headers to send, e.g. {"X-Env":"prod"}. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| test_id | string | yes | The uptime check id. |
| name | string | no | New name for the check. |
| website_url | string | no | New URL, FQDN or IP address to check. |
| check_rate | number | no | Seconds between checks: 0, 30, 60, 300, 900, 1800, 3600 or 86400. |
| contact_groups | array | no | Contact group ids to alert (see statuscake_list_contact_groups). An empty list clears them. |
| tags | array | no | Tags for the check. An empty list clears them. |
| paused | boolean | no | true to pause the check (stops running and alerting), false to resume. |
| timeout | integer | no | Seconds to wait for the first byte, 5-75 (default 15). |
| trigger_rate | integer | no | Minutes to wait before sending an alert, 0-60 (default 0). |
| confirmation | integer | no | Number of confirmation servers that must agree before alerting, 0-3 (default 2). |
| regions | array | no | Region codes to run the check from (see statuscake_list_uptime_locations). |
| find_string | string | no | String to look for in the response; the check is down if not found. |
| do_not_find | boolean | no | Invert find_string: the check is down if the string IS present. |
| include_header | boolean | no | Include response headers in the find_string search. |
| follow_redirects | boolean | no | Follow redirects when testing (off by default). |
| final_endpoint | string | no | Where the redirect chain should end (with follow_redirects). |
| status_codes_csv | string | no | Comma-separated HTTP status codes that count as down, e.g. "500,502,503". |
| enable_ssl_alert | boolean | no | Alert when the site's SSL certificate is about to expire. |
| user_agent | string | no | Custom User-Agent sent with each check. |
| custom_header | string | no | JSON object string of headers to send, e.g. {"X-Env":"prod"}. |
Start monitoring a site's SSL certificate for expiry and problems. Returns the new id as data.new_id. StatusCake: POST /ssl.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| website_url | string | yes | URL of the server under test; must begin with https://. |
| check_rate | number | yes | Seconds between checks: 300, 600, 1800, 3600, 86400 or 2073600. |
| alert_at | array | yes | Exactly three day counts before expiry at which to alert, e.g. [30, 7, 1]. |
| alert_expiry | boolean | no | Alert when the certificate is about to expire. |
| alert_broken | boolean | no | Alert when certificate problems are found. |
| alert_mixed | boolean | no | Alert when mixed content is found. |
| alert_reminder | boolean | no | Send alert reminders. |
| contact_groups | array | no | Contact group ids to alert (see statuscake_list_contact_groups). An empty list clears them. |
| follow_redirects | boolean | no | Follow redirects when testing (off by default). |
| hostname | string | no | Hostname of the server under test, if different from the URL. |
| user_agent | string | no | Custom User-Agent sent when testing. |
| paused | boolean | no | Create the check paused. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Name of the check. |
| period | integer | yes | Seconds since the last ping before the check is down, 30-172800 (e.g. 1800). |
| contact_groups | array | no | Contact group ids to alert (see statuscake_list_contact_groups). An empty list clears them. |
| tags | array | no | Tags for the check. An empty list clears them. |
| host | string | no | Name of the hosting provider (informational). |
| paused | boolean | no | Create the check paused. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Name of the maintenance window. |
| start_at | string | yes | Start, RFC3339, e.g. 2026-10-04T01:30:00Z. |
| end_at | string | yes | End, RFC3339, e.g. 2026-10-04T06:00:00Z. |
| timezone | string | yes | IANA timezone the times are read in, e.g. UTC or Europe/London. |
| repeat_interval | string | no | How often it repeats: never, 1d, 1w, 2w or 1m. |
| tests | array | no | Uptime check ids to include. |
| tags | array | no | Include every uptime check carrying these tags. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Statuscake or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Statuscake can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.