No user-submitted related servers found.
Scored across 26 tools
Tools mostly target distinct resource+action pairs, and descriptions actively guide selection (e.g. find_cluster explicitly says to use compare_wallets when you already have candidates; get_transfers is 'prefer over walking signatures'). However the transaction cluster (get_transactions, get_transaction_history, get_transaction_raw, investigate_transaction) and the transfer/swap family (get_transfers, get_swaps, get_transaction_history) overlap enough that an agent could still hesitate.
Predominantly consistent snake_case with a verb_noun or get_noun pattern (get_balances, get_swaps, analyze_wallet, trace_funds, find_cluster, case_update/read/export). Minor deviations: a few noun-only names (chain_status, server_metrics, wallet_pnl, solana_rpc) break the verb-first convention, but overall the pattern is predictable.
At 26 tools this is on the heavy side for a single server, which typically signals bloat. Here the domain (Solana on-chain forensics across transactions, tokens, assets, tracing, clustering and cases) is genuinely broad and each tool appears to earn its place, so it lands just shy of ideal rather than excessive.
The surface covers the full investigation lifecycle: orientation (chain_status, get_balances, get_account), transaction parsing at multiple granularities, token/asset inspection, wallet and token risk analysis, fund tracing, clustering, bridging, PnL, and a complete case CRUD (case_update, case_read, case_export). A read-only solana_rpc escape hatch closes the remaining gaps, leaving no obvious dead ends.