API Status Check MCP Server
Related Servers
Alternatives to API Status Check MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLive operational status for 2,400+ major software services — AWS, GitHub, Stripe, OpenAI, Cloudflare, and more — pulled from each provider's official status page and returned as a normalised up / degraded / down result for any service you ask about.51MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to check real-time status, uptime, and incidents for 200+ popular APIs (Stripe, OpenAI, AWS, GitHub, Twilio, etc.) through read-only, no-authentication tools.-
- AlicenseNot gradedqualityBmaintenanceEnables checking real-time operational status of 75+ AI services (OpenAI, Anthropic, Cursor, etc.) through tools like check_ai_status and list_ai_services.MIT
- AlicenseAqualityDmaintenanceReal-time status monitoring, uptime tracking, incident history, and API pricing for 42+ AI tools including ChatGPT, Claude, Gemini, Cursor, GitHub Copilot, Perplexity, DeepSeek, and Groq. No API key required. Data updated every 5 minutes from independent monitoring infrastructure.749 npm1MIT

GetMonitor MCP Serverofficial
AlicenseCqualityBmaintenanceConnects AI assistants to GetMonitor status pages, monitors, incidents, and maintenance schedules via read-only tools.100189 npmApache 2.0- AlicenseAqualityCmaintenanceEnables checking real-time service outages and incidents from whatbroke.today, allowing users to ask about current downtime, service status, and incident details.532 npmMIT
TDQS
Scored across 5 tools
The tools have distinct purposes based on their names: checking categories, statuses, URLs, and listing APIs and categories. While 'check_category' and 'list_categories' might overlap slightly (both relate to categories), they appear to serve different functions (checking vs. listing), so ambiguity is minimal.
All tool names follow a consistent verb_noun pattern with 'check_' or 'list_' prefixes, using snake_case throughout. This makes the naming predictable and easy to understand, with no deviations in style.
With 5 tools, the count is well-scoped for an API status check server. It covers core operations like checking and listing without being overly sparse or bloated, fitting typical expectations for such a domain.
The tools cover checking and listing operations, but there are notable gaps for a full API status management system. For example, there are no tools for creating, updating, or deleting APIs or categories, which limits lifecycle coverage and could lead to dead ends in agent workflows.