atx/registry

www.hemmabo.com

https://www.hemmabo.com/mcp

67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago

Why this score

oauth_metadata_present+14
mcp.unauthenticated_consequential_tools-8
tls_present_and_valid+4
mcp_capabilities_discoverable+4
reachable+2
hsts_enabled+1

Findings (2)

mediumCapabilities are listable without authentication, including 3 whose names suggest state change (hemmabo_booking_cancel, hemmabo_booking_checkout, hemmabo_booking_create) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation2d ago10d8f855f992dcc2…
http_response_observation2d ago721c5e0e1394a97f…
availability_observation2d ago530fc98c9fdc5b86…
hosting_provider_observation2d ago07b610f7cd67ffa2…
tls_certificate_observation2d ago90b20f3b703d794e…
oauth_metadata_observation2d ago57be4caa125d15bb…
mcp_protocol_observation2d ago3d9b685684c4ef8e…
mcp_capability_observation2d ago6a08f97eddbf1971…

Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.

Operate this service?

Prove control of www.hemmabo.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →