app.exit1.dev/mcp/v1
https://app.exit1.dev/mcp/v1
77
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (2)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 256a0022acc1d2a1… |
| http_response_observation | 2d ago | cd7176cee5e5b006… |
| availability_observation | 2d ago | c667e55408b5ce79… |
| hosting_provider_observation | 2d ago | 958411567b2d9bdc… |
| tls_certificate_observation | 2d ago | 3a7211beb2264372… |
| oauth_metadata_observation | 2d ago | 3ba52395471ac9f6… |
| mcp_protocol_observation | 2d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of app.exit1.dev/mcp/v1 to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.