io.usefulapi/statuscake
REMOTE · STATUSCAKE.USEFULAPI.IO · SCANNED OCT 4
Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · statuscake.usefulapi.io
claude mcp add --transport http io-usefulapi-statuscake 'https://statuscake.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-statuscake": {
"url": "https://statuscake.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-statuscake": {
"type": "http",
"url": "https://statuscake.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-statuscake] url = "https://statuscake.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-statuscake": {
"type": "remote",
"url": "https://statuscake.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-statuscake --url 'https://statuscake.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-statuscake:
url: "https://statuscake.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-statuscake": {
"Transport": "http",
"Url": "https://statuscake.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-statuscake -t streamable-http -u 'https://statuscake.usefulapi.io/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 +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.
- 2 Oct 26 +1
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +4
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +53
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 29 Sept 26 18
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://statuscake.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of statuscake.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://statuscake.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://statuscake.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://statuscake.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://statuscake.usefulapi.io/mcp |
| Authorisation server | https://statuscake.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://statuscake.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://statuscake.usefulapi.io/mcp | HTTPS enforced | 301 | https://statuscake.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
statuscake_create_heartbeat_check Create a heartbeat check ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Name of the check. |
| paused | boolean | – | Create the check paused. |
| period | integer | yes | 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. |
No output schema declared.
No examples provided.
statuscake_create_maintenance_window Create a maintenance window ~244
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end_at | string | yes | End, RFC3339, e.g. 2026-10-04T06:00:00Z. |
| name | string | yes | Name of the maintenance window. |
| repeat_interval | string | – | How often it repeats: never, 1d, 1w, 2w or 1m. |
| start_at | string | yes | 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 | yes | IANA timezone the times are read in, e.g. UTC or Europe/London. |
No output schema declared.
No examples provided.
statuscake_create_ssl_check Create an SSL check ~269
Start monitoring a site's SSL certificate for expiry and problems. Returns the new id as data.new_id. StatusCake: POST /ssl.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_at | array | yes | 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 | yes | 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 | yes | URL of the server under test; must begin with https://. |
No output schema declared.
No examples provided.
statuscake_create_uptime_check Create an uptime check ~638
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.
| Name | Type | Req | Description |
|---|---|---|---|
| basic_password | string | – | HTTP basic-auth password for the target. |
| basic_username | string | – | HTTP basic-auth username for the target. |
| check_rate | number | yes | 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 | yes | 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 | yes | 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 | yes | URL, FQDN or IP address to check. |
No output schema declared.
No examples provided.
statuscake_get_heartbeat_check Get one heartbeat check ~57
Fetch one heartbeat check in full, including its ping URL, period, status and when it last received a ping. StatusCake: GET /heartbeat/{test_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| test_id | string | yes | The heartbeat check id. |
No output schema declared.
No examples provided.
statuscake_get_maintenance_window Get one maintenance window ~43
Fetch one maintenance window by id. StatusCake: GET /maintenance-windows/{window_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| window_id | string | yes | The maintenance window id. |
No output schema declared.
No examples provided.
statuscake_get_pagespeed_history Get pagespeed check history ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The pagespeed check id. |
No output schema declared.
No examples provided.
statuscake_get_ssl_check Get one SSL check ~57
Fetch one SSL certificate check in full — expiry, issuer, cipher, scores, flags and any mixed-content resources found. StatusCake: GET /ssl/{test_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| test_id | string | yes | The SSL check id. |
No output schema declared.
No examples provided.
statuscake_get_uptime_check Get one uptime check ~61
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| test_id | string | yes | The uptime check id. |
No output schema declared.
No examples provided.
statuscake_get_uptime_history Get uptime check history ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The uptime check id. |
No output schema declared.
No examples provided.
statuscake_get_uptime_periods Get uptime check up/down periods ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The uptime check id. |
No output schema declared.
No examples provided.
statuscake_list_contact_groups List contact groups ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page of results, starting at 1. |
No output schema declared.
No examples provided.
statuscake_list_heartbeat_checks List heartbeat checks ~154
List heartbeat (push) checks — jobs that must ping a StatusCake URL within a period — with their status, period and ping URL. StatusCake: GET /heartbeat.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
statuscake_list_maintenance_windows List maintenance windows ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page of results, starting at 1. |
| state | string | – | Only windows in this state. |
No output schema declared.
No examples provided.
statuscake_list_pagespeed_checks List pagespeed checks ~82
List pagespeed checks with their location, alert thresholds and latest stats (load time ms, page size kb, request count, latest issue). StatusCake: GET /pagespeed.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page of results, starting at 1. |
No output schema declared.
No examples provided.
statuscake_list_pagespeed_locations List pagespeed monitoring locations ~68
List StatusCake's pagespeed monitoring servers — region, IPs and status. StatusCake: GET /pagespeed-locations.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | – | Only servers in this country, as an ISO 3166-1 alpha-2 code, e.g. GB. |
No output schema declared.
No examples provided.
statuscake_list_ssl_checks List SSL checks ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page of results, starting at 1. |
No output schema declared.
No examples provided.
statuscake_list_uptime_alerts List uptime check alerts ~117
Alerts triggered by one uptime check — when, the status it changed to and the status code. StatusCake: GET /uptime/{test_id}/alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The uptime check id. |
No output schema declared.
No examples provided.
statuscake_list_uptime_checks List uptime checks ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
statuscake_list_uptime_locations List uptime monitoring locations ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| region_code | string | – | Only servers in this region code. |
No output schema declared.
No examples provided.
statuscake_update_uptime_check Update an uptime check ~653
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.