atx/registry

google.fetcher.sh

https://google.fetcher.sh/mcp

71
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 3h ago

Why this score

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

Findings (2)

lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0
infoCapability set changed: +0 / -3
mcp.capability_set_changed @ 1.0.0

Evidence (9)

TypeObservedSHA-256
dns_resolution_observation3h ago4a400cc8e224c1eb…
http_response_observation3h agoaa355d0fc53f93e1…
availability_observation3h ago40c40c644363ea2a…
hosting_provider_observation3h agoe7292135d1d3f6bd…
tls_certificate_observation3h ago812aa5318a4d4bc5…
oauth_metadata_observation3h agoe41ed79bed98d7ae…
mcp_protocol_observation3h ago0d9d89bf1b62904f…
mcp_capability_observation3h agoc3bbc19b8d2305a1…
mcp_capability_drift3h ago895f3e0290c97898…

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

Operate this service?

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

Claim this profile →