exit1-mcp

MCPcommunitylive
v0.2.0Exit1MITUpdated 1mo agonpmGitHub

MCP server for Exit1 uptime monitoring — set up monitors, configure alerts, and query uptime from AI assistants

Endpoint healthlive
checked 2 days ago · 263ms · auth required
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5Downloads/wk
1mo agoLast update
Package
AuthorExit1
LicenseMIT
Version0.2.0
Sourcenpm+mcp-registry
npmexit1-mcp
GitHubMopra/exit1.dev.mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface15 tools · 1 privileged
Security scan✓ Cleanv0.2.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

15 tools · 1 privileged
Statically extracted from the published packagev0.2.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_accountNo description published

This tool published no description. Forge does not invent one.

list_checksNo description published

This tool published no description. Forge does not invent one.

get_checkNo description published

This tool published no description. Forge does not invent one.

get_check_historyNo description published

This tool published no description. Forge does not invent one.

get_check_statsNo description published

This tool published no description. Forge does not invent one.

get_status_pageNo description published

This tool published no description. Forge does not invent one.

create_checkNo description published

This tool published no description. Forge does not invent one.

update_checkNo description published

This tool published no description. Forge does not invent one.

toggle_checkNo description published

This tool published no description. Forge does not invent one.

delete_checkprivilegedNo description published

This tool published no description. Forge does not invent one.

get_alert_settingsNo description published

This tool published no description. Forge does not invent one.

set_email_alertsNo description published

This tool published no description. Forge does not invent one.

add_webhook_alertNo description published

This tool published no description. Forge does not invent one.

send_test_alertNo description published

This tool published no description. Forge does not invent one.

setup_monitoringNo description published

This tool published no description. Forge does not invent one.

0 of 15 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for Exit1 uptime monitoring — set up monitors, configure alerts, and query uptime from AI assistants

Keywords
mcpexit1uptimemonitoringmodel-context-protocolobservabilityalerting
Alternatives
Comparing tool surfaces…

Tools exposed

15 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in monitoring & logging