SERVER

Exit1 Uptime Monitoring

Rank #72,373

dev.exit1/exit1-mcp

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

1 version

by Mopra (1 servers)View repository ↗Claim this server

Listed & last published

Aug 12, 2026

OVERVIEW

Exit1 Uptime Monitoring is a Model Context Protocol (MCP) server published by Mopra. It ranks #72,373 of 137,492 servers tracked on MCP Toplist. Exit1 Uptime Monitoring is listed across 2 registries — Official MCP and Glama, with 1 tracked version. It was first listed on Aug 12, 2026 and most recently updated on Aug 12, 2026.

STANDING

#72,373of 137,492 tracked servers

Ranks ahead of 65,119 of 137,492 servers on MCP Toplist.

CONNECT

Use Exit1 Uptime Monitoring

No setupRuns out of the box

No credentials or required configuration declared — add it to your MCP client and go.

Remote · HTTP

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

npm package

claude mcp add exit1-mcp -e "EXIT1_API_KEY=<your EXIT1_API_KEY>" -e "EXIT1_API_URL=<your EXIT1_API_URL>" -- npx -y exit1-mcp

Replace each placeholder with your own value before saving.

Remote · HTTP

[mcp_servers.exit1-mcp]
url = "https://app.exit1.dev/mcp/v1"

Add to ~/.codex/config.toml.

npm package

[mcp_servers.exit1-mcp]
command = "npx"
args = ["-y", "exit1-mcp"]

[mcp_servers.exit1-mcp.env]
EXIT1_API_KEY = "<your EXIT1_API_KEY>"
EXIT1_API_URL = "<your EXIT1_API_URL>"

Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.

Remote · HTTP

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

Settings → Connectors → “Add custom connector”, then paste this URL.

npm package

{
  "mcpServers": {
    "exit1-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "exit1-mcp"
      ],
      "env": {
        "EXIT1_API_KEY": "<your EXIT1_API_KEY>",
        "EXIT1_API_URL": "<your EXIT1_API_URL>"
      }
    }
  }
}

Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.

Remote · HTTP

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

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project).

npm package

{
  "mcpServers": {
    "exit1-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "exit1-mcp"
      ],
      "env": {
        "EXIT1_API_KEY": "<your EXIT1_API_KEY>",
        "EXIT1_API_URL": "<your EXIT1_API_URL>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.

Remote · HTTP

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

Save as .vscode/mcp.json in your workspace.

npm package

{
  "servers": {
    "exit1-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "exit1-mcp"
      ],
      "env": {
        "EXIT1_API_KEY": "<your EXIT1_API_KEY>",
        "EXIT1_API_URL": "<your EXIT1_API_URL>"
      }
    }
  }
}

Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.

Remote · HTTP

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

Add to ~/.codeium/windsurf/mcp_config.json.

npm package

{
  "mcpServers": {
    "exit1-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "exit1-mcp"
      ],
      "env": {
        "EXIT1_API_KEY": "<your EXIT1_API_KEY>",
        "EXIT1_API_URL": "<your EXIT1_API_URL>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.

Remote · HTTP

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

npm package

{
  "mcpServers": {
    "exit1-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "exit1-mcp"
      ],
      "env": {
        "EXIT1_API_KEY": "<your EXIT1_API_KEY>",
        "EXIT1_API_URL": "<your EXIT1_API_URL>"
      }
    }
  }
}

Replace each placeholder with your own value before saving.

BADGE

Show your rank

Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.

Markdown

[![MCP Toplist](https://mcptoplist.com/badge/dev.exit1%2Fexit1-mcp.svg)](https://mcptoplist.com/server/dev.exit1%2Fexit1-mcp)

HTML

<a href="https://mcptoplist.com/server/dev.exit1%2Fexit1-mcp"><img src="https://mcptoplist.com/badge/dev.exit1%2Fexit1-mcp.svg" alt="MCP Toplist: #72,373 of 137,492" /></a>

Variants: append ?metric=score or ?metric=stars to the image URL.

REGISTRIES

Listed on 2 registries

Official MCP

Glama

ORGANIZATION

Mopra

Organization

Mopra

Servers in org

Versions across org

VERSIONS

Available versions (1)

Version	Published
0.2.0	Aug 12, 2026

FAQ

Frequently asked questions

Who maintains Exit1 Uptime Monitoring?: Exit1 Uptime Monitoring is maintained by Mopra, which publishes 1 MCP server (1 total version) tracked on MCP Toplist.
Is Exit1 Uptime Monitoring listed on the Official MCP Registry?: Yes — Exit1 Uptime Monitoring is listed on the Official MCP Registry, alongside Glama.
How many versions does Exit1 Uptime Monitoring have?: MCP Toplist tracks 1 version of Exit1 Uptime Monitoring, most recently published on Aug 12, 2026.
Where can I find the source code for Exit1 Uptime Monitoring?: The source code for Exit1 Uptime Monitoring is hosted at github.com/Mopra/exit1.dev.mcp.

Used in projects

Do you run this server?

Add to a project

Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.

EXPLORE

All MCP Servers Official MCP Servers GitHub MCP Servers Best MCP Servers Most Active MCP Servers New MCP Servers Best New MCP Servers