Skip to main content
Glama
robinmordasiewicz

F5 Cloud Status MCP Server

Related Servers

Alternatives to F5 Cloud Status MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      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
      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
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with F5 devices through the iControl REST API to manage objects like virtual servers, pools, iRules, and profiles. It provides comprehensive tools for listing, creating, updating, and deleting F5 configurations via natural language interfaces.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables management of F5 BIG-IP load balancers through secure authentication and configuration queries. Supports multiple devices with token caching, allowing users to list virtual servers and device configurations through natural language.
      -
    • A
      license
      C
      quality
      B
      maintenance
      Monitor 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.
      5
      8 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      -

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: get-component targets a specific item, get-components lists all, get-incidents focuses on incidents, get-maintenance on maintenance, get-overall on overall status, and search enables keyword queries. The descriptions reinforce these boundaries, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with the prefix 'f5-status-', such as 'f5-status-get-component' and 'f5-status-search'. This uniformity enhances readability and predictability, with no deviations in style or convention.

    Tool Count5/5

    With 6 tools, the server is well-scoped for monitoring F5 Cloud status, covering key aspects like components, incidents, maintenance, overall status, and search. Each tool earns its place without feeling excessive or insufficient for the domain.

    Completeness5/5

    The tool set provides complete coverage for status monitoring, including CRUD-like operations (get/list for components, incidents, maintenance) and additional utilities (overall status and search). There are no obvious gaps, enabling agents to handle typical workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues