Exit1 Uptime Monitoring MCP Server

by exit1 Your server? Claim it

answering

Exit1 Uptime Monitoring is answering right now. Last checked 9 min ago. 335 installs a week from npm. Last commit 13 Oct 2026.

Set up uptime monitoring from your editor: create checks, alerts, and query uptime. Can sign you up.

Installs per day peak 11 · avg 4 · +25% w/w

a month agotoday

Uptime history 65 days of history · worst day 96%

65 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

256 ms

Response time

average over 24h

335

Installs / week

npm and PyPI

Exit1 Uptime Monitoring missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

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

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

This one needs environment variables set before it will start: EXIT1_API_KEY (Exit1 Public API key (ek_live_…), created at https://app.exit1.dev/api-keys. Optional: without it the server offers a create_account tool that signs the user up and connects automatically.), EXIT1_API_URL (Override the Exit1 API base URL. Development only.). The author declared them in the registry entry; get the values from the project itself.

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.exit1.dev/mcp/v1	streamable-http	sign-in	259 ms	9 min ago

Alternatives to Exit1 Uptime Monitoring

same job, measured the same way

Agent Health

by autonet

Free owned-agent uptime monitoring, DNS domain proof, signed alerts and opt-in endpoint checks.

46 tools answering

Uptimepage

by uptimepage

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

39 tools answering

UptyBots

by uptybots

Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks

35 installs/wk 15 tools answering

Sentinel

by rootstuff

Uptime, SSL, DNS and domain monitoring you can talk to from Claude or any MCP client.

answering

HostTracker

by hosttracker

Website uptime monitoring: run checks from 300+ locations, manage monitors, alerts and incidents

65 tools answering

OhSnap uptime monitoring

by ohsnap

Check if a website is down, add uptime monitors, read outage history and send test alerts.

6 tools answering

Vivere

by vivere

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

7 tools answering

UptimeRobot

by uptimerobot

Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.

answering

Exit1 Uptime Monitoring — questions

Answers built from our own checks of this server.

Why is there no tool list for Exit1 Uptime Monitoring?

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 Exit1 Uptime Monitoring 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 256 ms. The bar chart above shows every period we have measured.

How do I connect Exit1 Uptime Monitoring?

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 Exit1 Uptime Monitoring?

No API key is involved. Exit1 Uptime Monitoring 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 Exit1 Uptime Monitoring?

It answers our handshake in 256 ms on average, which is faster than 51% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Exit1 Uptime Monitoring?

The npm package exit1-mcp was installed 335 times in the last week. Week over week that is +25%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Exit1 Uptime Monitoring open source?

Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.