mcpbeat Sign in

Exit1 Uptime Monitoring MCP Server

by exit1 Your server? Claim it
answering

Exit1 Uptime Monitoring is answering right now. Last checked 1 min ago. 75 installs a week from npm. Last commit 24 Aug 2026.

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

Installs per day peak 139 · avg 6 · +18700% w/w
a month agotoday
Uptime history 20 days of history · worst day 99%
20 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
381 ms
Response time
average over 24h
75
Installs / week
npm and PyPI

Nothing serious here today

Today is the operative word: we check Exit1 Uptime Monitoring every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

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

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 endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://app.exit1.dev/mcp/v1 streamable-http needs key 292 ms 1 min ago

Alternatives to Exit1 Uptime Monitoring

same job, measured the same way
DevHelm MCP Server
by devhelmhq

Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm

453 installs/wk local only
UptyBots
by uptybots

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

155 installs/wk 15 tools answering
D
Watchpup
by workers-watchpup-watchpup

Free uptime monitoring: HTTP/TCP/TLS/DNS + MCP server checks, cron heartbeats, status pages, alerts.

12 tools answering
Uptimepage
by uptimepage

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

15 tools answering
HostTracker
by hosttracker

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

65 tools answering
Safeship
by safeship

API monitoring from your editor. Checks the JSON your endpoints return, not just the status code.

answering
Checkly
by usefulapi

Query Checkly synthetic monitoring — checks, statuses, results, alerts, reporting and dashboards.

22 tools answering
Xitoring
by xitoring

Connect AI assistants to Xitoring monitoring: servers, uptime, incidents, metrics, SSL, and alerts.

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 381 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 will need your own key or an OAuth login: it refuses anonymous clients.
Does Exit1 Uptime Monitoring need an API key?
Yes. Every time we knock, Exit1 Uptime Monitoring answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Exit1 Uptime Monitoring?
It answers our handshake in 381 ms on average, which is faster than 46% 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 75 times in the last week. Week over week that is +18700%. 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.