Status Observer MCP
This server allows you to monitor and query the operational status of major digital platforms through a simple interface:
Check specific platform status: Use
status --[platform](e.g.,status --github) to check a specific platformList all available platforms: Use
status listto see all supported platformsCheck all platform statuses: Use
status --allto get the status of all platforms at onceReal-time updates: Receive up-to-date information on operational health of platforms like GitHub, Slack, Discord, Docker, and more
Monitors operational status of Asana platform and provides real-time updates about service availability and component health.
Tracks and reports on the operational status of Atlassian services, allowing queries about current service health and availability.
Provides detailed status information about Cloudflare's global infrastructure and services, including regional performance data and maintenance status.
Monitors the operational status of DigitalOcean's cloud infrastructure and reports on service availability and performance.
Tracks Discord platform status, offering real-time information about service availability and component health.
Monitors Dropbox service status and provides current information about platform availability and performance.
Provides detailed status information for GitHub's infrastructure, including Git operations, API requests, Actions, Webhooks, Issues, Pull Requests, and other components.
Monitors the operational status of Google Cloud Platform services and provides real-time updates about service health and availability.
Tracks Netlify platform status and provides information about service availability and performance.
Monitors the operational status of npm registry and related services, reporting on current availability and performance.
Tracks Reddit platform status and provides information about service health and component availability.
Monitors Slack's operational status and provides real-time information about service availability and component health.
Tracks the operational status of Twilio services and reports on current availability and performance metrics.
Provides detailed status information about Vercel's global edge network and deployment infrastructure, including API, Dashboard, Builds, Serverless Functions, and CDN availability.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Status Observer MCPcheck the status of GitHub and OpenAI"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Status Observer
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 runningnpm run build from a freshly cloned repository.
Last updated: 2025-09-12T07:22:15Z (UTC) - Added OpenRouter status integration with RSS incident tracking
Features
Monitor world's most used digital platforms (GitHub, Slack, Discord, etc.)
Track AI providers including OpenRouter, OpenAI, Anthropic, and Gemini
Get detailed status information for specific services with incident history
Check status of specific components within each platform
Real-time updates of service status with impact analysis
Comprehensive incident tracking with resolution status and timelines
Simple query interface with commands like
status --openrouter
Related MCP server: mcp-rss-aggregator
Demo
Click 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.
Requirements
Node.js 16 or higher
Claude Desktop
Internet connection to access status APIs
Installation
Installing Manually
Clone or download this repository:
git clone https://github.com/imprvhub/mcp-status-observer
cd mcp-status-observerInstall dependencies:
npm installBuild the project:
npm run buildRunning the MCP Server
There are two ways to run the MCP server:
Option 1: Running manually
Open a terminal or command prompt
Navigate to the project directory
Run the server directly:
node build/index.jsKeep this terminal window open while using Claude Desktop. The server will run until you close the terminal.
Option 2: Auto-starting with Claude Desktop (recommended for regular use)
The Claude Desktop can automatically start the MCP server when needed. To set this up:
Configuration
The Claude Desktop configuration file is located at:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
Edit 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
macOS/Linux example:
/Users/username/mcp-status-observerWindows example:
C:\\Users\\username\\mcp-status-observer
If 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.
Usage
Restart Claude Desktop after modifying the configuration
In Claude, use the
statuscommand to interact with the Status Observer MCP ServerThe MCP server runs as a subprocess managed by Claude Desktop
Available Commands
The Status Observer MCP provides a single tool named status with several commands:
Command | Description | Parameters | Example |
| List all available platforms | None |
|
| Get status for a specific platform | Platform name |
|
| Get status for all platforms | None |
|
Supported Platforms
The Status Observer monitors 22 major digital platforms across various categories:
AI & Machine Learning (4)
OpenRouter - AI model routing and access platform
OpenAI - Leading AI services provider (ChatGPT, DALL-E, API)
Anthropic - AI assistant provider (Claude)
Gemini - Google's multimodal AI platform
Cloud Infrastructure (4)
Google Cloud Platform - Comprehensive cloud computing services
DigitalOcean - Developer-focused cloud infrastructure
Vercel - Frontend deployment and edge platform
Netlify - Web development and deployment platform
Developer Tools & Platforms (5)
Docker - Container platform and services
GitHub - Version control and collaboration platform
npm - JavaScript package manager and registry
Atlassian - Developer collaboration tools (Jira, Bitbucket, Confluence)
Supabase - Open source backend platform (PostgreSQL, auth, storage)
Productivity & Collaboration (5)
LinkedIn - Professional networking platform
Slack - Business communication and collaboration
Asana - Team workflow and project management
Dropbox - Cloud file storage and collaboration
X (Twitter) - Social media and real-time communication
Web Infrastructure & Security (3)
Cloudflare - Web infrastructure, CDN, and security
Discord - Developer community and communication platform
Reddit - Social news and developer community platform
Analytics & Business Tools (1)
Amplitude - Product analytics platform
Example Usage
Here are various examples of how to use the Status Observer with Claude:
Direct Commands:
# 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 listPreview

Natural Language Prompts:
You can also interact with the MCP using natural language. Claude will interpret these requests and use the appropriate commands:
"Could you check if OpenRouter is having any API issues right now?"
"What's the status of OpenAI's ChatGPT service?"
"Has there been any recent incidents with Claude or the Anthropic API?"
"Is Google Cloud Platform experiencing any outages in my region?"
"Check if Docker Hub is operational for automated builds"
"What's the current status of LinkedIn's Sales Navigator?"
"Can you tell me if Google's Gemini AI is experiencing any service disruptions?"
"Show me the status of all AI platforms including OpenRouter and OpenAI"
"Are there any active incidents affecting GitHub Actions or Git operations?"
"Check the overall health of Vercel and Netlify for my deployment pipeline"
"Has Supabase had any recent database or authentication issues?"
"What's the status of all major platforms right now?"
Troubleshooting
"Server disconnected" error
If you see the error "MCP Status Observer: Server disconnected" in Claude Desktop:
Verify the server is running:
Open a terminal and manually run
node build/index.jsfrom the project directoryIf the server starts successfully, use Claude while keeping this terminal open
Check your configuration:
Ensure the absolute path in
claude_desktop_config.jsonis correct for your systemDouble-check that you've used double backslashes (
\\) for Windows pathsVerify you're using the complete path from the root of your filesystem
Tools not appearing in Claude
If the Status Observer tools don't appear in Claude:
Make sure you've restarted Claude Desktop after configuration
Check the Claude Desktop logs for any MCP communication errors
Ensure the MCP server process is running (run it manually to confirm)
Verify that the MCP server is correctly registered in the Claude Desktop MCP registry
Checking if the server is running
To check if the server is running:
Windows: Open Task Manager, go to the "Details" tab, and look for "node.exe"
macOS/Linux: Open Terminal and run
ps aux | grep node
If you don't see the server running, start it manually or use the auto-start method.
Contributing
Adding New Status APIs
Contributors can easily add support for additional platforms by modifying the initializePlatforms method in src/index.ts. The process is straightforward:
Identify a platform's status API endpoint
Add a new entry using the
addPlatformmethod 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 platform
Example:
this.addPlatform('newservice', 'New Service', 'https://status.newservice.com/api/v2/summary.json', 'Description of the service');Custom API Integration
For platforms with non-standard status pages (like OpenRouter, OpenAI, Anthropic), you can create custom handlers:
Add the platform to
initializePlatforms()Create a TypeScript interface for the response format
Add a specific handler method like
getOpenRouterStatus()Update the main
getPlatformStatus()method to route to your handlerAdd quick status support in
getQuickPlatformStatus()
Example structure for custom handlers:
private async getCustomPlatformStatus(platform: PlatformStatus): Promise<string> {
// Custom parsing logic for your platform
// Return formatted status text
}Platform Categories
When adding new platforms, consider organizing them into logical categories:
AI/ML: OpenRouter, OpenAI, Anthropic, Gemini
Cloud Infrastructure: GCP, AWS, Azure, DigitalOcean
Developer Tools: GitHub, GitLab, Docker, npm
Productivity: Slack, Microsoft 365, Google Workspace
Web Infrastructure: Cloudflare, Fastly, Akamai
License
This project is licensed under the Mozilla Public License 2.0 - see the LICENSE file for details.
Related Links
Changelog
2025-09-12: Added OpenRouter integration with RSS incident tracking and detailed impact analysis
2025-04-26: Added Docker status integration with comprehensive component monitoring
2025-03-15: Enhanced GCP regional status reporting with incident correlation
2025-02-28: Added Anthropic and Gemini AI platform monitoring
2025-01-20: Initial release with core platform support (GitHub, Vercel, Cloudflare, etc.)
Built for the developer community by imprvhub
Available Tools
1 toolstatusB
Check operational status of major digital platforms
| Name | Required | Description | Default |
|---|---|---|---|
| command | Yes | Command to execute (list, --all, or platform with -- prefix like --github) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Check operational status' which implies a read-only operation, but doesn't specify whether this requires authentication, rate limits, what the output format looks like, or any side effects. For a tool with no annotation coverage, this is insufficient behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose with zero waste. It's appropriately sized and front-loaded, making it easy to understand at a glance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no annotations, no output schema, and a single parameter with full schema coverage, the description is minimally adequate. It states what the tool does but lacks details on behavior, output, or usage context. For a status-checking tool, this leaves gaps in understanding how to interpret results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already fully documents the single 'command' parameter. The description doesn't add any meaning beyond what the schema provides (e.g., it doesn't explain what 'list', '--all', or platform checks like '--github' actually do or return). Baseline 3 is appropriate when the schema does all the work.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose as 'Check operational status of major digital platforms', which is a specific verb ('Check') + resource ('operational status of major digital platforms'). It's not tautological with the name 'status', and there are no sibling tools to differentiate from, so it earns a 4 rather than a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It simply states what the tool does without any usage instructions. With no sibling tools, this is less critical but still a gap in guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.0- First observed
status
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'status' has a clear, distinct purpose that cannot be confused with any other tool in this set.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or conventions. The name 'status' is straightforward and follows a simple noun-based pattern.
A single tool is too few for a server named 'Status Observer MCP', which implies monitoring multiple platforms or aspects. This minimal set feels thin and underdeveloped for the apparent scope of observing status across major digital platforms.
The tool surface is severely incomplete for a status observer domain. It only provides a generic status check without tools for listing platforms, setting alerts, retrieving historical data, or handling specific platform types, leading to significant gaps in functionality.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
- sentinelOAuthio.rootstuff
Uptime, SSL, DNS and domain monitoring you can talk to from Claude or any MCP client.
Model Context Protocol server for Studex tools, notifications, and profile integrations
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Related MCP Servers
- FlicenseBqualityDmaintenanceA Model Context Protocol server that enables users to kickoff and monitor deployed CrewAI workflows through Claude Desktop.259-
- AlicenseCqualityCmaintenanceModel Context Protocol Server for aggregating RSS feeds in Claude Desktop127Mozilla Public 2.0
- FlicenseNot gradedqualityDmaintenanceA Python server implementing the Model Context Protocol that exposes tools for querying external APIs, compatible with Claude Desktop and ChatGPT Desktop.-
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables interaction with Polymarket prediction markets through Claude Desktop.31MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/imprvhub/mcp-status-observer'
If you have feedback or need assistance with the MCP directory API, please join our Discord server