Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
M

Mopra/exit1.dev.mcp

Independent directory — not the official site. Details below come from the project's public repository.

MCP server for Exit1 uptime monitoring.

Before you install: a copy-paste endpoint config is available · license MIT

updated 2026-11-08
View on GitHub ↗Direct link · no redirect page
Install & config
Remote endpoint (mcpServers - Claude Desktop / Cursor / Windsurf)
{
  "mcpServers": {
    "mopra-exit1-dev-mcp": {
      "url": "https://app.exit1.dev/mcp/v1"
    }
  }
}
Paste this into the mcpServers config of Claude Desktop or Cursor. The endpoint comes from public evidence; we do not install or host it. Official Registry record: this endpoint lists no request headers. That is not the same as key-free - the project docs decide.
VS Code (.vscode/mcp.json - the key is servers, remote needs type: http)
{
  "servers": {
    "mopra-exit1-dev-mcp": {
      "type": "http",
      "url": "https://app.exit1.dev/mcp/v1"
    }
  }
}
VS Code differs from the other three: the top-level key is <code>servers</code> and a remote endpoint also needs <code>"type": "http"</code>. Paste into .vscode/mcp.json.
Claude Code (command line)
claude mcp add --transport http mopra-exit1-dev-mcp https://app.exit1.dev/mcp/v1
Claude Code does not read a config file; add the server with this command.
Config file: macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json, Linux ~/.config/Claude/claude_desktop_config.json. Key names differ by client: Clients & CLI
Star count
0 ★ · Mopra/exit1.dev.mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
Score
score 300 · 3 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository Mopra/exit1.dev.mcp;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

# exit1-mcp

Excerpted from the repository README (abridged)

MCP server for Exit1 uptime monitoring. Let your AI assistant set up monitoring for the project you just shipped — read your repo, create the checks, configure alerts, and send a real test alert to prove it works — then ask it about uptime in plain language afterwards.
## Two ways to connect
Hosted (recommended). No API key, no npm install, no plan requirement to get started. Run this in your terminal before starting a session: the login opens your browser, you sign in (or sign up) with Clerk, approve, and you're connected.
bash
claude mcp add --transport http exit1 https://app.exit1.dev/mcp/v1 && claude mcp login exit1
One line on purpose: pasting the two commands as separate lines is unreliable in some terminals (cmd.exe drops the second line). In old Windows PowerShell (5.1), where && doesn't parse, run the two halves one at a time. Connect before you start the session: MCP clients load servers at startup, so a server added mid-conversation isn't usable until a restart. On Claude Code versions without claude mcp login, start claude and authenticate via /mcp instead.
Local stdio. This npm package. Uses a Public API key from your dashboard. Use it when your client doesn't support remote MCP servers with OAuth.
bash
claude mcp add exit1 -- npx -y exit1-mcp
export EXIT1_API_KEY="ek_live_your_key_here"
Both expose the same tools. The hosted server is easier; the stdio one has no browser step, which some CI-ish setups prefer.
## No account yet? Let the agent create one
Started without EXIT1_API_KEY, the stdio server doesn't exit. It starts in setup mode and offers one extra tool, create_account. Your agent calls it with your email address, and exit1 creates a free account and connects the server to it on the spot. Every other tool works straight away, and monitors start running.
bash
claude mcp add exit1 -- npx -y exit1-mcp
# then, in the session: "Set up uptime monitoring for this project with exit1. My email is you@example.com."
Or from a terminal, before the session:
bash
npx exit1-mcp signup --email you@example.com
Either way exit1 emails you a link to claim the account. Alerts are only delivered once you claim it, so nobody can point exit1's alerts at an address they don't own. On the claim page you decide whether the agent keeps access. Unclaimed accounts are paused after 7 days and deleted after 30.
The tokens are saved to ~/.exit1/credentials.json and refreshed automatically, so later sessions connect without any setup. EXIT1_API_KEY, when set, always wins. Agents that don't use MCP can do the same with one HTTP call: see Agent signup.
## Zero to monitored
Connect the server (above), then paste this into Claude Code, Cursor, Codex or any MCP-capable assistant, from inside your project:
Set up uptime monitoring for this project with Exit1.
1. Call get_account to see my plan limits. If you have a create_account tool
instead, I have no account yet: ask for my email and call it. If the Exit1
tools aren't available to you at all, don't try to connect from inside this
session; tell me to add the HTTP MCP server https://app.exit1.dev/mcp/v1 in
my tool, restart it, and paste this prompt again.
2. Read this repo to find what should be monitored: deployed URLs in vercel.json /
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/mopra-exit1-dev-mcp/)
Source
awesome · https://github.com/Mopra/exit1.dev.mcp
Browse by field
MCP servers
Listed by
3 independent sources
added
today

More MCP servers

All 6,555 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index