API Status Check MCP
Hosted, public real-time API uptime probes, incident history, and vendor reliability comparisons across 285 APIs in 30 categories.
About this Server
API Status Check MCP (`apistatuscheck`) provides AI agents with hosted, unauthenticated live uptime probes and incident history across 285 APIs in 30 categories. Instead of hallucinating status from outdated training data or parsing complex status pages, agents can run direct live probes, inspect 30-day uptime metrics, list degraded services, and compare vendor reliability with real response times and timestamps.
Direct low-latency RPC protocol communication with structured JSON schemas.
Restricted capability bounds to prevent accidental modifications or leakage.
Security & Best Practices
When to Use (and When Not To)
- •Verifying whether an external cloud API (OpenAI, Stripe, GitHub, AWS) is experiencing an active outage
- •Triaging webhook delivery failures or intermittent 500/502 gateway errors during development
- •Comparing reliability metrics across competing SaaS or infrastructure APIs before adoption
- •Kubernetes cluster internal pod troubleshooting and kubectl rollout scaling (use Kubernetes MCP instead)
- •Postman workspace collections and environment variable testing (use Postman MCP instead)
- •Reverse engineering binary and JavaScript Electron bundles (use REA MCP instead)
Install & Setup
claude mcp add --transport http apistatuscheck https://apistatuscheck.com/api/mcpExposed Tools & Endpoints
8 toolsFunctions your AI agent can invoke via this Model Context Protocol server
Probes an API endpoint in real-time returning up/degraded/down status, live response time ms, and hourly monitor status.
Searches the 285 monitored APIs by product name, category, or description to resolve its canonical slug.
Lists all monitored APIs in the catalog, optionally filtered by one of the 30 category slugs.
Lists all APIs currently marked as down or degraded by the latest hourly monitor sweep across all categories.
Retrieves 24h, 7d, or 30d uptime percentages, response-time stats, and historical latency data points.
Fetches vendor-published status incidents including start/end timestamps, severity, and affected components.
Compares and ranks multiple vendor APIs by downtime minutes, incident count, and MTTR.
Lists all 30 monitored API categories with total service counts in each.