atx/registry

api.tickerbot.io

https://api.tickerbot.io/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 13 whose names suggest state change (tickerbot_create_custom_signal, tickerbot_create_universe, tickerbot_create_webhook, …) — 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 agof9012924e7c5afe2…
http_response_observation2d agoed598b9782936b34…
availability_observation2d ago126d566fc83170f7…
tls_certificate_observation2d ago831f8786d4a55dbf…
oauth_metadata_observation2d agof4f65835b697392d…
mcp_protocol_observation2d ago0367df67b49eacdc…
mcp_capability_observation2d ago0504595b8c794aaa…

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

Operate this service?

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

Claim this profile →