statuspage-incidents
Read-only: recent incidents from public Atlassian Statuspage pages. Free, no API key.
Should I use this
Quality & Safety
A
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~164Tokens (tool definitions)
~843 BTypical response size
Minimal attention impact (0.13% of 128k context)
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"statuspage-incidents": {
"url": "https://looper-products.fly.dev/mcp-statuspage/"
}
}
}Remote endpoints
https://looper-products.fly.dev/mcp-statuspage/streamable-httpWhat it can do
Tool inventory
Tools (1)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢get_statuspage_incidents(page_url, limit)
Read-only: fetch recent incidents from a public Atlassian Statuspage-hosted status page (e.g. https://www.githubstatus.com) via its free, unauthenticated JSON API at <base>/api/v2/incidents.json. Returns each incident's name, status, impact, created_at, resolved_at and shortlink. No login or API key.
Input Schema
{
"type": "object",
"properties": {
"page_url": {
"type": "string",
"description": "Base URL of a Statuspage-hosted status page, e.g. https://www.githubstatus.com (must be https)"
},
"limit": {
"type": "integer",
"description": "Max incidents to return, 1-50, default 10"
}
},
"required": [
"page_url"
]
}Community
Evidence
Recent observations
verifiedversion not recorded1 tools