atx/registry

varosity.ai/api

https://varosity.ai/api/mcp

81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 10h ago

Why this score

oauth_metadata_present+14
mcp_requires_authentication+10
tls_present_and_valid+4
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation10h ago27efd09a812e46d6…
http_response_observation10h ago2dcf9b9e9c9d5349…
availability_observation10h agob98da71b3d38f072…
hosting_provider_observation10h ago07b610f7cd67ffa2…
tls_certificate_observation10h ago9f37736c69df7c61…
oauth_metadata_observation10h ago6eff7cc27a040bd9…
mcp_protocol_observation10h ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →