StatusCraft
Related Servers
Alternatives to StatusCraft
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceMonitor the real-time status of 200+ popular APIs and services. Check if services like GitHub, Stripe, AWS, and Slack are experiencing outages or degraded performance directly from your AI assistant.58 npm1MIT
- AlicenseAqualityBmaintenanceEnables querying the current state, incident history, resolution times, and feed URLs for over 1,100 SaaS/cloud vendor status pages.7MIT
- 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.735 npm1MIT

@pipeworx/statuspageofficial
AlicenseNot gradedqualityBmaintenanceMCP server that answers service status and uptime questions by reading Atlassian Statuspage feeds from hundreds of vendors, with keyless access and tools for checking status, incidents, and vendor listings.0MIT
TDQS
Scored across 5 tools
Tools are mostly distinct. get_status, get_all_status, and check_multiple all retrieve statuses but with different scopes (single, all, custom list). Descriptions clarify the differences, though an agent might still confuse get_all_status and check_multiple.
Naming follows verb_noun pattern generally, but verbs are inconsistent (check, get, list, refresh). 'check_multiple' uses an adjective instead of a noun, breaking the pattern. Overall readable but not fully consistent.
5 tools is well-scoped for a service status checking server. Each tool serves a clear purpose without excess, covering listing, single/get-all/custom status checks, and cache refresh.
Covers core needs: discover services, fetch status (individual, all, custom list), and force refresh. Minor gaps like historical statuses or adding/removing services are absent but not critical for the stated purpose.