atx/registry

api.hyperping.io/v1

https://api.hyperping.io/v1/mcp

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

Why this score

mcp.unauthenticated_consequential_tools-8
tls_present_and_valid+4
mcp_capabilities_discoverable+4
headers.missing_hsts-3
reachable+2

Findings (2)

mediumCapabilities are listable without authentication, including 2 whose names suggest state change (create_monitor, update_monitor) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation2d ago6b599afee603268a…
http_response_observation2d ago55d5192cceac30a5…
availability_observation2d ago0cbf156b13abfe99…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago934ec94eb62e9c39…
oauth_metadata_observation2d ago65d4b9f62833467f…
mcp_protocol_observation2d agofacdecaaa4d72f15…
mcp_capability_observation2d ago82ee9593ff120c24…

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

Operate this service?

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

Claim this profile →