status-aggregator

io.github.weiseerPublished by GitHub account weiseerv0.1.2Updated Oct 24, 2026

Cross-vendor SaaS status aggregator for AI agents (Anthropic/OpenAI/AWS/GH/Stripe/CF).

The publisher's own server: status.live national parks

Overview

AI-generated overview

A local stdio MCP server that aggregates the status pages of 14+ SaaS providers so an assistant can check outages and incidents in one call.

What you can do
List monitored providers with their last-known status and get full status for one provider with a cited status-page URL. Retrieve active incidents across all providers for the day. Get a quick health summary with counts by status. Results are pre-normalized across vendors, so the assistant avoids fetching each status page itself.
When to use it
Useful when an assistant needs to decide whether to retry, fall back, or explain a failure that may come from a third-party SaaS dependency such as a model provider, cloud host, or payment API.
Requirements
Runs locally over stdio, installed from the npm package @weiseer/status-aggregator-mcp (Node.js and npx). No authentication is declared. It fetches remote status snapshots unless STATUS_AGG_LOCAL_ONLY is set; STATUS_AGG_URL can override the snapshot URL. Desktop client only.
Before you install
By default it fetches a remote snapshot, so status queries leave the machine; set STATUS_AGG_LOCAL_ONLY to skip that. STATUS_AGG_URL lets you point it at a different snapshot source, so only use a URL you trust. The README is framed as a probe and lists related services, so treat its performance and cost claims as unverified.

Installation

In SourceWeft

  1. Open status-aggregator in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@weiseer/status-aggregator-mcp

Cross-vendor SaaS status as a stdio MCP server. For AI agents deciding retry/fallback.

Probe P-003 by weiseer.

What it does

Aggregates the status pages of 14+ SaaS providers AI agents depend on (Anthropic, OpenAI, Google AI, Mistral, GitHub, npm, Cloudflare, AWS, Vercel, Netlify, Render, Stripe, Algolia, Linear) into one MCP server.

Your agent can:

  • list_services — list monitored providers + last-known status
  • get_status — full status for one provider with cited status-page URL
  • get_incidents_today — active incidents across all
  • check_all — quick health summary (counts by status)

Why use this instead of your agent fetching each status page

Agent DIY (per call)status-aggregator
Status pages to fetch14 individual API calls1 MCP call
Token cost$0.05-0.15$0 free / $0.00005 paid
Latency3-8 seconds<100ms
Schema normalizationPer-vendor parsingPre-normalized

Install

bash
npm install -g @weiseer/status-aggregator-mcp

Use with Claude Desktop / Cursor / Cline / Continue / Windsurf

json
{  "mcpServers": {    "status-aggregator": {      "command": "npx",      "args": ["-y", "@weiseer/status-aggregator-mcp"]    }  }}

Environment

  • STATUS_AGG_URL — override remote snapshot URL
  • STATUS_AGG_LOCAL_ONLY=1 — skip remote fetch

Related weiseer services

  • @weiseer/llm-oracle-mcp — LLM pricing + availability oracle
  • @weiseer/bounty-mcp — live coding-bounty deal-flow
  • @weiseer/api-changelog-mcp — SDK breaking-change tracker
  • github.com/weiseer — all weiseer services

License

Apache-2.0

Source: README.md at commit f165ecd

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Status integrations