Vendor Status MCP server

vendor-status-mcp — 1,100+ SaaS status pages as an MCP server

1,127 vendor status pages mapped · 804 with a machine-readable feed · 15,418 incidents on record · polled every day · no API key · zero dependencies. (counts as of 2026-09-15 — datasetstatus returns today's.)*

Every SaaS and cloud vendor publishes a status page, and almost every one of them is on a different system — Atlassian Statuspage, Instatus, status.io, Better Stack, incident.io, or something home-grown. Vendor Status Watch keeps a living map of where those pages are, which ones expose JSON/RSS, and polls all 804 readable ones daily into one normalized incident history. This is that dataset wired into the Model Context Protocol, so Claude, Cursor, Continue or your own agent can ask questions like:

"Is Cloudflare having an incident right now?"

"Which of our vendors — Stripe, Twilio, Datadog, Auth0 — had incidents this month?"

"How long do GitHub incidents usually take to resolve?"

"Does Vendor X have an RSS or JSON status feed, and where is it?"

"What SaaS vendors are reporting a major outage today?"

Install

Nothing to build and nothing to install into your Python environment — the server is standard library only.

Claude Desktop / Claude Code / anything that reads an mcpServers block:

{
  "mcpServers": {
    "vendor-status": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/APVentureEngine/vendor-status-mcp", "vendor-status-mcp"]
    }
  }
}

Claude Code, one line:

claude mcp add vendor-status -- uvx --from git+https://github.com/APVentureEngine/vendor-status-mcp vendor-status-mcp

No uv? Clone and run it with plain Python:

git clone https://github.com/APVentureEngine/vendor-status-mcp && cd vendor-status-mcp
python3 -m vendor_status_mcp.server --selftest    # exercises every tool against live data

{
  "mcpServers": {
    "vendor-status": { "command": "python3", "args": ["-m", "vendor_status_mcp.server"], "cwd": "/path/to/vendor-status-mcp" }
  }
}

Tools

Every answer carries asof / checkedat and source. The states come from a daily poll, and every status answer says so in a caveat field rather than letting a model present yesterday's read as a live probe — when you need live, statusfeedurls hands you the vendor's own JSON. Where a vendor name is ambiguous (gitlab when only gitlabhost is in the map) the answer says "match": "fuzzy" and names the runner-up instead of guessing silently.

Why an MCP server and not just the JSON

Shortened. The full README is on GitHub.