API Status Check
REMOTE · APISTATUSCHECK.COM · SCANNED SEP 21
Live status probes plus published uptime and incident history for 280+ APIs and cloud services.
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 → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 916 tokens (~114/item across 8 items; 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the API Status Check MCP server?
API Status Check is a hosted endpoint at https://apistatuscheck.com/api/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 · apistatuscheck.com
claude mcp add --transport http shibley-apistatuscheck 'https://apistatuscheck.com/api/mcp'
{
"mcpServers": {
"shibley-apistatuscheck": {
"url": "https://apistatuscheck.com/api/mcp"
}
}
} {
"servers": {
"shibley-apistatuscheck": {
"type": "http",
"url": "https://apistatuscheck.com/api/mcp"
}
}
} [mcp_servers.shibley-apistatuscheck] url = "https://apistatuscheck.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shibley-apistatuscheck": {
"type": "remote",
"url": "https://apistatuscheck.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add shibley-apistatuscheck --url 'https://apistatuscheck.com/api/mcp' --transport streamable-http
mcp_servers:
shibley-apistatuscheck:
url: "https://apistatuscheck.com/api/mcp" {
"McpServers": {
"shibley-apistatuscheck": {
"Transport": "http",
"Url": "https://apistatuscheck.com/api/mcp"
}
}
} assistant mcp add shibley-apistatuscheck -t streamable-http -u 'https://apistatuscheck.com/api/mcp'
{
"mcpServers": {
"shibley-apistatuscheck": {
"type": "http",
"url": "https://apistatuscheck.com/api/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.
- 9 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_apis” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- 30 Aug 26 0
- Stability: 0.97 → pass security
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 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
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 11 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
- 1 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
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 21 Sept 2026 · Probed https://apistatuscheck.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=apistatuscheck.com | CN=YR2,O=Let's Encrypt,C=US | 23 Jul 2026 | 21 Oct 2026 | RSA 2048 | SHA256-RSA | 6a225db1d2993ac4475f1b828197c33048c |
| SANs: apistatuscheck.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of apistatuscheck.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| apistatuscheck.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://apistatuscheck.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://apistatuscheck.com/api/mcp | HTTPS enforced | 308 | https://apistatuscheck.com/api/mcp |
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 →
get_api_status Check an API right now ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | API slug, e.g. "openai". Use search_apis to resolve a name. |
No output schema declared.
No examples provided.
get_incident_history Get a service’s published incident history ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max incidents (default 25). |
| service | string | yes | API slug, e.g. "openai". Use search_apis to resolve a name. |
| window | string | – | Time window: 7d, 30d, 90d, 180d, 365d, all (default 90d). |
No output schema declared.
No examples provided.
get_uptime_history Get retained uptime history ~93
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%.
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | Window to return data points for (default 24h). |
| slug | string | yes | API slug, e.g. "openai". |
No output schema declared.
No examples provided.
list_apis List monitored APIs ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug to filter by, e.g. "ai" — omit for all categories. |
| limit | integer | – | Max results (default 25). |
No output schema declared.
No examples provided.
list_categories List API categories ~29
Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_down_apis List APIs currently down or degraded ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rank_reliability Rank vendors by reliability ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| services | array | yes | API slugs to compare, e.g. ["openai","anthropic","vercel"]. |
| window | string | – | Time window: 7d, 30d, 90d, 180d, 365d, all (default 90d). |
No output schema declared.
No examples provided.
search_apis Search monitored APIs ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 25). |
| query | string | yes | Free-text query, e.g. "openai" or "payments". |
No output schema declared.
No examples provided.
What is the API Status Check MCP server?
API Status Check is an MCP server listed in the public MCP registry as io.github.shibley/apistatuscheck. Live status probes plus published uptime and incident history for 280+ APIs and cloud services. This page covers its hosted endpoint (https://apistatuscheck.com/api/mcp).
Is the API Status Check MCP server safe to use?
API Status Check scores 82 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 API Status Check MCP server expose?
API Status Check exposes 8 tools: list_apis, search_apis, get_api_status, list_down_apis, get_uptime_history, and 3 more. Their descriptions and schemas cost roughly 747 tokens of context every time the server is loaded.
Does the API Status Check MCP server require authentication?
No. We connected to API Status Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the API Status Check MCP server still maintained?
API Status Check is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.