Skip to main content
Glama
vendor-status

vendor-status

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 — dataset_status 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" }
  }
}

Related MCP server: StatusCraft

Tools

Tool

What it answers

find_vendor

Resolve a name, slug or status-page domain to its map entry: status page URL, platform, whether a machine-readable feed exists, and its state in the newest poll.

vendor_status

One vendor's state from the newest daily poll — ok / degraded / partial / major / maintenance / unknown — with the vendor's own status line, open-incident count and the poll timestamp.

vendors_down_now

Every vendor that was not fully operational in the newest poll, worst first, plus counts by state across all 804 polled vendors.

vendor_incidents

One vendor's incident history as its page posted it: title, state, impact, start/resolve times, latest update, link. Filter by date and state.

vendor_resolution_times

Median, 90th percentile, over-24h count and the longest incident on record, from the vendor's own posted start and resolve timestamps.

status_feed_urls

The summary JSON, incidents JSON, RSS and Atom endpoints for one vendor's page, by platform — so a script can poll it directly with no key.

dataset_status

Vendors mapped, feeds readable, incidents on record and in the last 30 days, platform breakdown, cadence, license, bulk downloads.

Every answer carries as_of / checked_at 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, status_feed_urls 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

The JSON is right there and it is free — take it. This exists for the case where a model needs one specific answer: the map is 160 KB and each vendor's history is another file, so the tools do the lookup, the filtering and the percentile arithmetic locally and an agent spends a few hundred tokens instead of a context window.

The map is the part you cannot get from any one vendor. Nobody publishes "here is where every SaaS status page lives and which of them speak JSON" — it has to be discovered, re-probed when pages move, and pruned when they die, every day. find_vendor and status_feed_urls are that map, and the daily rebuild is what keeps them true.

Caching and network

Tools read the free public Vendor Status Watch endpoints over HTTPS and cache them on disk (~/.cache/vendor-status-mcp, override with VENDOR_STATUS_MCP_CACHE) with ETag revalidation, so ten tool calls in a row make at most one request per file per hour (VENDOR_STATUS_MCP_TTL, seconds). If the network is down and a cached copy exists, the cached copy is served and its own as_of tells you how old it is.

There is no key, no signup, no rate limit and no telemetry — this server sends nothing anywhere except plain GETs for public files.

Data, license, attribution

Data is compiled from vendors' own public status pages and released under CC BY 4.0 — credit "Vendor Status Watch" and link back. This server's code is MIT. Not affiliated with any vendor or status-page platform; each vendor's own page is the authority. "Resolution time" is the gap between a vendor's own posted start and resolve timestamps — not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse than one that posts nothing.

The one paid thing

Everything above is free and stays free, and so is the GitHub Actions template that alerts your Slack or Discord when a vendor you depend on breaks. If you would rather not run Actions yourself, the same alerts as a hosted service are $49 for 12 months, with a free 30-day trial and no card. It is the only thing here that costs money.

Bugs, a vendor missing from the map, a tool you want: open an issue.

Available Tools

7 tools
dataset_statusA

Coverage and freshness of the underlying dataset: vendors mapped, how many have machine-readable feeds, incidents on record, incidents in the last 30 days, platform breakdown, poll cadence, license and bulk downloads.

Inputs: no named parameters.

find_vendorA

Resolve a SaaS/cloud vendor by name, slug or status-page domain to its entry in the 1,100+ vendor status-page map: status page URL, platform (Statuspage, Instatus, status.io, Better Stack, ...), whether a machine-readable feed exists, and its state in the newest poll. Use this first when unsure of the exact vendor slug.

Inputs: query (required), limit.

status_feed_urlsA

The machine-readable endpoints for one vendor's status page — summary JSON, incidents JSON, RSS and Atom where the platform provides them — so an agent or a script can poll the vendor directly without a key. Also returns this dataset's normalized history JSON for the vendor.

Inputs: vendor (required).

vendor_incidentsA

One vendor's incident history as its status page posted it: title, state, impact, start/resolve timestamps, latest update text and the incident URL, newest first. Histories go back weeks to years depending on what the vendor's page exposes.

Inputs: vendor (required), limit, since, state.

vendor_resolution_timesA

How long one vendor's incidents take to be declared resolved: median, 90th percentile, count over 24h and the longest on record, computed from the vendor's own posted start and resolve timestamps (maintenance and inferred resolutions excluded). Not an uptime or SLA number.

Inputs: vendor (required).

vendors_down_nowA

Every vendor that was NOT fully operational in the newest poll, worst first (major, partial, degraded, then maintenance), with counts by state across all polled vendors. Use for 'which SaaS vendors have incidents right now'.

Inputs: limit, state, include_unknown, include_maintenance.

vendor_statusA

Current state of one vendor from the newest daily poll: ok / degraded / partial / major / maintenance / unknown, the vendor's own status line, open incident count and the poll timestamp. Says plainly that it is a daily poll, not a live probe.

Inputs: vendor (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    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

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      C
      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
      1
      MIT
    • 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
      1
      MIT
    • 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.
      71 npm
      MIT