atx/registry

blueauth.co/api/mcp-server

https://blueauth.co/api/mcp-server/mcp

67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1h ago

Why this score

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_observation1h ago1627beb34fc37c19…
http_response_observation1h ago70e504d33b159943…
availability_observation1h agoef59324fe49e4830…
hosting_provider_observation1h ago958411567b2d9bdc…
tls_certificate_observation1h ago466797c75d8fe5b5…
oauth_metadata_observation1h agoc6290122ba589dcc…
mcp_protocol_observation1h ago5f4c66c82509bed4…

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

Operate this service?

Prove control of blueauth.co/api/mcp-server to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →