atx/registry

rye.dev

https://rye.dev/mcp

59
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago

Why this score

oauth_metadata_present+14
tls.cert_expiring_soon-8
mcp.unauthenticated_consequential_tools-8
tls_present_and_valid+4
mcp_capabilities_discoverable+4
reachable+2
hsts_enabled+1

Findings (3)

mediumTLS certificate expires in 22 days
tls.cert_expiring_soon @ 1.0.0
mediumCapabilities are listable without authentication, including 2 whose names suggest state change (submit_contact, subscribe_newsletter) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation1d ago629348cc2a9ca99f…
http_response_observation1d ago2ad8db863764318e…
availability_observation1d ago062172c7edeb646b…
hosting_provider_observation1d agoe7292135d1d3f6bd…
tls_certificate_observation1d agofc4d2dc05f491b2a…
oauth_metadata_observation1d agoeca2aa161b3caad1…
mcp_protocol_observation1d agoeb30b039cbedb387…
mcp_capability_observation1d ago55decf50233cbebb…

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

Operate this service?

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

Claim this profile →