Skip to content
External endpointresponds

API Status Check

Check real-time uptime and incident status for 100+ APIs and cloud services.

Endpoint URL
https://apistatuscheck.com/api/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:00 AM UTC
Check
MCP initialize · 8s limit
Latency
215 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.shibley/apistatuscheck

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
apistatuscheck
Version
0.1.0
Capability keys
tools
Tool names
list_apis, search_apis, get_api_status, list_down_apis, get_uptime_history, get_incident_history, rank_reliability, list_categories
Instructions excerpt

Live and historical availability for public APIs and developer platforms. Use get_api_status when the user hits an error from a third-party API and you need to tell an outage apart from a bug in their own code. Statuses from list_apis and list_down_apis come from an hourly monitor and carry a timestamp; get_api_status probes the endpoint at call time. For past behaviour rather than the present, use get_incident_history (the vendor’s own published incidents) and rank_reliability (cross-vendor scorecard — incidents, downtime minutes and MTTR for several services at once, which no single vendor’s tooling can answer). Both report covered:false for services we hold no archive on; treat that as unknown, never as zero.

Reported Aug 17, 2026, 05:00 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 160ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 230ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 672ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 215ms