status-aggregator-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STATUS_AGG_URL | No | Override remote snapshot URL | |
| STATUS_AGG_LOCAL_ONLY | No | Skip remote fetch when set to 1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_servicesB | List monitored SaaS providers + last-known status. Filter by category or status. |
| get_statusB | Full status record for one service, with cited status-page URL. |
| get_incidents_todayC | Active incidents across all monitored services as of snapshot. |
| check_allB | Aggregate status counts. Quick health summary for agents deciding whether to retry/fallback. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.