Skip to content
mcp/skillhub

Exit1 Uptime Monitoring MCP Server

by mopradev.exit1/exit1-mcpv0.2.0

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

0Node.jsstdioremoteofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Maintained46d ago

Install Exit1 Uptime Monitoring MCP server

Install in Claude Code

claude mcp add exit1 -e EXIT1_API_KEY='<exit1-api-key>' -- npx -y exit1-mcp

Configuration

VariableRequiredSecretDescription
EXIT1_API_KEYyesyesExit1 Public API key (ek_live_…), created at https://app.exit1.dev/api-keys. Requires an Indie plan or higher.
EXIT1_API_URL——Override the Exit1 API base URL. Development only.

Remote endpoints

  • streamable-httphttps://app.exit1.dev/mcp/v1

Freshness

Maintained — last maintenance signal 46d ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-08-24 · 46d ago · GitHub

  2. Latest release

    no data · GitHub

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-08-12 · 58d ago · official registry · v0.2.0

FAQ

›How do I install the Exit1 Uptime Monitoring MCP server in Claude Code?

Run: claude mcp add exit1 -e EXIT1_API_KEY='<exit1-api-key>' -- npx -y exit1-mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Exit1 Uptime Monitoring require an API key?

Yes. It expects EXIT1_API_KEY, of which 1 is a secret.

›Can I use Exit1 Uptime Monitoring as a remote (hosted) MCP server?

Yes — it offers both a hosted endpoint and a local stdio package.

›Is Exit1 Uptime Monitoring in the official MCP registry?

Yes, as dev.exit1/exit1-mcp.

Alternatives to Exit1 Uptime Monitoring

Other monitoring & observability MCP servers.

View all