get_statuspage_incidents — statuspage incidents MCP Tool Read-only
get_statuspage_incidents
(get statuspage incidents) is one of 1 tool on the
statuspage incidents
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_statuspage_incidents from your client
- Claude Code statuspage incidents get_statuspage_incidents run in your project directory
- Claude Desktop statuspage incidents get_statuspage_incidents ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor statuspage incidents get_statuspage_incidents ~/.cursor/mcp.json
- VS Code statuspage incidents get_statuspage_incidents .vscode/mcp.json
- Zed statuspage incidents get_statuspage_incidents ~/.config/zed/settings.json
- Windsurf statuspage incidents get_statuspage_incidents ~/.codeium/windsurf/mcp_config.json
- Cline statuspage incidents get_statuspage_incidents ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI statuspage incidents get_statuspage_incidents ~/.gemini/settings.json
- Grok statuspage incidents get_statuspage_incidents .mcp.json (in your project root)
- ChatGPT statuspage incidents get_statuspage_incidents Settings → Connectors → Advanced → Developer mode
- Claude.ai statuspage incidents get_statuspage_incidents Settings → Connectors → Add custom connector
- LangChain statuspage incidents get_statuspage_incidents pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http statuspage-incidents https://looper-products.fly.dev/mcp-statuspage/
This list was read from the server itself, by connecting to it and calling tools/list on 28 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.