StatOSS

com.statossv1.0.0Updated Oct 8, 2026

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

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant read StatOSS status pages, monitors and incidents, and open incidents when a write key is used.

What it does
StatOSS is a remote MCP server for status pages and uptime monitoring. It exposes tools to read status, monitors and incidents, and to open incidents. Access level depends on the API key presented: read keys can view status, while write keys can also open incidents.
When to use it
Useful when an assistant needs to check service status or uptime monitors, or to report an incident into StatOSS during an operational workflow. It fits teams already using StatOSS for status pages who want that data reachable from an assistant.
Requirements
A remote streamable HTTP endpoint at statoss.com; no local runtime or package is needed. An Authorization header is required, carrying a Bearer token followed by a StatOSS API key beginning with sk_. Network access to the endpoint is required.
Before you install
The Authorization header carries a StatOSS API key, which is a secret. A write key can open incidents, so it can change data in StatOSS; prefer a read key unless incident creation is intended. Treat the key as sensitive and avoid exposing it in logs or shared configuration.

Installation

In SourceWeft

  1. Open StatOSS in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mcp": {
      "type": "http",
      "url": "https://statoss.com/api/v1/mcp"
    }
  }
}

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 8, 2026