API Status Check
REMOTE · APISTATUSCHECK.COM · SCANNED AUG 3
Check real-time uptime and incident status for 285 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 →
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 6 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 485 tokens (~80/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · apistatuscheck.com
claude mcp add --transport http shibley-apistatuscheck 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": {
"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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Jul 26 66
First indexed and scored.
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 3 Aug 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 |
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 |
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.
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_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 ~77
List the APIs and developer platforms this service monitors, optionally filtered by category. Statuses are from the most recent hourly monitor run, not a live probe.
| 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.
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.