mcp.uptimepage.dev
https://mcp.uptimepage.dev/mcp
90
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +12 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
Findings (0)
No findings from the current evidence set.
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 354ae2746195e79b… |
| http_response_observation | 2d ago | 9390982176a332e9… |
| availability_observation | 2d ago | 8ec57330a0b20a52… |
| tls_certificate_observation | 2d ago | d13faf9e5c02b6a2… |
| oauth_metadata_observation | 2d ago | 6a23e80710d2a71b… |
| mcp_protocol_observation | 2d ago | fc0f3c3d093fc697… |
| mcp_capability_observation | 2d ago | 114cd6040c7be97e… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.uptimepage.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.