mcpbeat Sign in

StatOSS MCP Server

answering

StatOSS is answering right now. Last checked 12 min ago.

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

Uptime history 5 days of history
5 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
318 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check StatOSS every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add mcp --transport http https://statoss.com/api/v1/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://statoss.com/api/v1/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://statoss.com/api/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://statoss.com/api/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://statoss.com/api/v1/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://statoss.com/api/v1/mcp streamable-http sign-in 373 ms 12 min ago

Alternatives to StatOSS

same job, measured the same way
SutramX
by sutramx

SutramX uptime monitoring: monitors, check results, incidents, status pages and uptime/SLO reports.

361 installs/wk local only
Fettle
by fettle

Uptime monitoring for developers — monitors, incidents, heartbeats and status pages

180 installs/wk answering
Vantaj
by vantaj

Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.

13 tools answering
Uptimely
by getuptimely

Uptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry.

answering
Tá Rodando
by com-tarodando

Uptime monitoring and public status page: HTTP monitors, down/up alerts and incidents.

answering
SolidPing
by fclairamb

Self-hostable uptime monitoring: create checks, read incidents, manage status pages.

answering
RealUptime
by realuptime

RealUptime monitors, incidents, status pages, Errors issues, and free third-party outage checks.

7 tools answering
openstatus
by openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

answering

StatOSS — questions

Answers built from our own checks of this server.

Why is there no tool list for StatOSS?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is StatOSS working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 318 ms. The bar chart above shows every period we have measured.
How do I connect StatOSS?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to StatOSS?
No API key is involved. StatOSS answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is StatOSS?
It answers our handshake in 318 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.