Status Observer
STDIOMonitor and query operational status of major digital platforms using MCP.
Monitor and query operational status of major digital platforms using MCP.
[!IMPORTANT] This project is continuously updated with new platform integrations. If you're not seeing a service that should be available, or if Claude doesn't recognize a platform, please update by running
npm run buildfrom a freshly cloned repository.Last updated: 2025-09-12T07:22:15Z (UTC) - Added OpenRouter status integration with RSS incident tracking
status --openrouterClick on any timestamp to jump to that section of the video
00:00 - LinkedIn Platform Status Assessment
Comprehensive analysis of LinkedIn's operational health, including detailed examination of core services such as LinkedIn.com, LinkedIn Learning, Campaign Manager, Sales Navigator, Recruiter, and Talent solutions. All systems confirmed fully operational with zero service disruptions.
00:20 - GitHub Infrastructure Status Overview
Detailed evaluation of GitHub's service availability, covering critical components including Git operations, API requests, Actions, Webhooks, Issues, Pull Requests, Packages, Pages, Codespaces, and Copilot functionality. Complete operational status confirmed across all GitHub services.
00:40 - Vercel Platform Reliability Analysis
In-depth examination of Vercel's global edge network and deployment infrastructure, featuring comprehensive status reporting on core services such as API, Dashboard, Builds, Serverless Functions, Edge Functions, and global CDN locations. All Vercel services verified operational across all regions.
01:08 - Cloudflare Network Status Examination
Extensive analysis of Cloudflare's global infrastructure status, detailing service availability across geographic regions and specific service components. Identified performance degradation in multiple regions (Africa, Asia, Europe, Latin America, Middle East, North America) while core services remain functional. Includes detailed assessment of regional data centers under maintenance and technical impact analysis.
01:46 - Global Operational Status Report
Consolidated overview of operational status across all major technology platforms and service providers, highlighting both fully operational services (GitHub, Vercel, Netlify, Asana, Atlassian, OpenRouter, etc.) and services experiencing degraded performance (Cloudflare, Twilio). Includes strategic recommendations for organizations with dependencies on affected services.
git clone https://github.com/imprvhub/mcp-status-observer cd mcp-status-observer
npm install
npm run build
There are two ways to run the MCP server:
node build/index.js
Keep this terminal window open while using Claude Desktop. The server will run until you close the terminal.
The Claude Desktop can automatically start the MCP server when needed. To set this up:
The Claude Desktop configuration file is located at:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.jsonEdit this file to add the Status Observer MCP configuration. If the file doesn't exist, create it:
{ "mcpServers": { "statusObserver": { "command": "node", "args": ["ABSOLUTE_PATH_TO_DIRECTORY/mcp-status-observer/build/index.js"] } } }
Important: Replace ABSOLUTE_PATH_TO_DIRECTORY with the complete absolute path where you installed the MCP
/Users/username/mcp-status-observerC:\\Users\\username\\mcp-status-observerIf you already have other MCPs configured, simply add the "statusObserver" section inside the "mcpServers" object. Here's an example of a configuration with multiple MCPs:
{ "mcpServers": { "otherMcp1": { "command": "...", "args": ["..."] }, "otherMcp2": { "command": "...", "args": ["..."] }, "statusObserver": { "command": "node", "args": [ "ABSOLUTE_PATH_TO_DIRECTORY/mcp-status-observer/build/index.js" ] } } }
The MCP server will automatically start when Claude Desktop needs it, based on the configuration in your claude_desktop_config.json file.
status command to interact with the Status Observer MCP ServerThe Status Observer MCP provides a single tool named status with several commands:
| Command | Description | Parameters | Example | 
|---|---|---|---|
list | List all available platforms | None | status list | 
--[platform] | Get status for a specific platform | Platform name | status --openrouter | 
--all | Get status for all platforms | None | status --all | 
The Status Observer monitors 22 major digital platforms across various categories:
Here are various examples of how to use the Status Observer with Claude:
# AI Platforms
status --openrouter
status --openai
status --anthropic
status --gemini
# Cloud Infrastructure
status --gcp
status --vercel
status --digitalocean
status --netlify
# Developer Tools
status --docker
status --github
status --atlassian
status --supabase
status --npm
# Productivity & Social
status --linkedin
status --slack
status --x
status --dropbox
# Web Infrastructure
status --cloudflare
status --discord
# All platforms
status --all
status list

You can also interact with the MCP using natural language. Claude will interpret these requests and use the appropriate commands:
If you see the error "MCP Status Observer: Server disconnected" in Claude Desktop:
Verify the server is running:
node build/index.js from the project directoryCheck your configuration:
claude_desktop_config.json is correct for your system\\) for Windows pathsIf the Status Observer tools don't appear in Claude:
To check if the server is running:
ps aux | grep nodeIf you don't see the server running, start it manually or use the auto-start method.
Contributors can easily add support for additional platforms by modifying the initializePlatforms method in src/index.ts. The process is straightforward:
addPlatform method with the following parameters:
id: A unique identifier for the platform (lowercase, no spaces)name: The display name of the platformurl: The status API endpoint URLdescription: A brief description of the platformExample:
this.addPlatform('newservice', 'New Service', 'https://status.newservice.com/api/v2/summary.json', 'Description of the service');
For platforms with non-standard status pages (like OpenRouter, OpenAI, Anthropic), you can create custom handlers:
initializePlatforms()getOpenRouterStatus()getPlatformStatus() method to route to your handlergetQuickPlatformStatus()Example structure for custom handlers:
private async getCustomPlatformStatus(platform: PlatformStatus): Promise<string> { // Custom parsing logic for your platform // Return formatted status text }
When adding new platforms, consider organizing them into logical categories:
This project is licensed under the Mozilla Public License 2.0 - see the LICENSE file for details.
Built for the developer community by imprvhub