atx/registry

api.decker-ai.com/api/v1

https://api.decker-ai.com/api/v1/mcp

50
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 50m ago

Why this score

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

Findings (3)

mediumCapabilities are listable without authentication, including 4 whose names suggest state change (decker.close_position, decker.place_order, decker.set_skill_overlay, …) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowInput schema changed without a name change: decker.get_market_state
mcp.tool_schema_changed @ 1.0.0
infoCapability set changed: +1 / -0
mcp.capability_set_changed @ 1.0.0

Evidence (9)

TypeObservedSHA-256
dns_resolution_observation50m agodc008a813ebcc78d…
http_response_observation50m ago95fbd95a73d39bd4…
availability_observation50m ago321f69b029f7378c…
hosting_provider_observation50m agof6ca63562d443d49…
tls_certificate_observation50m agod24b61125667fa99…
oauth_metadata_observation50m ago439aab6e246dea9e…
mcp_protocol_observation50m agoa713f445b662f0d8…
mcp_capability_observation50m ago8368826875ff421a…
mcp_capability_drift50m agod584d5944f543d53…

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

Operate this service?

Prove control of api.decker-ai.com/api/v1 to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →