statusLABSCO SUMMARY
One tool, three commands, twenty-two platforms — the whole surface fits in a sentence.
The value is the breadth behind a single call: asking one question covers your AI provider, your CDN and your deployment platform at once, which is the actual shape of "is it me or is it them". Platform coverage grows over time, so if a service you expect is missing, rebuild from a fresh clone rather than assuming it is unsupported.
What it is
A Node server that queries the official status pages of 22 major platforms and reports operational state, component-level detail and incident history. One tool with three commands covers all of it.
What you get
- The
statustool, withlistfor available platforms,--allfor everything at once, and--[platform]for one - AI providers: OpenRouter, OpenAI, Anthropic and Gemini
- Cloud: Google Cloud Platform, DigitalOcean, Vercel, Netlify
- Developer tools: Docker, GitHub, npm, Atlassian, Supabase
- Productivity and social: LinkedIn, Slack, Asana, Dropbox, X
- Web infrastructure: Cloudflare, Discord, Reddit; analytics: Amplitude
- Component-level detail within a platform, plus incident history with resolution status and timelines
Requirements
Node.js 16 or higher and an internet connection to reach the status APIs. Clone the repository, npm install, npm run build, then point Claude Desktop at build/index.js with an absolute path — double backslashes on Windows. The npm package name is mcp-status-observer, version 0.7.0. Licensed under the Mozilla Public License 2.0.
Setup effort
Build from source — git clone https://github.com/imprvhub/mcp-status-observer
USE CASES
01
Deciding whether the outage is yours
Check every platform at once before opening the debugger.
02
Checking one provider you depend on
Query that platform directly and read its component-level state.
03
Explaining a degraded deploy
Look at the incident history and timelines rather than guessing at correlation.
04
Seeing what it can even answer
List the supported platforms before asking about one.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- node on PATH
- Node.js 16 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/imprvhub/mcp-status-observer
cd mcp-status-observer
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"statusObserver": {
"command": "node",
"args": [
"<YOUR_PATH_TO_DIRECTORY>/mcp-status-observer/build/index.js"
]
}
}
}
