Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.usefulapi/instatus

REMOTE · INSTATUS.USEFULAPI.IO · SCANNED SEP 20

Manage status pages: components, incidents and maintenances; set live component status.

Available components

remote · instatus.usefulapi.io 73
+55 this week 73 Trust /100
Trust breakdown (7 categories)

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 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 enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1917 tokens (~136/item across 14 items; 14 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
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 14 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
Install

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

io.usefulapi/instatus is a hosted endpoint at https://instatus.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 · instatus.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-instatus 'https://instatus.usefulapi.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-usefulapi-instatus": {
      "url": "https://instatus.usefulapi.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-usefulapi-instatus": {
      "type": "http",
      "url": "https://instatus.usefulapi.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-usefulapi-instatus]
url = "https://instatus.usefulapi.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-instatus": {
      "type": "remote",
      "url": "https://instatus.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-usefulapi-instatus --url 'https://instatus.usefulapi.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-usefulapi-instatus:
    url: "https://instatus.usefulapi.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-usefulapi-instatus": {
      "Transport": "http",
      "Url": "https://instatus.usefulapi.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-usefulapi-instatus -t streamable-http -u 'https://instatus.usefulapi.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-usefulapi-instatus": {
      "type": "http",
      "url": "https://instatus.usefulapi.io/mcp"
    }
  }
}

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

Changelog

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.

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Sept 26 +53
    • Transport: unverified → pass ▲ security
    • Authorization: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Schema quality: unverified → fail ▼ functional
    • Schema quality: unverified → fail ▼ functional
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Schema quality: unverified → excellent ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Destructive annotations: 100 functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 12 Sept 26 0
    • Transport: fail → unverified ▼ security
  • 1 Sept 26 −10
    • Endpoint reachability: behind authorisation → not serving MCP ▼ security
    • Transport: pass → fail ▼ security
    • Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools. security
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
  • 31 Aug 26 +10
    • Endpoint reachability: not serving MCP → behind authorisation ▼ security
    • Transport: unverified → pass ▲ security
    • Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
    • Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
    • Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
    • Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 19 Aug 26 0
    • Endpoint reachability: behind authorisation → not serving MCP ▼ security
    • Transport: pass → unverified ▼ security
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
Diagnostics

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 20 Sept 2026 · Probed https://instatus.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 16 Sept 2026 15 Dec 2026 ECDSA 256 ECDSA-SHA256 6d4a999d162accf313fa075b832ad61f
SANs: usefulapi.io, instatus.usefulapi.io, *.instatus.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 instatus.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://instatus.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" 

Bearer realm="OAuth", resource_metadata="https://instatus.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document https://instatus.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://instatus.usefulapi.io/mcp
Authorisation server https://instatus.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://instatus.usefulapi.io/mcp Verified 200
http (plaintext) http://instatus.usefulapi.io/mcp Inconclusive 401
MCP tools · 14 exposed · ~1,917 tokens

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 →

Tool Tokens
instatus_create_incident ~216

CREATES a new incident — this MODIFIES live status-page data and can notify subscribers. Provide `name` (required); optionally set the initial `message`, affected `components`, per-component impact via `statuses`, `status`, `started`, `notify`, and `shouldPublish`. Instatus: POST /v1/{page_id}/incidents. Returns the created incident.

NameTypeReqDescription
componentsarray–Component ids affected by this incident.
messagestring–Incident update message (Markdown supported).
namestringyesIncident title (required).
notifyboolean–Whether to notify subscribers about this update.
page_idstringyesThe status page's id.
shouldPublishboolean–Whether the incident should be published to the status page.
startedstring–ISO 8601 timestamp for when the incident started.
statusstring–Incident status.
statusesarray–Per-component impact — set each listed component's status for this event.

No output schema declared.

No examples provided.

instatus_create_maintenance ~229

CREATES a new scheduled maintenance — this MODIFIES live status-page data and can notify subscribers. Provide `name` (required); optionally set `message`, affected `components`, per-component impact via `statuses`, `status`, `start`/`end`, `duration`, and `notify`. Instatus: POST /v1/{page_id}/maintenances. Returns the created maintenance.

NameTypeReqDescription
componentsarray–Component ids affected by this maintenance.
durationinteger–Maintenance duration in minutes.
endstring–ISO 8601 timestamp for when the maintenance ends.
messagestring–Maintenance update message (Markdown supported).
namestringyesMaintenance title (required).
notifyboolean–Whether to notify subscribers about this update.
page_idstringyesThe status page's id.
startstring–ISO 8601 timestamp for when the maintenance starts.
statusstring–Maintenance status.
statusesarray–Per-component impact — set each listed component's status for this event.

No output schema declared.

No examples provided.

instatus_delete_incident ~80

PERMANENTLY DELETES an incident by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/incidents/{incident_id}.

NameTypeReqDescription
incident_idstringyesThe incident's id to delete.
page_idstringyesThe status page's id.

No output schema declared.

No examples provided.

instatus_delete_maintenance ~82

PERMANENTLY DELETES a scheduled maintenance by id — this MODIFIES live status-page data and cannot be undone. Instatus: DELETE /v1/{page_id}/maintenances/{maintenance_id}.

NameTypeReqDescription
maintenance_idstringyesThe maintenance's id to delete.
page_idstringyesThe status page's id.

No output schema declared.

No examples provided.

instatus_get_component ~78

Get a single component by id — its full state (name, description, status, order, showUptime, grouped, archived). Instatus: GET /v2/{page_id}/components/{component_id}.

NameTypeReqDescription
component_idstringyesThe component's id.
page_idstringyesThe status page's id.

No output schema declared.

No examples provided.

instatus_get_incident ~71

Get a single incident by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/incidents/{incident_id}.

NameTypeReqDescription
incident_idstringyesThe incident's id.
page_idstringyesThe status page's id.

No output schema declared.

No examples provided.

instatus_get_maintenance ~73

Get a single scheduled maintenance by id — its full state including its update timeline and affected components. Instatus: GET /v1/{page_id}/maintenances/{maintenance_id}.

NameTypeReqDescription
maintenance_idstringyesThe maintenance's id.
page_idstringyesThe status page's id.

No output schema declared.

No examples provided.

instatus_list_components ~109

List a status page's components — id, name, description, status, order, showUptime, grouped, archived. The component ids are what you set impact on. Instatus: GET /v2/{page_id}/components.

NameTypeReqDescription
pageinteger–Page number to fetch (default 1).
page_idstringyesThe status page's id (from list_pages).
per_pageinteger–Items per page (default 50, max 100).

No output schema declared.

No examples provided.

instatus_list_incidents ~135

List a status page's incidents, most recent first — optionally filtered by status. Each incident: id, name, status, impact, affected components, updates, timestamps. Instatus: GET /v1/{page_id}/incidents.

NameTypeReqDescription
pageinteger–Page number to fetch (default 1).
page_idstringyesThe status page's id.
per_pageinteger–Items per page (default 50, max 100).
statusstring–Filter to incidents with this status (INVESTIGATING, IDENTIFIED, MONITORING, RESOLVED).

No output schema declared.

No examples provided.

instatus_list_maintenances ~103

List a status page's scheduled maintenances, most recent first — id, name, status, affected components, start/end, updates. Instatus: GET /v2/{page_id}/maintenances.

NameTypeReqDescription
pageinteger–Page number to fetch (default 1).
page_idstringyesThe status page's id.
per_pageinteger–Items per page (default 50, max 100).

No output schema declared.

No examples provided.

instatus_list_pages ~95

List all status pages on the account — each page's id, subdomain, name, status, url, custom domain, and timestamps. The page id is what every other tool takes as `page_id`. Instatus: GET /v2/pages.

NameTypeReqDescription
pageinteger–Page number to fetch (default 1).
per_pageinteger–Items per page (default 50, max 100).

No output schema declared.

No examples provided.

instatus_update_component ~214

UPDATES a component by id — this MODIFIES live status-page data. The key way to set a component's operational status (OPERATIONAL, UNDERMAINTENANCE, DEGRADEDPERFORMANCE, PARTIALOUTAGE, MAJOROUTAGE). Send only the fields you want to change. Instatus: PUT /v2/{page_id}/components/{component_id}. Returns the updated component.

NameTypeReqDescription
archivedboolean–Whether the component is archived (hidden).
component_idstringyesThe component's id to update.
descriptionstring–Free-form component description.
groupedboolean–Whether the component is displayed within a group.
namestring–Component name.
orderinteger–Display order of the component on the page.
page_idstringyesThe status page's id.
showUptimeboolean–Whether to show the uptime graph for this component.
statusstring–Operational status of the component.

No output schema declared.

No examples provided.

instatus_update_incident ~217

UPDATES an existing incident by id — this MODIFIES live status-page data and can notify subscribers (e.g. move it to MONITORING or RESOLVED). Send only the fields you want to change. Instatus: PUT /v1/{page_id}/incidents/{incident_id}. Returns the updated incident.

NameTypeReqDescription
componentsarray–Component ids affected by this incident.
incident_idstringyesThe incident's id to update.
messagestring–Incident update message (Markdown supported).
namestring–Incident title.
notifyboolean–Whether to notify subscribers about this update.
page_idstringyesThe status page's id.
shouldPublishboolean–Whether the incident should be published to the status page.
startedstring–ISO 8601 timestamp for when the incident started.
statusstring–Incident status.
statusesarray–Per-component impact — set each listed component's status for this event.

No output schema declared.

No examples provided.

instatus_update_maintenance ~215

UPDATES an existing scheduled maintenance by id — this MODIFIES live status-page data and can notify subscribers. Send only the fields you want to change. Instatus: PUT /v1/{page_id}/maintenances/{maintenance_id}. Returns the updated maintenance.

NameTypeReqDescription
componentsarray–Component ids affected by this maintenance.
durationinteger–Maintenance duration in minutes.
endstring–ISO 8601 timestamp for when the maintenance ends.
maintenance_idstringyesThe maintenance's id to update.
messagestring–Maintenance update message (Markdown supported).
namestring–Maintenance title.
notifyboolean–Whether to notify subscribers about this update.
page_idstringyesThe status page's id.
startstring–ISO 8601 timestamp for when the maintenance starts.
statusstring–Maintenance status.
statusesarray–Per-component impact — set each listed component's status for this event.

No output schema declared.

No examples provided.

Common questions

What is the io.usefulapi/instatus MCP server?

io.usefulapi/instatus is an MCP server listed in the public MCP registry as io.usefulapi/instatus. Manage status pages: components, incidents and maintenances; set live component status. This page covers its hosted endpoint (https://instatus.usefulapi.io/mcp).

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

io.usefulapi/instatus scores 73 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/instatus MCP server expose?

io.usefulapi/instatus exposes 14 tools: instatus_list_pages, instatus_list_components, instatus_get_component, instatus_list_incidents, instatus_get_incident, and 9 more. Their descriptions and schemas cost roughly 1,917 tokens of context every time the server is loaded.

Does the io.usefulapi/instatus MCP server require authentication?

Yes. io.usefulapi/instatus 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/instatus MCP server still maintained?

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