atx/registry

junglecleaner.com/api

https://junglecleaner.com/api/mcp

81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 3h 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_observation3h agoed5ad85a7f002833…
http_response_observation3h agof87920f412cfe9f6…
availability_observation3h agof20ed53859cd17e4…
hosting_provider_observation3h ago07b610f7cd67ffa2…
tls_certificate_observation3h ago10e97a67cadfd205…
oauth_metadata_observation3h ago141d713578c4de3c…
mcp_protocol_observation3h ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →