gleaming-cassata-d41682.netlify.app

This server isn't on gate's handpicked list. That's not necessarily bad, but there's no third-party signal about it — review its tools carefully.

The tool accepts any HTTPS URL and instructs the agent/service to fetch and cross-check 'live 402 payment terms' from that target. Only an https:// prefix is enforced, with no restriction against internal/private hostnames or unusual ports. If used by a backend service without further validation, this could be leveraged to probe internal network endpoints or non-x402 services via SSRF. Not inherently malicious given its stated purpose, but the input surface is broader than needed.

The description states that 'wallet-capable MCP clients ... auto-construct the EIP-3009 signature' based on this audit's output, implying the agent may proceed to sign and settle a payment without an explicit human-in-the-loop confirmation step. While the tool itself doesn't move funds, its stated role is to justify autonomous fund-transfer authorization, which is a sensitive action that ideally should require explicit user confirmation before signing.

This and the other paid x402 tools (lion_trend_intent_signal_csv, lion_base_dex_signals_json, lion_adaptive_data_query) are designed to be called repeatedly by an agent, each triggering a small USDC payment (0.005–0.05 USDC) via x402. Individually trivial, but an agent could invoke these tools many times across a session without per-call user awareness, resulting in cumulative unauthorized spend. Recommend the agent surface each payment request to the user before settlement rather than treating it as routine tool output.