atx/registry

api.relaystation.ai

https://api.relaystation.ai/mcp

75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago

Why this score

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

Findings (3)

mediumCapabilities are listable without authentication, including 7 whose names suggest state change (append_to_baton, create_agent_address, create_baton, …) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
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 ago1e19dd08950e33d5…
http_response_observation2d ago7cfdf2dcf88cb28e…
availability_observation2d ago914b719aa6591282…
tls_certificate_observation2d ago21b397ba87524b81…
oauth_metadata_observation2d ago18591ab3fc46fc64…
mcp_protocol_observation2d ago2ebb57bed37d5cf2…
mcp_capability_observation2d ago30af6aee8e5ff266…

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

Operate this service?

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

Claim this profile →