Index / MCP servers / Exit1 Uptime Monitoring

Exit1 Uptime Monitoring MCP server

Exit1 Uptime Monitoring is the official remote MCP server from exit1.dev. It answers at https://app.exit1.dev/mcp/v1 over streamable HTTP and asks you to sign in with your exit1.dev account before it lists its tools, so your client opens a login the first time it connects. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, got the sign-in challenge, so it is up.

Status
Answering
Tools
listed after sign-in
Official
yes, served from exit1.dev
Reliability
10 of 10 checks
Response time
372 ms
Transport
streamable HTTP
Last checked
18 October 2026

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

Description as the publisher wrote it.

What Exit1 Uptime Monitoring needs before it works

A sign-in. The server refused to list its tools to an anonymous client and answered with an authentication challenge, which is how an MCP server protected by OAuth behaves. Add it with one of the setups below; the first connection opens a login for your exit1.dev account, and the tools appear once you have approved it.

Add Exit1 Uptime Monitoring to your AI client

Every block below points at https://app.exit1.dev/mcp/v1. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http exit1-uptime-monitoring https://app.exit1.dev/mcp/v1
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "exit1-uptime-monitoring": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.exit1.dev/mcp/v1"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "exit1-uptime-monitoring": {
      "url": "https://app.exit1.dev/mcp/v1"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "exit1-uptime-monitoring": {
      "type": "http",
      "url": "https://app.exit1.dev/mcp/v1"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "exit1-uptime-monitoring": {
      "url": "https://app.exit1.dev/mcp/v1"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "exit1-uptime-monitoring": {
      "serverUrl": "https://app.exit1.dev/mcp/v1"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "exit1-uptime-monitoring": {
      "url": "https://app.exit1.dev/mcp/v1"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Exit1 Uptime Monitoring
version: 0.0.1
schema: v1
mcpServers:
  - name: Exit1 Uptime Monitoring
    type: streamable-http
    url: https://app.exit1.dev/mcp/v1
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "exit1-uptime-monitoring": {
      "httpUrl": "https://app.exit1.dev/mcp/v1"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "exit1-uptime-monitoring": {
      "type": "http",
      "url": "https://app.exit1.dev/mcp/v1"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "exit1-uptime-monitoring": {
      "url": "https://app.exit1.dev/mcp/v1"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fapp.exit1.dev%2Fmcp%2Fv1&type=streamable_http&id=exit1-uptime-monitoring&name=Exit1%20Uptime%20Monitoring

Is Exit1 Uptime Monitoring up right now?

It answered our last check on 18 October 2026 in 372 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Exit1 Uptime Monitoring

Questions about Exit1 Uptime Monitoring

Is there an official Exit1 Uptime Monitoring MCP server?

Yes. It is published by exit1.dev and served from app.exit1.dev, the vendor's own domain: https://app.exit1.dev/mcp/v1.

How do I sign in to Exit1 Uptime Monitoring?

Add the server with a setup above. The first time your client connects it opens the sign-in page for exit1.dev; approve it and the tools load.

Is Exit1 Uptime Monitoring down?

It answered our last check on 18 October 2026 in 372 ms. Over 10 checks since 5 September 2026 it answered 10.

How do I add Exit1 Uptime Monitoring to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://app.exit1.dev/mcp/v1. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Exit1 Uptime Monitoring need an API key?

It needs a sign-in rather than a key you paste: the server answered with an authentication challenge, so your client runs the login when it first connects.

Where this comes from

Publisher: dev.exit1. Endpoint host: app.exit1.dev. ARD identifier: urn:air:dev.exit1:mcp:exit1-mcp. First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.