MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

Statuspage MCP by usefulapi

By usefulapi.io Verified namespace

Read pages, components, incidents and maintenances; create and update incidents in Statuspage.

WebsiteSource code
Connect to Statuspage MCP by usefulapi
Checks passed
12 / 22

2 failed · 8 not measured

Median response
62 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
15

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Outdated check

Last connection measurement is over 24 hours old. Current availability is unknown.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
220
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 62 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name statuspage-mcp.

  • Pass
    Lists tools

    tools/list returned 15 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 62 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 62 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Fail
    Parameters documented

    37 of 50 parameters have a description (74%). The bar is 80%.

  • Fail
    Safety hints

    1 tools set neither readOnlyHint nor destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-10T23:34:58.50946Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using Statuspage MCP by usefulapi

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http statuspage-mcp-by-usefulapi https://statuspage.usefulapi.io/mcp

Capabilities

Tools 15

statuspage_count_subscribers

Count the subscribers of a page by type (email, sms, webhook and others). API: GET /pages/{page_id}/subscribers/count.

Discovered
statuspage_create_incident

WRITE, public. Create a real-time incident on the live status page. It is visible to visitors. With deliver_notifications true (the default of Statuspage) it also sends messages to subscribers. A second call creates a second incident. API: POST /pages/{page_id}/incidents.

Discovered
statuspage_get_component

Get one component with its status, group and description. API: GET /pages/{page_id}/components/{component_id}.

Discovered
statuspage_get_component_uptime

Get uptime data for one component over a date range (default: the last 90 days). Dates are ISO 8601. API: GET /pages/{page_id}/components/{component_id}/uptime.

Discovered
statuspage_get_incident

Get one incident with its full update timeline and affected components. API: GET /pages/{page_id}/incidents/{incident_id}.

Discovered
statuspage_get_page

Get the profile of one status page (name, subdomain, domain, time zone, notification settings). API: GET /pages/{page_id}.

Discovered
statuspage_list_component_groups

List the component groups of a page. API: GET /pages/{page_id}/component-groups.

Discovered
statuspage_list_components

List the components of a page with their current status (operational, degraded_performance, partial_outage, major_outage, under_maintenance). API: GET /pages/{page_id}/components.

Discovered
statuspage_list_incidents

List incidents of a page, newest first. Use q to search by name, status or impact text. API: GET /pages/{page_id}/incidents.

Discovered
statuspage_list_maintenances

List scheduled maintenances of a page. kind: scheduled (all planned), upcoming (not started) or active (in progress). API: GET /pages/{page_id}/incidents/{scheduled|upcoming|active_maintenance}.

Discovered
statuspage_list_metrics

List the metrics shown on a page (for example response time). API: GET /pages/{page_id}/metrics.

Discovered
statuspage_list_pages

List the status pages the API key can see, with ids, names and subdomains. Start here to get a page_id. API: GET /pages.

Discovered
statuspage_list_unresolved_incidents

List incidents that are not resolved yet (investigating, identified, monitoring). API: GET /pages/{page_id}/incidents/unresolved.

Discovered
statuspage_update_component_status

WRITE, public. Set the status of one component on the live status page. Visitors see the change at once. API: PATCH /pages/{page_id}/components/{component_id}.

Discovered
statuspage_update_incident

WRITE, public. Post a new update on an incident: change its status, add update text, or set the status of components. Each call with body adds a new timeline entry and can notify subscribers, so do not repeat it. Setting status resolved closes the incident. API: PATCH /pages/{page_id}/incidents/{incident_id}.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected62 ms15

Related servers

All alternatives

Same function and industry, ranked by checks passed then median latency.

Explore alternatives to Statuspage MCP by usefulapi