Live status probes plus published uptime and incident history for 280+ APIs and cloud services.
Scored across 8 tools
Each tool addresses a distinct concern: live probe, vendor incident history, uptime stats, API listing, categories, down APIs, reliability comparison, and search. No two tools overlap in purpose; even similar concepts like incident vs uptime history are clearly separated.
All tool names follow a consistent verb_noun pattern in snake_case: get_*, list_*, rank_*, search_*. The verbs are precise and the nouns are the resource types (api, incident, uptime, category, etc.).
8 tools is squarely in the ideal 3-15 range for a focused status-checking service. Each tool covers a necessary operation without bloat or redundancy.
The surface covers the full lifecycle: discovery (search_apis, list_categories), current status (get_api_status, list_down_apis), historical data (get_incident_history, get_uptime_history), and comparative analysis (rank_reliability). No obvious gaps; even edge cases like stale snapshots are handled via descriptions.
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.
Inputs: slug (required).
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.
Inputs: service (required), limit, window.
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%.
Inputs: slug (required), range.
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.
Inputs: limit, category.
Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis.
Inputs: no named parameters.
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.
Inputs: no named parameters.
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.
Inputs: services (required), window.
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.
Inputs: query (required), limit.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Live status, incidents and maintenance windows for 8,000+ cloud and SaaS status pages.
Real-time status & uptime monitoring for 294 popular APIs — is it down, and how reliable?
Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.
Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.
Add one secure layer between your agents and this server.
