Skip to main content
Glama
APVentureEngine

vendor-status

by APVentureEngine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to vendor-status

No user-submitted related servers found.

    Related Servers

    • StatusCraft

      jabbawocky
      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
    • @pipeworx/statuspage by pipeworx-io

      @pipeworx/statuspageofficial

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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.
      2 npm
      MIT

    • APIzone

      HappyMealSteak
      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.
      -

    • API Status Check MCP Server

      shibley
      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
      12 npm
      1
      MIT
    • StackWitness by stackwitness

      StackWitnessofficial

      stackwitness
      F
      license
      Not graded
      quality
      C
      maintenance
      Let agents read and manage your org’s independent monitors, incidents, status pages, and alerts (honest measured state, no false greens).
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct concern: single-vendor current status, vendor lookup, aggregate outages, incident history, resolution metrics, feed endpoints, and dataset metadata. Even the incident-related tools are clearly separated by current state vs. historical detail.

    Naming Consistency4/5

    Most tools follow a consistent snake_case noun-phrase pattern with a vendor_ prefix, making the set easy to scan. find_vendor is a verb-led deviation)Skip, and vendors_down_now uses a different structure, but these are minor and do not undermine predictability.

    Tool Count5/5

    Seven tools is well-scoped for a read-only vendor status dataset. Each tool covers a distinct part of the workflow without unnecessary duplication or bloat.

    Completeness4/5

    The set covers lookup, current status, affected vendors, incident history, resolution statistics, direct feed access, and dataset health. A bulk 'all vendor statuses' or cross-vendor incident search is missing, but core agent workflows are well supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources