MCPNav

Exit1 Uptime Monitoring

MCP server · by exit1

Monitoring & Observability
npmStreamable HTTP
v0.2.0

Set up uptime monitoring from your editor: create checks, configure alerts, query uptime history.

Install

Run one of the commands below, then add the client config underneath.

npm
npx -y exit1-mcp
Streamable HTTP
https://app.exit1.dev/mcp/v1

Client configuration

Paste into Claude Desktop, Cursor (mcp.json), VS Code or any MCP client, then restart the client.

mcpServers
{
  "mcpServers": {
    "exit1-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "exit1-mcp"
      ]
    }
  }
}

About this server

Exit1 Uptime Monitoring is listed in the Monitoring & Observability category of the MCPNav directory. It is distributed as npm, Streamable HTTP and can be loaded by any client that speaks the Model Context Protocol.

Typical uses include giving your assistant scoped access to the corresponding service so it can answer questions and take actions with real data instead of guessing. Always review what a server can access before you enable it — see our MCP security guide.

Frequently asked questions

What is the Exit1 Uptime Monitoring MCP server?

Exit1 Uptime Monitoring is an MCP server by exit1. Set up uptime monitoring from your editor: create checks, configure alerts, query uptime history.

How do I install Exit1 Uptime Monitoring?

Install it with: npx -y exit1-mcp. Then add the JSON config to your client's MCP settings and restart the client.

Is Exit1 Uptime Monitoring free to use?

The MCP server itself is free to install. The source is public on https://github.com/Mopra/exit1.dev.mcp. Any third-party API it calls (such as a search or maps API) may require its own key and billing.

Which clients support Exit1 Uptime Monitoring?

Any MCP-compatible client can use it, including Claude Desktop, Cursor, VS Code, Windsurf and custom agents.