atx/registry

ai.upsalt.io/mcp/booking

https://ai.upsalt.io/mcp/booking

61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 8h 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)

mediumCapabilities 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
lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation8h agod3d0e98c8b1138a3…
http_response_observation8h ago765d9ce176f887b8…
availability_observation8h ago5dfdb44d7893f56f…
tls_certificate_observation8h ago85f11c2fba546062…
oauth_metadata_observation8h agoa02d5be3c060e05c…
mcp_protocol_observation8h ago3ffed792b1e520cf…
mcp_capability_observation8h ago9ac6c9b4b72f57bb…

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.

Claim this profile →