Exit1 Uptime Monitoring
connectsapp.exit1.dev
Set up uptime monitoring from your editor: create checks, configure alerts, query uptime history.
https://app.exit1.dev/mcp/v1WebsiteOAuthlast checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 262 msHow to authenticate
Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://app.exit1.dev |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✕Not advertised |
| PKCE | ✓S256 |
| Grant types | authorization_code, refresh_token |
| Scopes | checks:read, checks:write, alerts:read, alerts:write |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Refused — credentials required |
| Documentation | https://docs.exit1.dev/integrations/mcp |
Contract history
No contract recorded yet — the server has not answered an anonymous connection.
Run this server? A verified owner can publish snapshots with their own credentials, and the contract history starts here, marked owner-reported.
mcpi-cli publish https://app.exit1.dev/mcp/v1Get alerted when this contract changes
Depend on this server? Leave an email. No contract is on record here yet, so alerts can only start once one is published — and alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/exit1-uptime-monitoring)Own this server?
Sign in to claim this listing by proving control of the endpoint.