# API Status Check (remote · apistatuscheck.com)

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

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `apistatuscheck.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/shibley-apistatuscheck/api-mcp.md), [page](https://verifymcp.io/servers/shibley-apistatuscheck/api-mcp)

## Channel facts

- Endpoint: `https://apistatuscheck.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 485 tokens (~80/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http shibley-apistatuscheck https://apistatuscheck.com/api/mcp
```

### Codex

```toml
[mcp_servers.shibley-apistatuscheck]
url = "https://apistatuscheck.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shibley-apistatuscheck": {
      "type": "remote",
      "url": "https://apistatuscheck.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shibley-apistatuscheck --url https://apistatuscheck.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  shibley-apistatuscheck:
    url: "https://apistatuscheck.com/api/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 67, +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.

### 2026-08-01 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-31 (score 66)

First indexed and scored.

## MCP tools (6)

### `list_apis` (~77 tokens)

List monitored APIs

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.

Input parameters:

- `category` (string): Category slug to filter by, e.g. "ai" — omit for all categories.
- `limit` (integer): Max results (default 25).

### `search_apis` (~73 tokens)

Search monitored 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.

Input parameters:

- `limit` (integer): Max results (default 25).
- `query` (string, required): Free-text query, e.g. "openai" or "payments".

### `get_api_status` (~82 tokens)

Check an API right now

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.

Input parameters:

- `slug` (string, required): API slug, e.g. "openai". Use search_apis to resolve a name.

### `list_down_apis` (~55 tokens)

List APIs currently down or degraded

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.

### `get_uptime_history` (~93 tokens)

Get retained 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%.

Input parameters:

- `range` (string): Window to return data points for (default 24h).
- `slug` (string, required): API slug, e.g. "openai".

### `list_categories` (~29 tokens)

List API categories

Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/shibley-apistatuscheck/api-mcp#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 67
- 2026-08-01: 66
- 2026-07-31: 66

## Links

- Remote endpoint: https://apistatuscheck.com/api/mcp
- Repository: https://github.com/shibley/apistatuscheck-mcp-server
- Website: https://apistatuscheck.com/
- Changelog RSS feed: https://verifymcp.io/servers/shibley-apistatuscheck/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/shibley-apistatuscheck/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/shibley-apistatuscheck/api-mcp