Exit1 Uptime Monitoring

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

Connector by exit1.devOfficial · Domain verified by the MCP Registry

IndexedMITLocal (stdio)Remote (HTTP)

Install

Works with Claude Code, VS Code, Codex, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/exit1-dev-exit1-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Remote endpoint

https://app.exit1.dev/mcp/v1 Remote (HTTP)

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

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

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools: 7 read · 7 write · 1 delete
Secrets: 1 (API keys, tokens or passwords)
Install scripts: None found
Runs as: Node.js package

Tools by what they do 15

Read from the source code; the running server may list different tools.

Read 7 · Look things up without changing anything.

get_account
get_alert_settings
get_check
get_check_history
get_check_stats
get_status_page
list_checks

Write 7 · Create, change, send or run things.

add_webhook_alert
create_account
create_check
send_test_alert
set_email_alerts
toggle_check
update_check

Delete 1 · Delete, drop, revoke or wipe things.

delete_check

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

EXIT1_API_KEY

Other settings (environment variables or headers).

EXIT1_API_URL

Network hosts it talks to 1

app.exit1.dev · found in remote endpoint, install command

Files it touches

Any path the agent passes to its tools

Tools (15)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

add_webhook_alertAdd webhook alert
Send alerts to Slack, Discord, Microsoft Teams or any HTTPS endpoint. Paste the incoming-webhook URL the user gives you; the platform is detected from the URL if you do not pass webhook_type.
create_accountCreate an exit1 account
Create a free exit1 account for the user and connect this server to it, so the other tools work right away. Use the user's own email address: exit1 emails it a link to claim the account, and alerts are only delivered once they claim it. Monitors you create before then start running immediately. Fails if the email already has an account; then ask the user for an API key instead.
create_checkCreate check
Create a new monitor. Use 'website' for a page that should return 200, 'rest_endpoint' for an API endpoint (supports JSONPath assertions on the response body), 'ping' for ICMP, 'tcp' for a raw port, 'dns' for record drift, 'domain' for registration expiry, and 'heartbeat' for cron jobs that call in. Check the plan's minCheckIntervalMinutes via get_account before setting check_frequency_minutes.
delete_checkDelete check
Permanently delete a check and stop monitoring it. This cannot be undone. Prefer toggle_check unless the user explicitly wants it gone.
get_accountGet account
Get the current plan, its limits, and how much of them is already used. Call this FIRST when setting up monitoring — it tells you how many checks you can create and the fastest check interval the plan allows, so you can plan within the plan instead of hitting errors halfway through.
get_alert_settingsGet alert settings
Show where alerts currently go — email recipients and connected webhooks. Call this before configuring alerts so you do not duplicate a channel the user already has.
get_checkGet check
Get full detail for one check: status, response time, SSL certificate state and maintenance mode.
get_check_historyGet check history
Get individual check results over time — timestamps, status codes, response times and errors. Use when investigating an incident or confirming a fix held.
get_check_statsGet check stats
Get aggregate uptime percentage and response-time statistics for a check across one or more time ranges. Good for 'how has this been doing' questions and week-over-week comparisons.
get_status_pageGet status page
Get the current snapshot of a public status page, with each check's status and uptime percentage.
list_checksList checks
List monitored checks with their current status and folder. Use for an overview, to find offline checks, or to see what is already monitored before creating duplicates. Pass folder to list one folder; add recursive to include its subfolders. Pass include="uptime" to add 24h and 30d uptime percentages and the 24h average response time to each check.
send_test_alertSend test alert
Fire a real test alert so the user can confirm delivery works. ALWAYS finish a monitoring setup with this — a channel that was configured but never tested is the most common way monitoring silently fails. Pass channel='email' or channel='webhook' with a webhook_id.
set_email_alertsConfigure email alerts
Set which email addresses receive alerts and which events trigger them. Events: website_down, website_up, website_error, ssl_error, ssl_warning, domain_expiring, domain_expired, domain_renewed. Defaults to website_down + website_up, which is the right pair for most people.
toggle_checkEnable or disable check
Enable or disable a check without deleting it. Disabled checks stop probing and stop alerting — use this rather than delete_check for a temporary pause.
update_checkUpdate check
Change an existing check's settings. Only the fields you pass are modified.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit: Oct 12, 2026 (16 days ago)
Last release: Oct 12, 2026 (16 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name: dev.exit1/exit1-mcp
Version: 0.4.0
Auth: Auth not stated, API key
Packages: npm exit1-mcp
License: MIT
Repository: github.com/Mopra/exit1.dev.mcp
Website: exit1.dev
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: Official MCP Registry github-graphql

Rank

of 44,833 in Connectors

Score

0.593

Security 30%not yet
Popularity 25%0.29
Freshness 20%1.00
Rating 15%not yet
Docs 10%0.94

How ranking works →

Grades

Freshness

Active in the last 30 days. Last activity 16 days ago.

–

Security

Security scan: in progress. Grades from our dependency, secret, code and prompt-injection checks appear here once they launch. Until then, check the code before you install.

Indexed

Found automatically from a public source. Not yet claimed by its publisher.

How grades work →

Availability

100% uptime, last 30 days (1 check)

Last check: 3 days ago
Status: Up, asks for a login or key
Median response: 374 ms

Up
Up, auth required
Down
Not checked
No data

A daily MCP handshake with the remote endpoint. “Auth required” means it answered and wants a login or key. “Not checked” means the URL needs your own account or blocks automated checks.

Is this yours?

Claim it to add pricing, screenshots and docs, and to get a verified badge.

Claim listing Suggest a fix

Report a security problem

Cite this page

Exit1 Uptime Monitoring MCP server. Agent Mart. https://agentmart.dev/connectors/exit1-dev-exit1-mcp (last updated 2026-10-24)