atx/registry

yelp.fetcher.sh

https://yelp.fetcher.sh/mcp

71
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 6d ago

Why this score

oauth_metadata_present+14
tls_present_and_valid+4
mcp_capabilities_discoverable+4
headers.missing_hsts-3
reachable+2

Findings (1)

lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation6d agod8290b0e30058a98…
http_response_observation6d agobd36ad4a195402d4…
availability_observation6d ago40f037c1e9635a0c…
hosting_provider_observation6d agoe7292135d1d3f6bd…
tls_certificate_observation6d ago3e2b5f3d841ec153…
oauth_metadata_observation6d ago84176fe8d672100f…
mcp_protocol_observation6d ago266db67ae5e5d0e2…
mcp_capability_observation6d agoa52bdb59ee529136…

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

Operate this service?

Prove control of yelp.fetcher.sh to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →