Skip to main content
Glama
imprvhub

Status Observer MCP

status

Monitor and verify the operational status of digital platforms using specific commands to list, check all, or target individual platforms like GitHub.

Instructions

Check operational status of major digital platforms

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesCommand to execute (list, --all, or platform with -- prefix like --github)

Implementation Reference

  • Main MCP tool handler for 'status': parses command (list, --all, --<platform>) and delegates to StatusObserver methods.
    if (name === "status") {
      const command = (typeof args?.command === 'string' ? args.command : '').toLowerCase() || '';
      
      if (command === 'list') {
        return {
          content: [
            {
              type: "text",
              text: statusObserver.getPlatformsList()
            }
          ]
        };
      } else if (command === '--all') {
        return {
          content: [
            {
              type: "text",
              text: await statusObserver.getAllPlatformsStatus()
            }
          ]
        };
      } else if (command.startsWith('--')) {
        const platformId = command.slice(2);
        return {
          content: [
            {
              type: "text",
              text: await statusObserver.getPlatformStatus(platformId)
            }
          ]
        };
      } else {
        throw new Error(`Unknown command: ${command}. Available commands: list, --all, or platform with -- prefix like --openrouter, --openai, --github`);
      }
    }
  • Input schema definition for the 'status' tool, specifying the 'command' parameter.
    status: {
      description: "Check operational status of major digital platforms including AI providers, cloud services, and developer tools",
      schema: {
        type: "object",
        properties: {
          command: {
            type: "string",
            description: "Command to execute (list, --all, or platform with -- prefix like --openrouter, --openai, --github)"
          }
        },
        required: ["command"]
      }
    }
  • src/index.ts:1084-1108 (registration)
    Server initialization registering the 'status' tool via capabilities.
    const server = new Server(
      {
        name: "mcp-status-observer",
        version: "0.1.0",
      },
      {
        capabilities: {
          tools: {
            status: {
              description: "Check operational status of major digital platforms including AI providers, cloud services, and developer tools",
              schema: {
                type: "object",
                properties: {
                  command: {
                    type: "string",
                    description: "Command to execute (list, --all, or platform with -- prefix like --openrouter, --openai, --github)"
                  }
                },
                required: ["command"]
              }
            }
          },
        },
      }
    );
  • src/index.ts:1110-1129 (registration)
    ListTools handler registering/declaring the 'status' tool schema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: "status",
            description: "Check operational status of major digital platforms including AI providers like OpenRouter, OpenAI, Anthropic; cloud services like GCP, Vercel; and developer tools",
            inputSchema: {
              type: "object",
              properties: {
                command: {
                  type: "string",
                  description: "Command to execute (list, --all, or platform with -- prefix like --openrouter, --openai, --github, --gcp)"
                }
              },
              required: ["command"]
            }
          }
        ]
      };
    });
  • Core helper method in StatusObserver that fetches and formats status for a specific platform, dispatching to platform-specific handlers.
    async getPlatformStatus(platformId: string): Promise<string> {
      const platform = this.platforms.get(platformId);
      if (!platform) {
        return `Platform '${platformId}' not found. Use 'status list' to see available platforms.`;
      }
    
      try {
        if (platformId === 'anthropic') {
          return await this.getAnthropicStatus(platform);
        }
    
        if (platformId === 'atlassian') {
          return await this.getAtlassianStatus(platform);
        }
    
        if (platformId === 'docker') {
          return await this.getDockerStatus(platform);
        }
    
        if (platformId === 'gcp') {
          return await this.getGCPStatus(platform);
        }
    
        if (platformId === 'gemini') {
          return await this.getGeminiStatus(platform);
        }
    
        if (platformId === 'linkedin') {
          return await this.getLinkedInStatus(platform);
        }
    
        if (platformId === 'openai') {
          return await this.getOpenAIStatus(platform);
        }
    
        if (platformId === 'openrouter') {
          return await this.getOpenRouterStatus(platform);
        }
    
        if (platformId === 'supabase') {
          return await this.getSupabaseStatus(platform);
        }
    
        if (platformId === 'x') {
          return await this.getXStatus(platform);
        }
        
        const response = await axios.get(platform.url);
        const data = response.data;
        
        let statusOutput = `${platform.name} Status:\n`;
        statusOutput += `${this.formatOverallStatus(data, platformId)}\n\n`;
        
        if (data.components && Array.isArray(data.components)) {
          statusOutput += `Components:\n`;
          data.components.forEach((component: any) => {
            statusOutput += `- ${component.name}: ${this.normalizeStatus(component.status)}\n`;
            if (component.description) {
              statusOutput += `  Description: ${component.description}\n`;
            }
          });
        } else if (data.components && typeof data.components === 'object') {
          statusOutput += `Components:\n`;
          Object.keys(data.components).forEach(key => {
            const component = data.components[key];
            statusOutput += `- ${component.name}: ${this.normalizeStatus(component.status)}\n`;
            if (component.description) {
              statusOutput += `  Description: ${component.description}\n`;
            }
          });
        } else if (platformId === 'github') {
          this.processGitHubComponents(data, platform);
          statusOutput += this.getGitHubComponentsText(platform);
        }
        
        statusOutput += `\nLast Updated: ${this.formatUpdateTime(data.page?.updated_at || data.updated || new Date().toISOString())}`;
        
        return statusOutput;
      } catch (error) {
        console.error(`Error fetching status for ${platform.name}:`, error);
        
        return `Unable to fetch real-time status for ${platform.name}. The status API might be unavailable or the format has changed.`;
      }
    }
Behavior2/5

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.

Conciseness5/5

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.

Completeness3/5

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.

Parameters3/5

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.

Purpose4/5

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.

Usage Guidelines2/5

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.

Install Server

Other Tools

Related Tools

Latest Blog Posts

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