Exit1 Uptime Monitoring
NPM · EXIT1-MCP · 2 COMPONENTS
Set up uptime monitoring from your editor: create checks, alerts, and query uptime. Can sign you up.
Available components
Last scanned (2 hours ago)
Scores higher than 44% of npm servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1843 tokens (~122/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 14 Oct 26 +33
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: good functional
- First check of Tool coverage: 82 functional
- 12 Oct 26 0
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.2.0 → 0.4.0 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
- 14 Aug 26 0
- Security disclosure: fail → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Analysed npm/exit1-mcp@0.4.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_webhook_alert Add webhook alert ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | Defaults to website_down + website_up |
| name | string | yes | Label shown in the dashboard, e.g. '#alerts' |
| secret | string | – | Optional HMAC signing secret for generic webhooks |
| url | string | yes | HTTPS webhook URL (e.g. a Slack incoming webhook) |
| webhook_type | string | – | Override auto-detection |
No output schema declared.
No examples provided.
create_account Create an exit1 account ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | How you identify yourself to the user in the claim email, e.g. "Claude Code". |
| string | yes | The user's email address. Ask them if you don't know it. |
No output schema declared.
No examples provided.
create_check Create check ~317
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.
| Name | Type | Req | Description |
|---|---|---|---|
| check_frequency_minutes | number | – | Minutes between checks. Must be >= the plan's minCheckIntervalMinutes. |
| expected_status_codes | array | – | Status codes treated as healthy. Defaults to 2xx. |
| http_method | string | – | – |
| name | string | – | Human-readable name, e.g. 'Production API' |
| record_types | array | – | DNS record types to baseline (type 'dns' only) |
| request_body | string | – | JSON request body for POST/PUT/PATCH rest_endpoint checks |
| request_headers | object | – | Extra request headers. Do not put secrets here that you would not paste into a dashboard. |
| response_time_limit_ms | number | – | Fail the check if it responds slower than this |
| response_validation | object | – | Body assertions: this is what turns a 200 into a real health check. |
| type | string | – | Check type (default 'website') |
| url | string | – | URL to monitor. For 'dns' and 'domain' pass a bare domain. Omit for 'heartbeat'. |
No output schema declared.
No examples provided.
delete_check Delete check ~52
Permanently delete a check and stop monitoring it. This cannot be undone. Prefer toggle_check unless the user explicitly wants it gone.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | The check ID returned by list_checks or create_check |
No output schema declared.
No examples provided.
get_account Get account ~65
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_alert_settings Get alert settings ~39
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_check Get check ~45
Get full detail for one check: status, response time, SSL certificate state and maintenance mode.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | The check ID returned by list_checks or create_check |
No output schema declared.
No examples provided.
get_check_history Get check history ~129
Get individual check results over time — timestamps, status codes, response times and errors. Use when investigating an incident or confirming a fix held.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | The check ID returned by list_checks or create_check |
| from | string | – | Start date, ISO 8601 (e.g. 2026-07-01T00:00:00Z) |
| limit | integer | – | Results per page (default 25) |
| page | integer | – | – |
| status | string | – | – |
| to | string | – | End date, ISO 8601 |
No output schema declared.
No examples provided.
get_check_stats Get check stats ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | The check ID returned by list_checks or create_check |
| ranges | string | – | Comma-separated ranges: 1h, 6h, 1d, 7d, 30d, 60d, 90d. Default 1d,7d,30d |
No output schema declared.
No examples provided.
get_status_page Get status page ~41
Get the current snapshot of a public status page, with each check's status and uptime percentage.
| Name | Type | Req | Description |
|---|---|---|---|
| status_page_id | string | yes | The status page ID |
No output schema declared.
No examples provided.
list_checks List checks ~205
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.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Only checks in this folder, as a path like "Clients/Acme" (exact match unless recursive is true) |
| include | string | – | Set to "uptime" to add uptime24hPercent, uptime30dPercent and avgResponseTime24hMs to each check (null when unavailable) |
| limit | integer | – | Results per page (default 25) |
| page | integer | – | Page number |
| recursive | boolean | – | With folder, also include checks in its subfolders (default false) |
| status | string | – | Filter by current status |
No output schema declared.
No examples provided.
send_test_alert Send test alert ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Which channel to test |
| webhook_id | string | – | Required when channel is 'webhook' |
No output schema declared.
No examples provided.
set_email_alerts Configure email alerts ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | – | Turn email alerting on or off (default true) |
| events | array | – | Events to alert on |
| format | string | – | Use 'text' for ticketing systems |
| recipients | array | – | Email addresses that should receive alerts |
No output schema declared.
No examples provided.
toggle_check Enable or disable check ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | The check ID returned by list_checks or create_check |
| disabled | boolean | yes | true to pause the check, false to resume it |
No output schema declared.
No examples provided.
update_check Update check ~106
Change an existing check's settings. Only the fields you pass are modified.
| Name | Type | Req | Description |
|---|---|---|---|
| check_frequency_minutes | number | – | – |
| check_id | string | yes | The check ID returned by list_checks or create_check |
| expected_status_codes | array | – | – |
| http_method | string | – | – |
| name | string | – | – |
| response_time_limit_ms | number | – | – |
| response_validation | object | – | Same shape as create_check.response_validation |
| url | string | – | – |
No output schema declared.
No examples provided.
How do I install the Exit1 Uptime Monitoring MCP server?
Exit1 Uptime Monitoring runs locally as an npm package, launched with npx -y exit1-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · exit1-mcp
claude mcp add dev-exit1-exit1-mcp -- npx -y exit1-mcp
What is the Exit1 Uptime Monitoring MCP server?
Exit1 Uptime Monitoring is an MCP server listed in the public MCP registry as dev.exit1/exit1-mcp. Set up uptime monitoring from your editor: create checks, alerts, and query uptime. Can sign you up. This page covers its npm package (exit1-mcp).
Is the Exit1 Uptime Monitoring MCP server safe to use?
Exit1 Uptime Monitoring scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Exit1 Uptime Monitoring MCP server expose?
Exit1 Uptime Monitoring exposes 15 tools: create_account, get_account, list_checks, get_check, get_check_history, and 10 more. Their descriptions and schemas cost roughly 1,659 tokens of context every time the server is loaded.
Is the Exit1 Uptime Monitoring MCP server still maintained?
Exit1 Uptime Monitoring is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Exit1 Uptime Monitoring MCP server under?
Exit1 Uptime Monitoring declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.