StackWitness MCP Server

by stackwitness Your server? Claim it

answering

StackWitness is answering right now. Last checked 5 min ago.

Independent monitoring: status, monitors, and incidents from your StackWitness workspace.

Uptime history 91 days of history · worst day 92%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

192 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

StackWitness missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

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

https://mcp.stackwitness.com/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.stackwitness.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.stackwitness.com/mcp	streamable-http	sign-in	161 ms	5 min ago

Alternatives to StackWitness

same job, measured the same way

openstatus

by openstatus

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

answering

StatOSS

by statoss

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

answering

Openuptime

by openuptime

Manage uptime monitors, incidents and status pages from any MCP client.

answering

Statuser

by statuser-cloud

Monitor services, manage incidents and status pages in Statuser.cloud from your AI assistant.

116 installs/wk answering

Uptimepage

by uptimepage

Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.

41 tools answering

losclouds

by losclouds

Cloud and SaaS service status, plus your team's monitors, status pages, incidents, and alerts.

answering

Metricwatch

by cloudcorprecords

Datadog metrics, dashboards, logs, incidents, and monitors from your MCP client.

local only

SutramX

by sutramx

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

77 installs/wk local only

StackWitness — questions

Answers built from our own checks of this server.

Why is there no tool list for StackWitness?

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 StackWitness 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 192 ms. The bar chart above shows every period we have measured.

How do I connect StackWitness?

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 StackWitness?

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

It answers our handshake in 192 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.