Instatus MCP Server

by instatus Your server? Claim it

answering

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

Status pages, incidents, maintenance, components and subscribers on Instatus.

Uptime history 16 hours of history

16 hours agonow

100.0%

Uptime 24h

58 of 58 checks

—

Tools

hidden behind auth

555 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

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

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.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.instatus.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.instatus.com/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.instatus.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.instatus.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.instatus.com/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

URL	Transport	State	Latency	Checked
https://mcp.instatus.com/mcp	streamable-http	sign-in	522 ms	12 min ago

Alternatives to Instatus

same job, measured the same way

Instatus MCP by usefulapi

by usefulapi

Manage status pages: components, incidents and maintenances; set live component status.

14 tools answering

openstatus

by openstatus

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

answering

Uptimely

by getuptimely

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

answering

Pingoru status

by pingoru

Live status, incidents and maintenance windows for 8,000+ cloud and SaaS status pages.

answering

ScaledPapers

by scaledpapers

Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.

34 tools answering

Status.io MCP by usefulapi

by usefulapi

Read Status.io components, incidents, maintenance; post incidents, schedule maintenance, set status.

20 tools answering

OneUptime

by oneuptime

Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime.

223 tools answering

Sorry MCP by usefulapi

by usefulapi

Read status pages and incidents; make confirmed public changes and manage individual subscribers.

21 tools answering

Instatus — questions

Answers built from our own checks of this server.

Why is there no tool list for Instatus?

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 Instatus working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 58 of 58 checks got a reply (100.0%), average response time 555 ms. The bar chart above shows every period we have measured.

How do I connect Instatus?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form 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 Instatus?

No API key is involved. Instatus 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 Instatus?

It answers our handshake in 555 ms on average, which is faster than 20% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.