# io.usefulapi/statuscake (remote · statuscake.usefulapi.io)

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

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `statuscake.usefulapi.io`: 77/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-statuscake/statuscake.md), [page](https://verifymcp.io/servers/io-usefulapi-statuscake/statuscake)

## Channel facts

- Endpoint: `https://statuscake.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3535 tokens (~168/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.usefulapi/statuscake MCP server?

io.usefulapi/statuscake is a hosted endpoint at https://statuscake.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "io-usefulapi-statuscake": {
      "type": "http",
      "url": "https://statuscake.usefulapi.io/mcp"
    }
  }
}
```

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-statuscake": {
      "type": "remote",
      "url": "https://statuscake.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-statuscake --url 'https://statuscake.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-statuscake:
    url: "https://statuscake.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-statuscake": {
      "Transport": "http",
      "Url": "https://statuscake.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-statuscake -t streamable-http -u 'https://statuscake.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-statuscake": {
      "type": "http",
      "url": "https://statuscake.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-04 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-02 (score 76, +1)

- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 75, +4)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 71, +53)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (21)

### `statuscake_list_uptime_checks` (~156 tokens)

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.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `matchany` (boolean): With tags: return checks matching ANY of the tags instead of ALL of them.
- `nouptime` (boolean): Skip calculating uptime percentages (faster for large accounts).
- `page` (integer): Page of results, starting at 1.
- `status` (string): Only checks currently in this state.
- `tags` (string): Comma-separated tags; only checks carrying these tags are returned.

### `statuscake_get_uptime_check` (~61 tokens)

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}.

Input parameters:

- `test_id` (string, required): The uptime check id.

### `statuscake_get_uptime_history` (~137 tokens)

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.

Input parameters:

- `after` (integer): Only results after this UNIX timestamp (seconds).
- `before` (integer): Only results before this UNIX timestamp (seconds). Use it with links.next to page back in time.
- `limit` (integer): Results per page, 1-100 (default 25).
- `test_id` (string, required): The uptime check id.

### `statuscake_get_uptime_periods` (~134 tokens)

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.

Input parameters:

- `after` (integer): Only results after this UNIX timestamp (seconds).
- `before` (integer): Only results before this UNIX timestamp (seconds). Use it with links.next to page back in time.
- `limit` (integer): Results per page, 1-100 (default 25).
- `test_id` (string, required): The uptime check id.

### `statuscake_list_uptime_alerts` (~117 tokens)

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.

Input parameters:

- `after` (integer): Only results after this UNIX timestamp (seconds).
- `before` (integer): Only results before this UNIX timestamp (seconds). Use it with links.next to page back in time.
- `limit` (integer): Results per page, 1-100 (default 25).
- `test_id` (string, required): The uptime check id.

### `statuscake_list_ssl_checks` (~88 tokens)

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.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page of results, starting at 1.

### `statuscake_get_ssl_check` (~57 tokens)

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}.

Input parameters:

- `test_id` (string, required): The SSL check id.

### `statuscake_list_pagespeed_checks` (~82 tokens)

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.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page of results, starting at 1.

### `statuscake_get_pagespeed_history` (~128 tokens)

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.

Input parameters:

- `after` (integer): Only results after this UNIX timestamp (seconds).
- `before` (integer): Only results before this UNIX timestamp (seconds). Use it with links.next to page back in time.
- `limit` (integer): Results per page, 1-100 (default 25).
- `test_id` (string, required): The pagespeed check id.

### `statuscake_list_heartbeat_checks` (~154 tokens)

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.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `matchany` (boolean): With tags: return checks matching ANY of the tags instead of ALL of them.
- `nouptime` (boolean): Skip calculating uptime percentages (faster for large accounts).
- `page` (integer): Page of results, starting at 1.
- `status` (string): Only checks currently in this state.
- `tags` (string): Comma-separated tags; only checks carrying these tags are returned.

### `statuscake_get_heartbeat_check` (~57 tokens)

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}.

Input parameters:

- `test_id` (string, required): The heartbeat check id.

### `statuscake_list_contact_groups` (~84 tokens)

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.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page of results, starting at 1.

### `statuscake_list_maintenance_windows` (~107 tokens)

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.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page of results, starting at 1.
- `state` (string): Only windows in this state.

### `statuscake_get_maintenance_window` (~43 tokens)

Get one maintenance window

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

Input parameters:

- `window_id` (string, required): The maintenance window id.

### `statuscake_list_uptime_locations` (~75 tokens)

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.

Input parameters:

- `region_code` (string): Only servers in this region code.

### `statuscake_list_pagespeed_locations` (~68 tokens)

List pagespeed monitoring locations

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

Input parameters:

- `location` (string): Only servers in this country, as an ISO 3166-1 alpha-2 code, e.g. GB.

### `statuscake_create_uptime_check` (~638 tokens)

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.

Input parameters:

- `basic_password` (string): HTTP basic-auth password for the target.
- `basic_username` (string): HTTP basic-auth username for the target.
- `check_rate` (number, required): Seconds between checks: 0, 30, 60, 300, 900, 1800, 3600 or 86400.
- `confirmation` (integer): Number of confirmation servers that must agree before alerting, 0-3 (default 2).
- `contact_groups` (array): Contact group ids to alert (see statuscake_list_contact_groups). An empty list clears them.
- `custom_header` (string): JSON object string of headers to send, e.g. {"X-Env":"prod"}.
- `dns_ips` (array): IP addresses the DNS record must resolve to (DNS checks).
- `dns_server` (string): Nameserver to query (DNS checks).
- `do_not_find` (boolean): Invert find_string: the check is down if the string IS present.
- `enable_ssl_alert` (boolean): Alert when the site's SSL certificate is about to expire.
- `final_endpoint` (string): Where the redirect chain should end (with follow_redirects).
- `find_string` (string): String to look for in the response; the check is down if not found.
- `follow_redirects` (boolean): Follow redirects when testing (off by default).
- `host` (string): Name of the hosting provider (informational).
- `include_header` (boolean): Include response headers in the find_string search.
- `name` (string, required): Name of the check.
- `paused` (boolean): true to pause the check (stops running and alerting), false to resume.
- `port` (integer): Destination port (TCP, SMTP, SSH checks).
- `post_body` (string): JSON object string submitted with the request; setting it makes the check use HTTP POST.
- `post_raw` (string): Raw HTTP POST body to send.
- `regions` (array): Region codes to run the check from (see statuscake_list_uptime_locations).
- `status_codes_csv` (string): Comma-separated HTTP status codes that count as down, e.g. "500,502,503".
- `tags` (array): Tags for the check. An empty list clears them.
- `test_type` (string, required): Check type: HTTP, HEAD, TCP, DNS, SMTP, SSH or PING.
- `timeout` (integer): Seconds to wait for the first byte, 5-75 (default 15).
- `trigger_rate` (integer): Minutes to wait before sending an alert, 0-60 (default 0).
- `use_jar` (boolean): Enable cookie storage between requests.
- `user_agent` (string): Custom User-Agent sent with each check.
- `website_url` (string, required): URL, FQDN or IP address to check.

### `statuscake_update_uptime_check` (~653 tokens)

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}.

Input parameters:

- `basic_password` (string): HTTP basic-auth password for the target.
- `basic_username` (string): HTTP basic-auth username for the target.
- `check_rate` (number): Seconds between checks: 0, 30, 60, 300, 900, 1800, 3600 or 86400.
- `confirmation` (integer): Number of confirmation servers that must agree before alerting, 0-3 (default 2).
- `contact_groups` (array): Contact group ids to alert (see statuscake_list_contact_groups). An empty list clears them.
- `custom_header` (string): JSON object string of headers to send, e.g. {"X-Env":"prod"}.
- `dns_ips` (array): IP addresses the DNS record must resolve to (DNS checks).
- `dns_server` (string): Nameserver to query (DNS checks).
- `do_not_find` (boolean): Invert find_string: the check is down if the string IS present.
- `enable_ssl_alert` (boolean): Alert when the site's SSL certificate is about to expire.
- `final_endpoint` (string): Where the redirect chain should end (with follow_redirects).
- `find_string` (string): String to look for in the response; the check is down if not found.
- `follow_redirects` (boolean): Follow redirects when testing (off by default).
- `host` (string): Name of the hosting provider (informational).
- `include_header` (boolean): Include response headers in the find_string search.
- `name` (string): New name for the check.
- `paused` (boolean): true to pause the check (stops running and alerting), false to resume.
- `port` (integer): Destination port (TCP, SMTP, SSH checks).
- `post_body` (string): JSON object string submitted with the request; setting it makes the check use HTTP POST.
- `post_raw` (string): Raw HTTP POST body to send.
- `regions` (array): Region codes to run the check from (see statuscake_list_uptime_locations).
- `status_codes_csv` (string): Comma-separated HTTP status codes that count as down, e.g. "500,502,503".
- `tags` (array): Tags for the check. An empty list clears them.
- `test_id` (string, required): The uptime check id.
- `timeout` (integer): Seconds to wait for the first byte, 5-75 (default 15).
- `trigger_rate` (integer): Minutes to wait before sending an alert, 0-60 (default 0).
- `use_jar` (boolean): Enable cookie storage between requests.
- `user_agent` (string): Custom User-Agent sent with each check.
- `website_url` (string): New URL, FQDN or IP address to check.

