atx/registry

zaimhub.com/api

https://zaimhub.com/api/mcp

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

Why this score

tls_present_and_valid+12
reachable+6
mcp_capabilities_discoverable+4
headers.missing_hsts-3

Findings (2)

lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation2d agoaa17a746685c6ab1…
http_response_observation2d ago879824182da3e529…
availability_observation2d ago4a0bd9ed6d147ea6…
tls_certificate_observation2d agoe5adb4a08f6f8e79…
oauth_metadata_observation2d ago011a6b4159038638…
mcp_protocol_observation2d agoec3162bedbf91216…
mcp_capability_observation2d ago516a9b89896bbda0…

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

Operate this service?

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

Claim this profile →