Live status, incidents and maintenance windows for 8,000+ cloud and SaaS status pages.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Pinpoint the status of one component by name (case-insensitive substring match). Returns an error when the name matches multiple components — the agent should ask the user to disambiguate. Slug accepts shorthand / typos via fuzzy fallback.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pinpoint the status of one component by name (case-insensitive substring match). Returns an error when the name matches multiple components — the agent should ask the user to disambiguate. Slug accepts shorthand / typos via fuzzy fallback.
| Argument | Type | Description |
|---|---|---|
| slug* | string | |
| component* | string |
{
"type": "object",
"title": "component_statusArguments",
"required": [
"slug",
"component"
],
"properties": {
"slug": {
"type": "string",
"title": "Slug"
},
"component": {
"type": "string",
"title": "Component"
}
}
}Full record for one incident or maintenance: current status, impact, start / resolve times and duration, scheduled window (for maintenance), affected components, the vendor's link, the Pingoru page (pingoru_url) and every status update with its timestamp. Use to summarise 'what happened during the May 3 outage'. Covers the last 30 days plus anything still open. Slug accepts shorthand / typos via fuzzy fallback.
| Argument | Type | Description |
|---|---|---|
| slug* | string | |
| incident_id* | integer |
{
"type": "object",
"title": "incident_detailArguments",
"required": [
"slug",
"incident_id"
],
"properties": {
"slug": {
"type": "string",
"title": "Slug"
},
"incident_id": {
"type": "integer",
"title": "Incident Id"
}
}
}List a provider's components with current status. Use to drill into 'which AWS components are broken right now?' style questions. Set only_problematic=true to filter out the operational ones. Slug accepts shorthand / typos via fuzzy fallback (see provider_status docstring).
| Argument | Type | Description |
|---|---|---|
| slug* | string | |
| only_problematic | boolean |
{
"type": "object",
"title": "provider_componentsArguments",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"title": "Slug"
},
"only_problematic": {
"type": "boolean",
"title": "Only Problematic",
"default": false
}
}
}Recent incident history for a provider (days clamped to 1-30), plus a separate `maintenance` list: maintenance scheduled or held in the window, including upcoming windows. Each item has its current status (investigating / identified / monitoring / resolved, scheduled / in_progress / completed), start and resolve times, duration, impact, affected components, the vendor's link and the Pingoru page (pingoru_url). Pass component (substring match on component name) to scope to one component. Slug accepts shorthand / typos via fuzzy fallback.
| Argument | Type | Description |
|---|---|---|
| days | integer | |
| slug* | string | |
| component | any |
{
"type": "object",
"title": "provider_incidentsArguments",
"required": [
"slug"
],
"properties": {
"days": {
"type": "integer",
"title": "Days",
"default": 7
},
"slug": {
"type": "string",
"title": "Slug"
},
"component": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Component",
"default": null
}
}
}Get the current status and any active incidents for a status-page vendor. Use when the user asks 'is X down?' or 'is X having problems?'. slug: Provider slug or human name. Exact slug ('github', 'amazon-web-services', 'google-cloud') is matched first; on miss we fall back to a search lookup so common shorthands ('aws', 'gcp', 'github actions') and minor typos still resolve. The response includes `matched_via: 'fuzzy'` and the original query when fuzzy fallback was used so the agent can confirm with the user.
| Argument | Type | Description |
|---|---|---|
| slug* | string |
{
"type": "object",
"title": "provider_statusArguments",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"title": "Slug"
}
}
}Find providers by name or slug. Use when the agent does not know the exact slug ('look up that DBaaS… planetscale?'). Uses Meilisearch under the hood so typos and shorthand still match — 'aws', 'gcp', 'githb', 'k8s' all resolve to the right vendor.
| Argument | Type | Description |
|---|---|---|
| limit | integer | |
| query* | string |
{
"type": "object",
"title": "search_providersArguments",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 10
},
"query": {
"type": "string",
"title": "Query"
}
}
}