io.usefulapi/statuspal
REMOTE · STATUSPAL.USEFULAPI.IO · SCANNED AUG 3
Read status-page status, services, incidents and metrics; create, update and publish incidents.
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 →
Endpoint Security78
- 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 not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1218 tokens (~110/item across 11 items; 11 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 Management23
- Stability observed for 7 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · statuspal.usefulapi.io
claude mcp add --transport http io-usefulapi-statuspal https://statuspal.usefulapi.io/mcp
[mcp_servers.io-usefulapi-statuspal] url = "https://statuspal.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-statuspal": {
"type": "remote",
"url": "https://statuspal.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-statuspal --url https://statuspal.usefulapi.io/mcp --transport streamable-http
mcp_servers:
io-usefulapi-statuspal:
url: "https://statuspal.usefulapi.io/mcp" {
"mcpServers": {
"io-usefulapi-statuspal": {
"type": "http",
"url": "https://statuspal.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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 26 +57
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 12
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 3 Aug 2026 · Probed https://statuspal.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 | 19 Jul 2026 | 17 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | b9ad1884585d58ff135af2b4961e8082 |
| SANs: usefulapi.io, statuspal.usefulapi.io, *.statuspal.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 |
DNSSEC insecure
Validation of statuspal.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://statuspal.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://statuspal.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" Protected resource metadata
| Document | https://statuspal.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://statuspal.usefulapi.io/mcp |
| Authorisation server | https://statuspal.usefulapi.io |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://statuspal.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://statuspal.usefulapi.io/mcp | Inconclusive | 401 |
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.
statuspal_create_incident Create incident ~207
PUBLISHES a new incident to the LIVE public status page (and, with notify=true, emails/notifies subscribers). type="major" or "minor" is an outage incident; type="scheduled" creates a scheduled maintenance window. StatusPal: POST /status_pages/{subdomain}/incidents.
| Name | Type | Req | Description |
|---|---|---|---|
| ends_at | string | — | ISO8601 end time (optional). |
| notify | boolean | — | Whether to notify/email subscribers. |
| service_ids | array | yes | Ids of the affected services (required). |
| starts_at | string | — | ISO8601 start time (optional; required for scheduled maintenance). |
| subdomain | string | — | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
| title | string | yes | Incident title (required). |
| type | string | yes | Incident type. "major"/"minor" = outage severity; "scheduled" = a maintenance window. |
| updates | array | — | Optional initial updates to post with the incident. |
No output schema declared.
No examples provided.
statuspal_create_incident_update Post incident update ~185
POSTS an update (e.g. investigating → identified → monitoring → resolved) to an existing incident on the LIVE public status page (and, with notify=true, notifies subscribers). StatusPal: POST /status_pages/{subdomain}/incidents/{incident_id}/updates.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | The update message shown on the status page (required). |
| incident_id | number | yes | The incident id to post an update to. |
| notify | boolean | — | Whether to notify/email subscribers about this update. |
| posted_at | string | — | ISO8601 timestamp for the update (optional; defaults to now). |
| subdomain | string | — | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
| type | string | yes | Update type — common values: "investigating", "identified", "monitoring", "resolved", "issue". |
No output schema declared.
No examples provided.
statuspal_delete_incident Delete incident ~77
DELETES an incident from the LIVE public status page — this permanently removes it. StatusPal: DELETE /status_pages/{subdomain}/incidents/{incident_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | number | yes | The incident id to delete. |
| subdomain | string | — | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
No output schema declared.
No examples provided.
statuspal_get_incident Get incident ~66
Get a single incident by its id. StatusPal: GET /status_pages/{subdomain}/incidents/{incident_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | number | yes | The incident id. |
| subdomain | string | — | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
No output schema declared.
No examples provided.
statuspal_get_service_status Get service status ~71
Get the current status of a single service by its id. StatusPal: GET /status_pages/{subdomain}/services/{service_id}/status.
| Name | Type | Req | Description |
|---|---|---|---|
| service_id | number | yes | The service id. |
| subdomain | string | — | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
No output schema declared.
No examples provided.
statuspal_get_status Get overall status ~57
Get the current overall status of the status page (the aggregate status type). StatusPal: GET /status_pages/{subdomain}/status.
| Name | Type | Req | Description |
|---|---|---|---|
| subdomain | string | — | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
No output schema declared.
No examples provided.
statuspal_get_summary Get status page summary ~75
Get the FULL status-page summary — status_page, services[], incidents[], maintenances[], upcoming_maintenances[], info_notices[], and current_status_type. StatusPal: GET /status_pages/{subdomain}/summary.
| Name | Type | Req | Description |
|---|---|---|---|
| subdomain | string | — | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
No output schema declared.
No examples provided.
statuspal_list_incidents List incidents ~147
List incidents for a status page. Returns {incidents[], links:{next,prev}, meta:{total_count}}. Use `before`/`after` cursors to paginate and `type` to filter. StatusPal: GET /status_pages/{subdomain}/incidents.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | — | Pagination cursor — return incidents after this cursor. |
| before | string | — | Pagination cursor — return incidents before this cursor. |
| limit | number | — | Max incidents to return (default 20, max 100). |
| subdomain | string | — | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
| type | string | — | Filter incidents by type. |
No output schema declared.
No examples provided.
statuspal_list_metrics List metrics ~105
List the metrics configured on a status page. Use `before`/`after` cursors to paginate. StatusPal: GET /status_pages/{subdomain}/metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | — | Pagination cursor — return metrics after this cursor. |
| before | string | — | Pagination cursor — return metrics before this cursor. |
| limit | number | — | Max metrics to return. |
| subdomain | string | — | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
No output schema declared.
No examples provided.
statuspal_list_services List services ~65
List the services on a status page — each with {id, name, current_incident_type, children[]}. StatusPal: GET /status_pages/{subdomain}/services.
| Name | Type | Req | Description |
|---|---|---|---|
| subdomain | string | — | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
No output schema declared.
No examples provided.
statuspal_update_incident Update incident ~163
UPDATES an existing incident on the LIVE public status page (title/type/services/timing). StatusPal: PUT /status_pages/{subdomain}/incidents/{incident_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| ends_at | string | — | New ISO8601 end time. |
| incident_id | number | yes | The incident id to update. |
| notify | boolean | — | Whether to notify/email subscribers about the change. |
| service_ids | array | — | New set of affected service ids. |
| starts_at | string | — | New ISO8601 start time. |
| subdomain | string | — | Status page subdomain (overrides STATUSPAL_SUBDOMAIN). |
| title | string | — | New incident title. |
| type | string | — | New incident type ("major"/"minor"/"scheduled"). |
No output schema declared.
No examples provided.