M
Mopra/exit1.dev.mcp
MCP server for Exit1 uptime monitoring.
更新 2026-11-08
在 GitHub 查看 ↗直链 · 无中转页
安装与配置
远端端点(Claude Desktop / Cursor / Windsurf 共用 mcpServers)
{
"mcpServers": {
"mopra-exit1-dev-mcp": {
"url": "https://app.exit1.dev/mcp/v1"
}
}
}把这段粘进 Claude Desktop / Cursor 的 mcpServers 配置即可。端点来自公开证据,我们没有替你安装或托管它。 官方 Registry 记录:这个端点没有列出任何请求头。这不等于免密 —— 以项目文档为准。
VS Code(.vscode/mcp.json —— 键名是 servers,远程要 type: http)
{
"servers": {
"mopra-exit1-dev-mcp": {
"type": "http",
"url": "https://app.exit1.dev/mcp/v1"
}
}
}VS Code 的配置文件和另外三家不同:顶层键是 <code>servers</code>,远程端点还要写 <code>"type": "http"</code>。复制到 .vscode/mcp.json。
Claude Code(命令行)
claude mcp add --transport http mopra-exit1-dev-mcp https://app.exit1.dev/mcp/v1
Claude Code 不收 JSON 文件,用这条命令直接加。
配置文件在:macOS
~/Library/Application Support/Claude/claude_desktop_config.json、Windows %APPDATA%\Claude\claude_desktop_config.json、Linux ~/.config/Claude/claude_desktop_config.json。配置项的键名以你的客户端为准:客户端与 CLI- ★ 数取值
- 0 ★ · Mopra/exit1.dev.mcp · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
怎么安装?
我们【没有】从该仓库取到安装命令(我们的 install 覆盖率只有约 4%)。请看它的 README 或 releases 页。
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
Mopra/exit1.dev.mcp;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# exit1-mcp
以下摘录自该仓库的 README(片段)
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 /
## 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 /
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/mopra-exit1-dev-mcp/)
- 来源
- awesome · https://github.com/Mopra/exit1.dev.mcp
- 按领域浏览
- MCP 服务
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。