### `statuscake_create_ssl_check` (~269 tokens)

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.

Input parameters:

- `alert_at` (array, required): Exactly three day counts before expiry at which to alert, e.g. [30, 7, 1].
- `alert_broken` (boolean): Alert when certificate problems are found.
- `alert_expiry` (boolean): Alert when the certificate is about to expire.
- `alert_mixed` (boolean): Alert when mixed content is found.
- `alert_reminder` (boolean): Send alert reminders.
- `check_rate` (number, required): Seconds between checks: 300, 600, 1800, 3600, 86400 or 2073600.
- `contact_groups` (array): Contact group ids to alert (see statuscake_list_contact_groups). An empty list clears them.
- `follow_redirects` (boolean): Follow redirects when testing (off by default).
- `hostname` (string): Hostname of the server under test, if different from the URL.
- `paused` (boolean): Create the check paused.
- `user_agent` (string): Custom User-Agent sent when testing.
- `website_url` (string, required): URL of the server under test; must begin with https://.

### `statuscake_create_heartbeat_check` (~183 tokens)

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.

Input parameters:

- `contact_groups` (array): Contact group ids to alert (see statuscake_list_contact_groups). An empty list clears them.
- `host` (string): Name of the hosting provider (informational).
- `name` (string, required): Name of the check.
- `paused` (boolean): Create the check paused.
- `period` (integer, required): Seconds since the last ping before the check is down, 30-172800 (e.g. 1800).
- `tags` (array): Tags for the check. An empty list clears them.

### `statuscake_create_maintenance_window` (~244 tokens)

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.

Input parameters:

- `end_at` (string, required): End, RFC3339, e.g. 2026-10-04T06:00:00Z.
- `name` (string, required): Name of the maintenance window.
- `repeat_interval` (string): How often it repeats: never, 1d, 1w, 2w or 1m.
- `start_at` (string, required): Start, RFC3339, e.g. 2026-10-04T01:30:00Z.
- `tags` (array): Include every uptime check carrying these tags.
- `tests` (array): Uptime check ids to include.
- `timezone` (string, required): IANA timezone the times are read in, e.g. UTC or Europe/London.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-statuscake/statuscake#diagnostics

## Score history

- 2026-10-04: 77
- 2026-10-03: 76
- 2026-10-02: 76
- 2026-10-01: 75
- 2026-09-30: 71
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/statuscake MCP server?

io.usefulapi/statuscake is an MCP server listed in the public MCP registry as io.usefulapi/statuscake. Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks. This page covers its hosted endpoint (https://statuscake.usefulapi.io/mcp).

### Is the io.usefulapi/statuscake MCP server safe to use?

io.usefulapi/statuscake scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.usefulapi/statuscake MCP server expose?

io.usefulapi/statuscake exposes 21 tools: statuscake_list_uptime_checks, statuscake_get_uptime_check, statuscake_get_uptime_history, statuscake_get_uptime_periods, statuscake_list_uptime_alerts, and 16 more. Their descriptions and schemas cost roughly 3,535 tokens of context every time the server is loaded.

### Does the io.usefulapi/statuscake MCP server require authentication?

Yes. io.usefulapi/statuscake asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.usefulapi/statuscake MCP server still maintained?

io.usefulapi/statuscake is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://statuscake.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-statuscake/statuscake.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-statuscake/statuscake.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-statuscake/statuscake