v0.7.0

0eef26d: OpenRouter Status Monitoring Integration

Overview

This release introduces a significant expansion of the platform's monitoring capabilities by integrating comprehensive status tracking for OpenRouter, a prominent AI/ML platform. The primary purpose of this new feature is to provide users with a unified and detailed view of OpenRouter's operational status, including real-time incident detection, impact analysis, and historical incident data.

The integration addresses the growing need for robust monitoring across various AI service providers, ensuring that users relying on OpenRouter for their applications can quickly ascertain the health of its core components (API, Dashboard). This enhancement is crucial for developers and operations teams to proactively manage dependencies and respond to service disruptions. Users can expect improved visibility into OpenRouter's status, consistent incident reporting aligned with other monitored AI platforms, and a more complete picture of their AI infrastructure's reliability.

Release Details

• Release Date: 2025-09-12 07:39:50 UTC
• Commit: 0eef26d
• Author: imprvhub
• Branch(es): tag: 0.7.0

Changes

This release primarily focuses on the integration of OpenRouter status monitoring, enhancing the platform's ability to track and report on AI/ML service health.

Added Projects

• OpenRouter Integration: This new feature provides comprehensive status monitoring for the OpenRouter AI platform. It includes:
  • Type-Safe API Responses: Introduction of the OpenRouterStatusResponse interface to ensure type safety and consistency when handling OpenRouter's API responses.
  • Custom RSS Feed Incident Parsing: Implementation of a dedicated parser for OpenRouter's custom RSS feed to accurately extract incident information.
  • getOpenRouterStatus() Handler: A new handler function responsible for fetching, parsing, and processing OpenRouter status data, including detailed incident tracking.
  • Comprehensive Incident Filtering: Enhanced incident management to categorize and display active, recently resolved, and historical incidents within a 7-day window, providing a clear overview of service stability.
  • Standardized Impact Formatting: Improved formatting for incident impact and date handling, ensuring consistency with other monitored AI providers like OpenAI, Anthropic, and Gemini.
  • getQuickPlatformStatus() Update: The getQuickPlatformStatus() function has been updated to include OpenRouter in the --all summary, offering a consolidated view of all monitored platforms.
  • Platform Initialization: OpenRouter has been added to the platform initialization process, categorized under AI/ML, and its monitoring capabilities are highlighted in updated tool descriptions and command documentation.

Modified Files

• README.md (modified)

  • Changes: 155 total
  • Added: 122 lines
  • Removed: 33 lines

• src/index.ts (modified)

  • Changes: 176 total
  • Added: 168 lines
  • Removed: 8 lines

Testing

Extensive testing was performed to ensure the accuracy and reliability of the OpenRouter integration. This included:

• Unit Tests: Automated unit tests were conducted on the OpenRouterStatusResponse interface and the RSS feed parsing logic to validate data structure and extraction accuracy.
• Integration Tests: End-to-end integration tests were performed to verify the getOpenRouterStatus() handler's ability to fetch, process, and correctly report OpenRouter's status and incidents. This involved simulating various incident scenarios.
• Manual Verification: Manual checks were performed to confirm that the output of OpenRouter status matched the official OpenRouter status page, particularly for active and resolved incidents, and that the formatting was consistent with other AI platforms.

Instructions for Update

To update to this new version and access the OpenRouter status monitoring functionality, users can typically update their package dependencies. If you are using this as a Node.js package, run:

npm install
npm run build

If you are running from source, pull the latest changes from the repository:

git pull origin main # or your configured branch
npm install # to ensure all new dependencies are installed

Additional Notes

This integration ensures that OpenRouter's status reporting is consistent in format and detail with other major AI providers already monitored by the system. Users will benefit from a unified interface for monitoring the health of their critical AI infrastructure components. No breaking changes are anticipated with this release; it is purely additive functionality.

What's Changed

• Add MseeP.ai badge by @lwsinclair in #3
• MCP Trust Score by @Matvey-Kuk in #6
• chore(deps): bump form-data from 4.0.2 to 4.0.4 in the npm_and_yarn group across 1 directory by @dependabot[bot] in #5
• Add OpenRouter Status Monitoring via MCP by @imprvhub in #8

New Contributors

• @lwsinclair made their first contribution in #3
• @Matvey-Kuk made their first contribution in #6
• @dependabot[bot] made their first contribution in #5
• @imprvhub made contribution in #8

Full Changelog: 0.6.0...0.7.0

v0.6.0

c149ad0: Add Docker status monitoring integration

Overview

This release introduces the capability to monitor the status of Docker services within the platform. The primary purpose is to enhance the system's real-time status observation features. This new functionality allows the platform to query on the operational status of Docker Hub Services. The expected impact on users is the ability to gain visibility into the health and status of their components directly through the platform, improving overall system observability and troubleshooting capabilities.

Release Details

• Release Date: 2025-04-26 21:09:37 UTC
• Commit: c149ad0
• Author: Iván Luna
• Branch(es): main

Changes

New Features

• Docker Status Monitoring: Integrated functionality to monitor the status of Docker services. This involves introducing a dedicated Docker interface and handler within the MCP server architecture. This enhancement enables the platform to perform real-time checks on the state of Docker, providing up-to-date status information.

Modified Files

• README.md (modified)

  • Changes: 6 total
  • Added: 4 lines
  • Removed: 2 lines

• src/index.ts (modified)

  • Changes: 55 total
  • Added: 55 lines
  • Removed: 0 lines

Testing

Automated tests were executed to verify the correct implementation of the Dpcler status handler and ensure it can successfully retrieve and process status information from the specified Docker Hub endpoints. Manual checks were also performed to confirm the new natural language queries function as expected and return the correct status data.

Instructions for Update

To update to this version, pull the latest changes from the main branch of the repository:

git pull origin main

Depending on your deployment method, you may need to rebuild or restart the application to apply the changes.

Full Changelog: 0.5.0...0.6.0

v0.5.0

385b4e9: Add Gemini status monitoring integration

Overview

This release introduces the capability to monitor the status of Gemini services within the platform. This new feature was developed to enhance the platform's overall status observation capabilities by including real-time monitoring of external services like Gemini. The integration provides a dedicated interface and handler to interact with Gemini's status endpoints. Users can expect improved visibility into the health and availability of services dependent on or related to Gemini, contributing to more robust system monitoring and quicker identification of potential issues.

Release Details

• Release Date: 2025-04-26 20:14:19 UTC
• Commit: 385b4e9
• Author: Iván Luna
• Branch(es): main

Changes

This release primarily focuses on integrating Gemini service status monitoring.

New Features

• Gemini Status Monitoring: Added a new interface and handler specifically designed to query and report the status of Gemini services. This integration allows the platform to fetch real-time status information, enhancing the overall monitoring scope.
• README Update: The README.md file has been updated to include natural language examples demonstrating how to query the newly added Gemini status information.

Modified Files

• README.md (modified)

  • Changes: 2 total
  • Added: 2 lines
  • Removed: 0 lines

• src/index.ts (modified)

  • Changes: 114 total
  • Added: 91 lines
  • Removed: 23 lines

v0.4.0

e67da0c: Add Anthropic status monitoring integration

Overview

This release introduces a significant new feature: real-time monitoring of Anthropic services within the MCP status observer. The purpose of this integration is to provide users with immediate visibility into the operational status of key Anthropic platforms, including claude.ai, console.anthropic.com, and the Anthropic API. By adding this capability, users can quickly ascertain the health of these critical services, which is essential for applications and workflows that depend on them. The expected impact is improved awareness and troubleshooting capabilities for users relying on Anthropic services, allowing them to react promptly to any reported outages or performance issues.

Release Details

• Release Date: 2025-04-26 19:53:43 UTC
• Commit: e67da0c
• Author: Iván Luna
• Branch(es): main

Changes

This release primarily focuses on adding new monitoring capabilities.

New Features

• Anthropic Status Monitoring: Integrated monitoring for Anthropic services. This includes adding a dedicated interface and handler within the MCP server architecture to query and report the status of:
  • claude.ai
  • console.anthropic.com
  • Anthropic API
• Natural Language Query Examples: Added examples demonstrating how to query the status of the newly integrated Anthropic services using natural language commands.

Modified Files

• README.md (modified)

  • Changes: 3 total
  • Added: 2 lines
  • Removed: 1 lines

• src/index.ts (modified)

  • Changes: 82 total
  • Added: 80 lines
  • Removed: 2 lines

Testing

Automated tests were executed to verify the correct implementation of the Anthropic status handler and ensure it can successfully retrieve and process status information from the specified Anthropic endpoints. Manual checks were also performed to confirm the new natural language queries function as expected and return the correct status data.

Instructions for Update

To update to this version, pull the latest changes from the main branch of the repository:

git pull origin main

Depending on your deployment method, you may need to rebuild or restart the application to apply the changes.

v0.3.0

199ada8: Add OpenAI Status Monitoring Integration

Overview

This release introduces a significant new feature: the integration of real-time status monitoring for OpenAI services. The purpose of this addition is to provide users with immediate visibility into the operational status of key OpenAI components, including ChatGPT, various APIs, Sora, and other related services. This feature was created to address the need for reliable information regarding the availability and performance of these critical external dependencies. By integrating this monitoring capability directly into the MCP server, users can quickly ascertain if any issues they are experiencing might be related to the status of OpenAI's infrastructure. The expected impact on users is improved diagnostic capability and reduced time spent troubleshooting issues potentially caused by external service outages.

Release Details

• Release Date: 2025-04-26 19:34:36 UTC
• Commit: 199ada8
• Author: Iván Luna
• Branch(es): tag: 0.3.0

Changes

This release primarily focuses on adding a new integration for monitoring external service status.

New Features

• OpenAI Status Monitoring: Added a new integration to monitor the real-time status of OpenAI services. This includes checks for components such as ChatGPT, various OpenAI APIs, Sora, and other related infrastructure. An interface and handler for interacting with the OpenAI status endpoint have been implemented within the MCP server architecture.
• Natural Language Examples: Included natural language examples demonstrating how to query the status of OpenAI services using the system.

Documentation Updates

• The README.md file has been updated to include information about the new OpenAI status monitoring integration, providing guidance on its usage and relevance.

Modified Files

• README.md (modified)

  • Changes: 10 total
  • Added: 9 lines
  • Removed: 1 lines

• src/index.ts (modified)

  • Changes: 89 total
  • Added: 89 lines
  • Removed: 0 lines

Testing

Manual testing was performed to verify the functionality of the new OpenAI status monitoring integration. This included:

• Confirming that the system can successfully retrieve status information from the OpenAI status endpoint.
• Validating that the retrieved status is correctly processed and displayed.
• Testing the provided natural language examples to ensure they correctly trigger the OpenAI status query.

Instructions for Update

To update to this version, pull the latest changes from the repository or update your dependency if using a package manager.

# Example using git
git pull origin tag: 0.3.0

# Example using npm (if published)
npm update mcp-status-observer@0.3.0

Refer to the updated README.md for specific instructions on configuring and utilizing the new OpenAI status monitoring feature.

Additional Notes

This release does not introduce any known breaking changes. Users wishing to utilize the new OpenAI status monitoring feature may need to ensure appropriate network access to the OpenAI status endpoint and potentially configure relevant settings as outlined in the updated documentation.

v0.2.1

c1a625a: MCP Tools visibility in Smithery.ai

Overview

This release addresses a critical configuration issue preventing the MCP (Model Context Protocoll) server tools from being correctly recognized and executed within the Smithery.ai platform. The primary goal was to ensure the compiled tools are properly packaged and the runtime environment is configured to expose them via the expected path, thereby enabling users to leverage these tools effectively within their Smithery workflows. This fix is essential for the functionality of the MCP tools integration and is expected to have a positive impact by making the tools usable as intended.

Release Details

• Release Date: 2025-04-25 17:51:56 UTC
• Commit: c1a625a
• Author: Iván Luna
• Branch(es): main

Changes

Bug Fixes

• Corrected Tool Visibility in Smithery: Fixed an issue where the compiled MCP tools were not correctly exposed or found by the Smithery.ai platform due to incorrect packaging and runtime path configuration. This involved adjusting the Dockerfile and application entry point to ensure the executable is placed in an accessible location and the startCommand aligns with the container's execution environment.

Improvements

• Multi-Stage Docker Build: Updated the Dockerfile to utilize a multi-stage build process. This improves the build efficiency by separating the build environment from the final runtime environment, resulting in a smaller and more secure final Docker image.
• Improved TypeScript Packaging: Ensured that the compiled JavaScript output from the TypeScript source (src/index.ts) is correctly included in the final Docker image, resolving issues where the application code was missing or incorrectly located at runtime.
• Aligned Start Command: Modified the smithery.yaml configuration to align the startCommand with the actual CMD defined in the Dockerfile, ensuring the application starts correctly when deployed on the Smithery platform.

Modified Files

• Dockerfile (modified)

  • Changes: 14 total
  • Added: 7 lines
  • Removed: 7 lines

• smithery.yaml (modified)

  • Changes: 20 total
  • Added: 14 lines
  • Removed: 6 lines

• src/index.ts (modified)

  • Changes: 16 total
  • Added: 15 lines
  • Removed: 1 lines

Testing

Manual testing was performed by building the Docker image, deploying it to a Smithery environment, and verifying that the MCP tools were correctly listed and executable via the Smithery interface. The application's startup and basic functionality were also confirmed.

Instructions for Update

To apply these changes, users should pull the latest version of the repository and rebuild the Docker image. The updated image should then be deployed to replace the existing instance running on the Smithery platform. Ensure your Smithery configuration (smithery.yaml) is updated to match the version in this release if you maintain a separate copy.

Additional Notes

This release primarily focuses on fixing the deployment and configuration for the Smithery platform integration. Users who were unable to use the MCP tools within Smithery due to visibility issues should now find them fully functional after updating to this version.

v0.2.0

Google Cloud Platform Monitoring Integration d589646: Introduce GCP support in Model Context Protocol server

Overview

This release introduces the capability to monitor the status of Google Cloud Platform (GCP) services. This new feature was created to provide users with comprehensive visibility into the health of critical cloud infrastructure alongside other monitored services within the mcp-status-observer. By integrating GCP status monitoring, users can quickly identify potential issues affecting their GCP resources, such as active incidents or regional service disruptions, enhancing overall system observability and proactive issue detection. The expected impact on users is improved awareness of GCP service health directly within the observer's output.

Release Details

• Release Date: 2025-04-25 07:54:29 UTC
• Commit: d589646
• Author: Iván Luna
• Branch(es): tag: 0.2.0

GCP Status Monitoring Preview

Changes

New Features

• GCP Service Status Monitoring: Added support for fetching and displaying the current status of Google Cloud Platform services. This includes:
  • Retrieving the overall status of GCP.
  • Identifying and listing active incidents affecting GCP services.
  • Providing detailed status information for individual GCP services, broken down by region.
• Data Structure: Introduced the GCPStatusResponse interface to accurately model the structure of status data received from the GCP status API.
• Region Name Formatting: Implemented logic to format region names for improved readability in the status output.
• Integration: Integrated the GCP status retrieval and processing logic into the main StatusObserver class, allowing it to fetch and report on GCP status alongside other monitored platforms.

Modified Files

• src/index.ts (modified)
  • Changes: 100 total
  • Added: 100 lines
  • Removed: 0 lines

Testing

Manual testing was performed to verify the correct fetching, parsing, and display of GCP service status data. This included checking that the overall status, active incidents, and regional service statuses were accurately retrieved and presented in the observer's output under various simulated conditions (e.g., healthy status, active incidents).

Full Changelog: 0.1.0...0.2.0

v0.1.0

Initial Release 419821a: Project Initialization and Status Observer Tool

Overview

This release marks the initial commit and foundational setup for the mcp-status-observer project. The primary purpose of this project is to provide a Model Context Protocol (MCP) tool that allows users to quickly and easily check the operational status of various major digital platforms directly from within an MCP-compatible environment, such as Claude Desktop.

The tool was created to address the need for readily accessible service health information for developers, users, and administrators who rely on these platforms. By integrating this functionality as an MCP tool, users can query platform status without leaving their current workflow or needing to navigate to external status pages.

The expected impact on users is enhanced productivity and reduced friction when troubleshooting or monitoring dependencies on external services. Users can get real-time status updates for critical platforms like GitHub, Slack, Vercel, and others with simple commands.

Release Details

• Release Date: 2025-04-25 03:15:40 UTC
• Commit: 419821a
• Author: Iván Luna
• Branch(es): main

Changes

This initial release establishes the core project structure and introduces the fundamental functionality of the MCP Status Observer tool.

New Features

• MCP Status Observer Tool: Introduces a new MCP tool named status. This tool allows users to query the operational status of a predefined list of digital platforms.
  • Functionality: Fetches status information by making HTTP requests to the official status APIs or designated helper endpoints for each supported platform. It normalizes the status responses (e.g., "operational", "degraded performance", "major outage") for consistent reporting.
  • Commands: The status tool supports the following commands via its command input parameter:
    • list: Lists all available platforms that can be checked, along with a brief description.
    • --all: Fetches and displays a quick overall status for all supported platforms.
    • --<platformId>: Fetches and displays detailed status information for a specific platform (e.g., --github, --slack).
  • Supported Platforms: The initial implementation includes support for checking the status of: Amplitude, Asana, Atlassian, Cloudflare, DigitalOcean, Discord, Dropbox, GitHub, LinkedIn, Netlify, npm, Reddit, Slack, Supabase, Twilio, Vercel, and X.

Project Setup

• Initial Repository Structure: Sets up the basic directory structure for a Node.js/TypeScript project.
• Dependency Management: Includes package.json and package-lock.json for managing project dependencies, including the Model Context Protocol SDK and axios for making HTTP requests.
• TypeScript Configuration: Provides tsconfig.json for TypeScript compilation settings.
• Dockerization: Includes a Dockerfile for building a containerized version of the application, facilitating deployment and execution in various environments.
• Documentation: Adds a basic README.md file outlining the project's purpose and initial usage.
• Licensing: Includes the project's LICENSE file.
• Git Configuration: Adds .gitattributes and .gitignore for standard Git repository management.
• Smithery Configuration: Includes smithery.yaml, likely for build or deployment automation purposes.

Added Projects

• MCP Status Observer Tool: This release adds the core mcp-status-observer project itself. It functions as an MCP tool designed to provide real-time status updates for various digital services. Its importance lies in enabling users within an MCP environment to quickly ascertain the health of external dependencies.

Modified Files

• .gitattributes (added)

  • Changes: 1 total
  • Added: 1 lines
  • Removed: 0 lines

• .gitignore (added)

  • Changes: 205 total
  • Added: 205 lines
  • Removed: 0 lines

• Dockerfile (added)

  • Changes: 13 total
  • Added: 13 lines
  • Removed: 0 lines

• LICENSE (added)

  • Changes: 373 total
  • Added: 373 lines
  • Removed: 0 lines

• README.md (added)

  • Changes: 245 total
  • Added: 245 lines
  • Removed: 0 lines

• package-lock.json (added)

  • Changes: 1419 total
  • Added: 1419 lines
  • Removed: 0 lines

• package.json (added)

  • Changes: 21 total
  • Added: 21 lines
  • Removed: 0 lines

• public/assets/preview.png (added)

  • Changes: 0 total
  • Added: 0 lines
  • Removed: 0 lines

• smithery.yaml (added)

  • Changes: 24 total
  • Added: 24 lines
  • Removed: 0 lines

• src/index.ts (added)

  • Changes: 629 total
  • Added: 629 lines
  • Removed: 0 lines

• tsconfig.json (added)

  • Changes: 17 total
  • Added: 17 lines
  • Removed: 0 lines

Testing

Initial testing for this release involved manual verification of the core functionality. This included:

• Running the application locally to ensure it starts correctly and connects via StdioServerTransport.
• Using an MCP client (like Claude Desktop) to interact with the status tool.
• Executing the list command to verify the list of platforms is displayed correctly.
• Executing the --all command to check that overall statuses for all platforms are fetched and displayed.
• Executing specific platform commands (e.g., --github, --slack) to ensure detailed status information is retrieved and formatted correctly, including handling of different API response structures (e.g., Atlassian, LinkedIn, Supabase, X).
• Testing error handling for unknown commands or platforms.

Additional Notes

This is the initial release of the mcp-status-observer project, establishing the fundamental structure and core status checking functionality. It serves as the foundation for future enhancements and potential expansion of supported platforms or features. There are no migration steps or breaking changes associated with this release as it is the first version.