ai.upsalt.io/mcp/booking
https://ai.upsalt.io/mcp/booking
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 4h ago
Why this score
| tls_present_and_valid | +12 |
| mcp.unauthenticated_consequential_tools | -8 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
Findings (2)
| medium | Capabilities are listable without authentication, including 2 whose names suggest state change (cancel-booking, create-booking) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 4h ago | d3d0e98c8b1138a3… |
| http_response_observation | 4h ago | 765d9ce176f887b8… |
| availability_observation | 4h ago | c9b6c6988eff9b9a… |
| tls_certificate_observation | 4h ago | ba732241bfbb4642… |
| oauth_metadata_observation | 4h ago | a02d5be3c060e05c… |
| mcp_protocol_observation | 4h ago | 4c9538d29763fc4d… |
| mcp_capability_observation | 4h ago | 92cd9285bf1252c6… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of ai.upsalt.io/mcp/booking to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.