atx/registry

rides.rs/api

https://rides.rs/api/mcp

53
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 6d ago

Why this score

mcp.unauthenticated_consequential_tools-8
tls_present_and_valid+4
mcp_capabilities_discoverable+4
reachable+2
hsts_enabled+1

Findings (2)

mediumCapabilities are listable without authentication, including 1 whose name suggests state change (create_booking_request) — 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_observation6d ago9d2002386772e230…
http_response_observation6d ago44ad45bd7339784a…
availability_observation6d agoc99bac4785809774…
hosting_provider_observation6d agoe7292135d1d3f6bd…
tls_certificate_observation6d ago69e531fd7abb835c…
oauth_metadata_observation6d agoe100293e472fd665…
mcp_protocol_observation6d ago4e448e9831e41432…
mcp_capability_observation6d agoac70d1f6bcdabaea…

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

Operate this service?

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

Claim this profile →