status-aggregator-mcp
Aggregates the status page of Algolia to provide real-time health updates and incident alerts.
Aggregates the status page of Cloudflare to provide real-time health updates and incident alerts.
Aggregates the status page of GitHub to provide real-time health updates and incident alerts.
Aggregates the status page of Google AI to provide real-time health updates and incident alerts.
Aggregates the status page of Linear to provide real-time health updates and incident alerts.
Aggregates the status page of Netlify to provide real-time health updates and incident alerts.
Aggregates the status page of npm to provide real-time health updates and incident alerts.
Aggregates the status page of OpenAI to provide real-time health updates and incident alerts.
Aggregates the status page of Render to provide real-time health updates and incident alerts.
Aggregates the status page of Stripe to provide real-time health updates and incident alerts.
Aggregates the status page of Vercel to provide real-time health updates and incident alerts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@status-aggregator-mcp check status of OpenAI and GitHub"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@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 statusget_status— full status for one provider with cited status-page URLget_incidents_today— active incidents across allcheck_all— quick health summary (counts by status)
Related MCP server: Agent Aggregator
Why use this instead of your agent fetching each status page
Agent DIY (per call) | status-aggregator | |
Status pages to fetch | 14 individual API calls | 1 MCP call |
Token cost | $0.05-0.15 | $0 free / $0.00005 paid |
Latency | 3-8 seconds | <100ms |
Schema normalization | Per-vendor parsing | Pre-normalized |
Install
npm install -g @weiseer/status-aggregator-mcpUse with Claude Desktop / Cursor / Cline / Continue / Windsurf
{
"mcpServers": {
"status-aggregator": {
"command": "npx",
"args": ["-y", "@weiseer/status-aggregator-mcp"]
}
}
}Environment
STATUS_AGG_URL— override remote snapshot URLSTATUS_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 trackergithub.com/weiseer — all weiseer services
License
Apache-2.0
Available Tools
4 toolscheck_allB
Aggregate status counts. Quick health summary for agents deciding whether to retry/fallback.
Inputs: category.
get_incidents_todayC
Active incidents across all monitored services as of snapshot.
Inputs: no named parameters.
get_statusB
Full status record for one service, with cited status-page URL.
Inputs: service_id (required).
list_servicesB
List monitored SaaS providers + last-known status. Filter by category or status.
Inputs: category, current_status.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a distinct purpose: listing services, getting detailed status, fetching incidents, and aggregate summary. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern (list_services, get_status, get_incidents_today, check_all). The pattern is uniform and predictable.
With 4 tools, the surface is well-scoped for a status aggregator. Each tool covers a necessary operation without redundancy.
Core operations are present: listing, detail, incidents, and summary. Missing historical incident queries or subscription capabilities, but reasonable for a basic aggregator.
Related MCP Connectors
MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents.
Manage uptime monitors, incidents and status pages from any MCP client.
Read-only MCP server for AIStatusDashboard status, incidents, metrics, and fallback recommendations.
All-in-one monitoring for uptime, servers, incidents & status pages. Manage it all from AI chat.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables unified management of maintenance windows and incidents across Atlassian Statuspage and Uptime Kuma. It allows AI assistants to schedule maintenance, update service statuses, and list monitors through a single MCP-compatible interface.9MIT
- AlicenseAqualityDmaintenanceAggregates tools from multiple MCP servers, acting as a proxy to provide unified access to various AI agents and tools.1020 npm3MIT

@pipeworx/statuspageofficial
AlicenseNot gradedqualityCmaintenanceMCP 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 npmMIT- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query and monitor service status, latency, and performance through configurable checks (HTTP, TCP, SSL, keyword, JSON-path) and exposes tools for listing services, retrieving metrics, and running on-demand checks.Apache 2.0