vendor-status-mcp

Purpose: Checking the current status and incident history of many SaaS and cloud vendors without manually visiting each status page.

Inferred · not functionally tested

Audience: developers and DevOps teams

Inferred · not functionally tested

Functions: monitoring

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: WEB · deployment: browser, self_hosted, cli, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

vendor-status-mcp sits in PulseGate's Frameworks & runtimes category. Inferred · not functionally tested: It focuses on checking the current status and incident history of many SaaS and cloud vendors without manually visiting each status page. Inferred · not functionally tested: It is built as an open-source project for developers and DevOps teams. Basis unknown · not verified: The project is open source (Open Source). Basis unknown · not verified: It runs on the web, the command line, and API, and it can be self-hosted.

Behind vendor-status-mcp is APVentureEngine. Inferred · not functionally tested: Key capabilities include current status checks, incident history, and resolution times. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.