StackWitness MCP Server

by stackwitness Your server? Claim it

answering

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

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

Uptime history 47 days of history

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

191 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check StackWitness 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 11 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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "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

{
  "mcpServers": {
    "mcp": {
      "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	217 ms	11 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

Uptimepage

by uptimepage

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

16 tools answering

Fettle

by fettle

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

32 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

Vivere

by vivere

Know when cron jobs and AI agents stop running: create monitors and check in from your agent.

7 tools answering

DevHelm MCP Server

by devhelmhq

Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm

387 installs/wk local only

Betterstack

by usefulapi

Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

9 tools answering

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 191 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 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 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 191 ms on average, which is faster than 68% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.