atx/registry

api.readgzh.site/mcp-server

https://api.readgzh.site/mcp-server

61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago

Why this score

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_observation2d ago66fe21715fabbdbe…
http_response_observation2d agocf2b958b760d288e…
availability_observation2d agof7024e51c42eddfb…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d agoc6d467089a39ea1e…
oauth_metadata_observation2d agof3a21c8606c3dca9…
mcp_protocol_observation2d ago06ea1239417ffbc9…
mcp_capability_observation2d ago848c7551c1926314…

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

Operate this service?

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

Claim this profile →