# StatOSS [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://statoss.com/docs/agents  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/statoss

## Description
Status pages and uptime monitoring: read status, monitors and incidents; open incidents.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What StatOSS does

StatOSS MCP server provides an agent-facing interface for status pages and uptime monitoring. It covers three read-oriented areas: service status, configured monitors, and existing incidents. It also supports opening incidents, allowing an agent to move from observing a problem to recording it in the monitoring system.

The available description does not identify additional systems, data sources, notification channels, or incident fields. Treat the integration as focused on the StatOSS monitoring surface rather than as a general-purpose operations platform.

For a 📊 Monitoring workflow, StatOSS can be considered when an agent needs to answer questions about monitored service health or perform the supported incident-opening action. The supplied material does not describe historical analysis, alert delivery, monitor creation, monitor updates, or incident closure.

## Tools and capabilities

The documented capabilities are:

- Read status information from status pages.
- Read monitor information.
- Read incident information.
- Open incidents.

StatOSS MCP server is therefore suited to workflows that combine monitoring checks with incident intake. An agent could use the read operations to inspect the available monitoring state, then use the incident operation when a new issue needs to be opened. The source material does not provide tool names, argument schemas, return formats, permissions, or examples, so implementations should consult the linked documentation before building tool calls.

## Setup and configuration

The provided material does not include installation commands, transport details, configuration steps, authentication requirements, or environment variables. It also does not identify supported MCP clients. Use the StatOSS agent documentation at https://statoss.com/docs/agents for those operational details rather than assuming a particular launch command or client configuration.

No environment-variable names can be established from the available listing. The same limitation applies to credentials, endpoint settings, workspace selection, and any optional configuration.

## Limitations and notes

The available description confirms status, monitor, and incident reads plus incident creation, but it does not document the scope of each operation. In particular, it does not say whether status data is current or historical, which monitor types are supported, or what information is required to open an incident.

StatOSS MCP server should be evaluated against the agent’s required incident workflow before adoption. Confirm whether the server supports the fields, authentication model, transport, and client integration your environment requires. Because no README is available in the supplied material, compatibility and setup claims cannot be made beyond the listed monitoring operations.

_Full upstream README: https://allmcps.com/mcp/statoss/readme_