IncidentVault MCP Server

by incidentvault-app Your server? Claim it

answering

IncidentVault is answering right now. Last checked 2 min ago.

Incident, task and follow-up records with role and location limits on every call.

Uptime history 5 days of history

5 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

524 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check IncidentVault 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 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add incidentvault --transport http https://app.incidentvault.com/api/mcp/apps/server

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

https://app.incidentvault.com/api/mcp/apps/server

~/.codex/config.toml

[mcp_servers.incidentvault]
url = "https://app.incidentvault.com/api/mcp/apps/server"

.cursor/mcp.json

{
  "mcpServers": {
    "incidentvault": {
      "url": "https://app.incidentvault.com/api/mcp/apps/server"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "incidentvault": {
      "type": "http",
      "url": "https://app.incidentvault.com/api/mcp/apps/server"
    }
  }
}

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://app.incidentvault.com/api/mcp/apps/server	streamable-http	sign-in	495 ms	2 min ago

Alternatives to IncidentVault

same job, measured the same way

Rootly MCP

by servosity

Every Rootly incident, alert, and on-call object as a typed command - plus a local SQLite mirror

local only

AI Incident Law

by snapsynapse

Public-record corpus of AI litigation, regulation, and enforcement, anchored to EveryAILaw.

120 installs/wk local only

Incident Response MCP for Apache Airflow

by madamak

Diagnose Airflow failures from UI links with bounded logs and optional recovery actions.

134 installs/wk local only

Rootly

by mcparmory

Manage incident alerts, events, and workflows with custom automations

213 installs/wk local only

RadioChron

by sergii-ziborov

Local-first Wi-Fi incident diagnostics with native BLE scan, history, and risk evidence.

63 installs/wk local only

Context

by everydaysecurity

OSINT investigations with traceable evidence: domains, URLs, IPs, scams and business records.

answering

Cronjob.de

by cronjob

Web cron for sites without their own scheduler: calls your URLs on schedule and logs every call.

answering

Agent Billboard

by yourmatematt

Read and post to The Agent Billboard on Solana, with spend limits in code and a reasoning log.

123 installs/wk local only

IncidentVault — questions

Answers built from our own checks of this server.

Why is there no tool list for IncidentVault?

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

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

How do I connect IncidentVault?

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

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

It answers our handshake in 524 ms on average, which is faster than 22% 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.