Exit1 Uptime Monitoring MCP MCP server

The official MCP server for exit1.dev allows AI agents to interact directly with the Exit1 uptime monitoring platform. It enables users to create monitoring checks, configure alerts, and query real-time uptime history and logs without leaving their development environment. This integration supports various protocols including HTTP/S, TCP, UDP, WebSocket, and ICMP, providing detailed metrics like DNS, TLS, and TTFB timings.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by Pradsgaard Labs

MCP endpoint (Streamable HTTP)

https://app.exit1.dev/mcp/v1

Vendor documentation

What you can do with it

Create new uptime monitoring checks for websites or APIs
Query real-time status and latency data for active monitors
Configure alerting rules and notification channels
Retrieve historical uptime logs and incident details

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http exit1-uptime-monitoring-mcp https://app.exit1.dev/mcp/v1

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add exit1-uptime-monitoring-mcp --url https://app.exit1.dev/mcp/v1

Cursor

Merge this server into .cursor/mcp.json in your project, then enable exit1-uptime-monitoring-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "exit1-uptime-monitoring-mcp": {
      "url": "https://app.exit1.dev/mcp/v1"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "exit1-uptime-monitoring-mcp": {
      "type": "streamableHttp",
      "url": "https://app.exit1.dev/mcp/v1",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start exit1-uptime-monitoring-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "exit1-uptime-monitoring-mcp": {
      "type": "http",
      "url": "https://app.exit1.dev/mcp/v1"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http exit1-uptime-monitoring-mcp https://app.exit1.dev/mcp/v1

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "exit1-uptime-monitoring-mcp": {
      "url": "https://app.exit1.dev/mcp/v1"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "exit1-uptime-monitoring-mcp": {
      "serverUrl": "https://app.exit1.dev/mcp/v1"
    }
  }
}

See all 148

Do you run Exit1 Uptime Monitoring MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing