mcpbeat Sign in

API Status Check MCP Server

by shibley Your server? Claim it
not responding

API Status Check is listed as active in the registry but did not answer our last check. It exposes 8 tools. Last commit 9 Sep 2026.

Live status probes plus published uptime and incident history for 280+ APIs and cloud services.

Uptime history 91 days of history · worst day 0%
91 days agonow
2.2%
Uptime 24h
2 of 91 checks
8
Tools
read from the server
396 ms
Response time
average over 24h
1
Stars
last commit 9 Sep 2026

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 August 2026. No other catalogue keeps this.

9 Sep a tool description was rewritten list_apis
11 Aug 2 tools appeared get_incident_history, rank_reliability

API Status Check does not always answer

Over the last week it answered 12.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add apistatuscheck --transport http https://apistatuscheck.com/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://apistatuscheck.com/api/mcp
~/.codex/config.toml
[mcp_servers.apistatuscheck]
url = "https://apistatuscheck.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "apistatuscheck": {
      "url": "https://apistatuscheck.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "apistatuscheck": {
      "type": "http",
      "url": "https://apistatuscheck.com/api/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

apis
list_apis
List the APIs and developer platforms this service monitors, optionally filtered by category. Statuses come from the most recently published monitor snapshot, not a live probe, and can be up to a day old — check monitorCheckedAt, and call get_api_status when the caller needs the status right now.
search_apis
Find monitored APIs by name, slug, category or description. Use this to resolve a product name the user mentioned into the slug the other tools take.
api
get_api_status
Probe a monitored API endpoint at call time and return up/degraded/down with the response time. This is the tool to reach for when a user asks "is X down?" — it makes a real request rather than reading the hourly cache.
categories
list_categories
Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis.
down
list_down_apis
Everything the most recent monitor run found down or degraded, across all categories. Returns an empty list when the monitor snapshot is missing or stale — an empty list is therefore not proof that everything is healthy; check monitorLastRun.
incident
get_incident_history
Real incidents a vendor published on its own status page, newest first, with start/end times, duration, severity, affected components and a link to the vendor’s incident page. Use this for "has X been flaky lately?" — it is the vendor’s own record, not our probes. Services without a public Statuspage endpoint return covered:false rather than an empty list.
rank
rank_reliability
Given several service slugs, return a scorecard ranked worst-first: incident count, total downtime minutes, mean time to resolve, and the longest incident over a window. Use this to answer "which vendor in my stack is least reliable?" — it compares services across vendors, which a vendor’s own monitoring tool cannot. Services with no archive are listed separately as uncovered instead of being ranked as flawless.
uptime
get_uptime_history
Uptime percentages, response-time stats and recorded data points for one API over a time range. History is retained for 30 days; an API added recently will have few or no data points, which reads as null percentages rather than 100%.

Endpoints

URLTransportStateLatencyChecked
https://apistatuscheck.com/api/mcp streamable-http answering 31 ms 5 min ago

Alternatives to API Status Check

same job, measured the same way
Uptimepage
by uptimepage

Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.

41 tools answering
Downtester Status
by downtester

Live service status, active incidents, search, and outage history from Downtester.

answering
Statuser
by statuser-cloud

Monitor services, manage incidents and status pages in Statuser.cloud from your AI assistant.

116 installs/wk answering
ScaledPapers
by scaledpapers

Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.

34 tools answering
losclouds
by losclouds

Cloud and SaaS service status, plus your team's monitors, status pages, incidents, and alerts.

answering
StatusPal MCP by usefulapi
by usefulapi

Read status-page status, services, incidents and metrics; create, update and publish incidents.

11 tools answering
Openuptime
by openuptime

Manage uptime monitors, incidents and status pages from any MCP client.

answering
Pingoru status
by pingoru

Live status, incidents and maintenance windows for 8,000+ cloud and SaaS status pages.

answering

API Status Check — questions

Answers built from our own checks of this server.

What can API Status Check do?
It exposes 8 tools, read directly from the server on our last check. Among them: get_api_status, get_incident_history, get_uptime_history, list_apis, list_categories, list_down_apis and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is API Status Check working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 2 of 91 checks got a reply (2.2%), average response time 396 ms. The bar chart above shows every period we have measured.
The registry lists API Status Check as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect API Status Check?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does API Status Check need an API key?
No. API Status Check completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is API Status Check?
It answers our handshake in 396 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is API Status Check open source?
The code is open source: it is published under the MIT licence, written in TypeScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at apistatuscheck.com, which runs on its operator's own terms.