API Status Check
io.github.shibley/apistatuscheck · v0.2.3
Live status probes plus published uptime and incident history for 280+ APIs and cloud services.
MCPremoteno credentials
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 8 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
A 87/100
What it does: 8 tools · 7 read, 0 write
Test call list_apis: worked (997 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +2
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: 0
- Safe test call: +20
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://apistatuscheck.com/api/mcpTools
8 tools listed at last check
list_apisList 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_apisFind 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_statusProbe 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_apisEverything 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_historyUptime 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_historyReal 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 Statuspagrank_reliabilityGiven 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 monitlist_categoriesCategory slugs and how many monitored APIs sit in each. Use the slugs with list_apis.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.shibley/apistatuscheck)