hypernatt.com/mcp/protocol
https://hypernatt.com/mcp/protocol
68
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 7d ago
Why this score
| tls_present_and_valid | +12 |
| tls.cert_expiring_soon | -8 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
Findings (1)
| medium | TLS certificate expires in 27 days tls.cert_expiring_soon @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 7d ago | c8e71dbca7d01de4… |
| http_response_observation | 7d ago | 256a193690bbee75… |
| availability_observation | 7d ago | 963f1f169e9d6885… |
| tls_certificate_observation | 7d ago | eb293b809141e4ad… |
| oauth_metadata_observation | 7d ago | b41b1b1934b0d8bb… |
| mcp_protocol_observation | 7d ago | 815fd567a689bac9… |
| mcp_capability_observation | 7d ago | 145325e30cbf56a7… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of hypernatt.com/mcp/protocol to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.