Exit1 Uptime Monitoring
REMOTE · APP.EXIT1.DEV · 2 COMPONENTS · SCANNED AUG 22
Set up uptime monitoring from your editor: create checks, configure alerts, query uptime history.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Exit1 Uptime Monitoring MCP server?
Exit1 Uptime Monitoring is a hosted endpoint at https://app.exit1.dev/mcp/v1, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · app.exit1.dev
claude mcp add --transport http dev-exit1-exit1-mcp 'https://app.exit1.dev/mcp/v1'
{
"mcpServers": {
"dev-exit1-exit1-mcp": {
"url": "https://app.exit1.dev/mcp/v1"
}
}
} {
"servers": {
"dev-exit1-exit1-mcp": {
"type": "http",
"url": "https://app.exit1.dev/mcp/v1"
}
}
} [mcp_servers.dev-exit1-exit1-mcp] url = "https://app.exit1.dev/mcp/v1"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-exit1-exit1-mcp": {
"type": "remote",
"url": "https://app.exit1.dev/mcp/v1",
"enabled": true
}
}
} openclaw mcp add dev-exit1-exit1-mcp --url 'https://app.exit1.dev/mcp/v1' --transport streamable-http
mcp_servers:
dev-exit1-exit1-mcp:
url: "https://app.exit1.dev/mcp/v1" {
"McpServers": {
"dev-exit1-exit1-mcp": {
"Transport": "http",
"Url": "https://app.exit1.dev/mcp/v1"
}
}
} assistant mcp add dev-exit1-exit1-mcp -t streamable-http -u 'https://app.exit1.dev/mcp/v1'
{
"mcpServers": {
"dev-exit1-exit1-mcp": {
"type": "http",
"url": "https://app.exit1.dev/mcp/v1"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 12 Aug 26 36
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Aug 2026 · Probed https://app.exit1.dev/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.exit1.dev | CN=WR3,O=Google Trust Services,C=US | 26 Jul 2026 | 24 Oct 2026 | RSA 2048 | SHA256-RSA | 194c6f13b16dc06c095ba30071f27e45 |
| SANs: app.exit1.dev, status.exit1.dev | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
DNSSEC insecure
Validation of app.exit1.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| exit1.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="exit1", resource_metadata="https://app.exit1.dev/.well-known/oauth-protected-resource"
Bearer realm="exit1", resource_metadata="https://app.exit1.dev/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| www-authenticate | Bearer realm="exit1", resource_metadata="https://app.exit1.dev/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://app.exit1.dev/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://app.exit1.dev/mcp/v1 |
| Authorisation server | https://app.exit1.dev |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.exit1.dev/mcp/v1 | Auth required | 401 | |
| http (plaintext) | http://app.exit1.dev/mcp/v1 | HTTPS enforced | 301 | https://app.exit1.dev/mcp/v1 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
No tool schema has been captured from this endpoint yet.
What is the Exit1 Uptime Monitoring MCP server?
Exit1 Uptime Monitoring is an MCP server listed in the public MCP registry as dev.exit1/exit1-mcp. Set up uptime monitoring from your editor: create checks, configure alerts, query uptime history. This page covers its hosted endpoint (https://app.exit1.dev/mcp/v1).
Is the Exit1 Uptime Monitoring MCP server safe to use?
Exit1 Uptime Monitoring scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Does the Exit1 Uptime Monitoring MCP server require authentication?
Yes. Exit1 Uptime Monitoring asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Exit1 Uptime Monitoring MCP server still maintained?
Exit1 Uptime Monitoring is still listed as active in the MCP registry. We last reached this channel on 22 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.