Upstream
Related Servers
Alternatives to Upstream
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceLive 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.5510 npm1MIT
- 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.746 npm1MIT
- FlicenseNot gradedqualityBmaintenanceProvides real-time AI infrastructure data including LLM costs, model benchmarks, API deprecations, quality scores, and agent spend tracking. Supports authentication, rate limiting, x402 micropayments, and Stripe billing.-
- AlicenseNot 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.MIT
- AlicenseBqualityBmaintenanceal-time AI ecosystem intelligence for agents: 1,250+ classified AI security incidents, API pricing for 26 models across 7 providers, GPU cloud pricing, live provider status and cross-signal company analysis. No API key required.11MIT
- 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.510 npm1MIT
TDQS
Scored across 5 tools
The two check_* tools cleanly split provider-level health from model-level lifecycle, and list_providers is clearly the index helper for check_api_status. The main overlap is between list_recent_api_changes and get_digest, which both surface incidents/deprecations; the descriptions distinguish them (on-demand change feed vs once-a-day catch-up), so confusion is minor.
All names are snake_case verb_noun, with aliases documented (get_status, get_model, get_changes). Three verb families appear (check_, list_, get_), which is readable and mostly predictable, though not a single uniform verb pattern.
Five tools is a tight, well-scoped surface for an API/model monitoring service: status check, deprecation check, provider index, change feed, and digest. Each tool earns its place with no redundancy bloat.
Provider health, model deprecation, the provider index, recent changes and a daily digest cover the core monitoring lifecycle including lookups and alerts. A minor gap is the absence of a dedicated query for the MCP-server breaking changes mentioned in the digest, forcing agents to use the generic change feed.