Exit1 MCP server
{
"mcpServers": {
"exit1": {
"command": "npx",
"args": [
"-y",
"exit1-mcp@latest"
],
"env": {
"EXIT1_API_KEY": "<exit1_api_key>",
"EXIT1_API_URL": "https://...",
"CATALOG_REMOTE_PATH": "/path/to/directory"
}
}
}
}{
"mcpServers": {
"exit1": {
"command": "npx",
"args": [
"-y",
"exit1-mcp@latest"
],
"env": {
"EXIT1_API_KEY": "<exit1_api_key>",
"EXIT1_API_URL": "https://...",
"CATALOG_REMOTE_PATH": "/path/to/directory"
}
}
}
}{
"mcpServers": {
"exit1": {
"command": "npx",
"args": [
"-y",
"exit1-mcp@latest"
],
"env": {
"EXIT1_API_KEY": "<exit1_api_key>",
"EXIT1_API_URL": "https://...",
"CATALOG_REMOTE_PATH": "/path/to/directory"
}
}
}
}{
"servers": {
"exit1": {
"command": "npx",
"args": [
"-y",
"exit1-mcp@latest"
],
"env": {
"EXIT1_API_KEY": "${input:exit1_api_key}",
"EXIT1_API_URL": "${input:exit1_api_url}",
"CATALOG_REMOTE_PATH": "${input:catalog_remote_path}"
}
}
},
"inputs": [
{
"id": "exit1_api_key",
"type": "promptString",
"description": "Exit1 api key",
"password": true
},
{
"id": "exit1_api_url",
"type": "promptString",
"description": "Exit1 api url",
"password": true
},
{
"id": "catalog_remote_path",
"type": "promptString",
"description": "Catalog remote path",
"password": true
}
]
}{
"mcpServers": {
"exit1": {
"command": "npx",
"args": [
"-y",
"exit1-mcp@latest"
],
"env": {
"EXIT1_API_KEY": "<exit1_api_key>",
"EXIT1_API_URL": "https://...",
"CATALOG_REMOTE_PATH": "/path/to/directory"
}
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y exit1-mcpversion 0.2.0
What it does
This MCP server connects to Exit1, an uptime monitoring service. It lets you create and manage website and API monitors, configure alerts, and query uptime history and status through your AI assistant.
- Create uptime checks for deployed URLs by scanning your repo for configuration files and health endpoints.
- Set up email and webhook alerts (Slack, Discord, Teams) for monitoring events, then send test alerts to verify delivery.
- Query uptime statistics, response times, and detailed check results over time to assess service reliability.
Tools this server exposes
| Tool | Does |
|---|---|
| get_account | Retrieve your Exit1 plan limits and current usage. |
| list_checks | List all monitors with their current status. |
| get_check | Get detailed information for a single check, including SSL certificate state. |
| get_check_history | Retrieve individual check results over time. |
| get_check_stats | Get uptime percentage and response time metrics across a date range. |
| get_status_page | Fetch a snapshot of a public Exit1 status page. |
| create_check | Create a new monitor for a website, API, ping, TCP port, DNS record, domain, or heartbeat. |
| update_check | Modify settings on an existing check. |
| toggle_check | Pause or resume a monitor. |
| delete_check | Permanently delete a monitor. |
| get_alert_settings | View current alert recipients and configured events. |
| set_email_alerts | Configure email recipients and alert events. |
| add_webhook_alert | Connect webhook alerts to Slack, Discord, Teams, or a custom endpoint. |
| send_test_alert | Send a test alert to verify configuration works. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.