No user-submitted related servers found.
Scored across 10 tools
Most tools have sharply distinct roles: single-coin vs. scan variants (get_trade_call / scan_trade_calls, get_market_regime / scan_market_regimes) and synthesized vs. lexical knowledge (chat_knowledge / search_knowledge) are explicitly contrasted in their descriptions. The one clear overlap is get_trade_signal, which is openly an alias of get_trade_call — same behavior, two entries — mildly inflating the apparent surface.
The set is dominated by predictable verb_noun naming (get_*, scan_*, search_*, chat_*) with clear resource suffixes. Deviations are minor: pre_trade_check is noun-first and chat_knowledge/search_knowledge drop the verb_noun shape, but every name remains readable and self-descriptive.
Ten tools is squarely in the healthy range for a read-only signal/risk server, and each operation (single-asset, scan, risk check, track record, knowledge) maps to a real workflow. The only count bloat is the get_trade_signal alias, which duplicates get_trade_call rather than adding capability.
The surface covers the core lifecycle: per-asset and whole-market trade calls, regime reads and regime scans, cross-venue funding arbitrage, a pre-trade risk gate, verified performance history, and knowledge/documentation retrieval. Gaps are minor — no watchlist/alerting, no historical candle or backtest tool, and funding data is only exposed via arbitrage scans and composite verdicts rather than a dedicated pair-level lookup.