atx/registry

mcp.tronsave.io/testnet

https://mcp.tronsave.io/testnet/mcp

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

Why this score

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

Findings (2)

mediumCapabilities are listable without authentication, including 18 whose names suggest state change (tronsave_cancel_order, tronsave_create_order, tronsave_delete_auto_buy_setting, …) — 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 (8)

TypeObservedSHA-256
dns_resolution_observation2d ago49095ea8b1731b5e…
http_response_observation2d ago52943dd8c9afe85e…
availability_observation2d ago05069686c2daa2d1…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d agobf08250d9a3dd19e…
oauth_metadata_observation2d agobf8197d08debde97…
mcp_protocol_observation2d agof8f1c111d2192312…
mcp_capability_observation2d agoe05acfeb5e429c7c…

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

Operate this service?

Prove control of mcp.tronsave.io/testnet to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →