atx/registry

lodgedeck.vercel.app/api

https://lodgedeck.vercel.app/api/mcp

61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago

Why this score

tls_present_and_valid+4
mcp_capabilities_discoverable+4
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation1d ago129c0f7bb2114a0e…
http_response_observation1d ago256732befde0c2c7…
availability_observation1d ago7aa0f47255733806…
hosting_provider_observation1d ago07b610f7cd67ffa2…
tls_certificate_observation1d agoc56037c91c742c74…
oauth_metadata_observation1d ago67540d46652a639b…
mcp_protocol_observation1d agoff9a58f2c3c7c0d2…
mcp_capability_observation1d ago4f69e8f6281a220d…

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

Operate this service?

Prove control of lodgedeck.vercel.app/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →