Skip to main content
Glama

Server Details

Live cloud/SaaS outages, provider reliability and exploited CVEs from official status pages and CISA

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.2% over 44 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation4/5

The three deterministic tools have clearly distinct domains: incidents, reliability, and exploited vulnerabilities. The 'answer' tool overlaps with all of them, but its role as a fallback for free-form questions is explicit and the descriptions instruct agents to prefer deterministic tools, reducing ambiguity.

Naming Consistency3/5

Names are all lowercase snake_case, but the pattern is mixed: 'answer' and 'list_active_incidents' use verbs, while 'exploited_vulnerabilities' and 'provider_reliability' are noun phrases. It is readable and not chaotic, but not a consistent verb_noun convention.

Tool Count4/5

Four tools is a reasonable size for a niche outage-monitoring server. Each deterministic tool covers a core need and the LLM-based 'answer' fills gaps, though the server could arguably include a couple more specific status tools without feeling bloated.

Completeness4/5

The set covers active incidents, provider reliability, exploited vulnerabilities, and general Q&A, which addresses the main use cases for a live monitor. Missing features like scheduled maintenance or historical incident comparisons are workaround-able via the 'answer' tool, so there are no critical dead ends.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updates
    • First observedanswer
    • First observedexploited_vulnerabilities
    • First observedlist_active_incidents
    • First observedprovider_reliability

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    Live 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.
    5
    13 npm
    1
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables querying the current state, incident history, resolution times, and feed URLs for over 1,100 SaaS/cloud vendor status pages.
    7
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to check the live operational status of hundreds of cloud, SaaS and AI providers, returning current state, affected components and active incidents for a named stack so agents can tell a vendor outage apart from their own broken code. It answers from a continuously polled local database, so agents can query stacks, list degraded providers, and review incident history without calling vendor status pages.
    143 npm
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Provides read-only access to a live, sourced feed of publicly reported breaches, ransomware claims, exploited CVEs, malicious packages and connectivity drops, each tagged with an honest status. Enables agents to check whether a user's software stack is affected and retrieve plain-text fix runbooks for one-click remediation.
    120
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources