atx/registry

relay.parsee.ru

https://relay.parsee.ru:8443/mcp

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

Why this score

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

Findings (2)

mediumCapabilities are listable without authentication, including 8 whose names suggest state change (parsee_add_to_group, parsee_create_group, parsee_delete_group, …) — 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 (7)

TypeObservedSHA-256
dns_resolution_observation2d ago68aa4008621b159a…
http_response_observation2d agobb6fdc6b1ea44f8e…
availability_observation2d ago8055ebca5ce743b8…
tls_certificate_observation2d agof7ef3874fd9aee62…
oauth_metadata_observation2d agoa4757f4071678172…
mcp_protocol_observation2d ago6a9215ab3a8f9d1f…
mcp_capability_observation2d ago0dea7de273742ac8…

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

Operate this service?

Prove control of relay.parsee.ru to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →