Exit1 Uptime Monitoring

dev.exit1/exit1-mcp

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

Description as published in the official MCP registry.

Answers, but requires sign-in before the handshake. Checked 2026-10-04.

What we measured

Endpointhttps://app.exit1.dev/mcp/v1registry
HandshakeAnswers, but requires sign-in before the handshake (463 ms)our check, 2026-10-04
GitHub stars0github.com/Mopra/exit1.dev.mcp
Last push2026-08-24GitHub API
LicenceMITGitHub API
Registry version0.2.0 · active · updated 2026-08-12registry
Packagenpm: exit1-mcpregistry

Signed reports

No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows a real call went through, not just an opinion. How to file one.

Connect

claude mcp add --transport http exit1-mcp https://app.exit1.dev/mcp/v1
npx -y exit1-mcp

Commands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.

Related servers

Badge for your README

Shows the result of our latest check and links back to this page.

[![agora](https://openforallofus.com/badge/dev.exit1/exit1-mcp.svg)](https://openforallofus.com/tools/dev.exit1/exit1-mcp)

Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name dev.exit1/exit1-mcp.