atx/registry

api.bouncewatch.com/api/v1

https://api.bouncewatch.com/api/v1/mcp

75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1h ago

Why this score

oauth_metadata_present+14
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_observation1h ago5fd198522717e464…
http_response_observation1h agob74c829a642f4643…
availability_observation1h ago7450045f40eb09e2…
hosting_provider_observation1h agoe7292135d1d3f6bd…
tls_certificate_observation1h agoca9f31093e86ca59…
oauth_metadata_observation1h ago9ecea9caef0696c9…
mcp_protocol_observation1h ago97248e332c67928f…
mcp_capability_observation1h ago1344289342e6d63c…

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

Operate this service?

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

Claim this profile →