# API Status Check

- Registry name: `io.github.shibley/apistatuscheck` · version 0.2.3
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.shibley%2Fapistatuscheck
- Server page: https://mcpstation.net/s/io.github.shibley--apistatuscheck.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://apistatuscheck.com/api/mcp`

## Tools (as reported by the server, not verified)

- `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.
- `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.
- `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.
- `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%.
- `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 Statuspag
- `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 monit
- `list\_categories`: Category slugs and how many monitored APIs sit in each. Use the slugs with list\_apis.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html