Whale402
Related Servers
Alternatives to Whale402
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceWhale & Institutional Flow MCP Server — 8 tools for protocol TVL flows, alpha signals, stablecoin supply tracking. Part of ToolOracle (tooloracle.io).-
- AlicenseNot gradedqualityAmaintenanceSolana Whale Tracker & Copy Trading45,991 npm8MIT
- AlicenseNot gradedqualityDmaintenanceProvides predictive crypto market intelligence synthesized from whale positions, developer activity, and behavioral demand signals. Enables convergence scoring, whale divergence detection, and risk radar through MCP tools.171 npmMIT
- AlicenseAqualityCmaintenanceReal-time crypto whale intelligence MCP server with 55 tools across 14 blockchains. Free, no auth required.561MIT
- AlicenseNot gradedqualityAmaintenanceKOL, smart money & whale wallets API on Solana, BNB, Base, ETH: Wallet tracker, LeaderboardMIT

mcp-midasflowofficial
AlicenseNot gradedqualityDmaintenanceMidasFlow Flow API - Cross-exchange order flow, whale detection, liquidations, funding rates, squeeze alerts for AI agents. Native MCP server.MIT
TDQS
Scored across 5 tools
Each tool targets a fairly distinct object: token-holder clusters, billing status, trend radar, token activity, and wallet profiling. There is minor potential overlap between get_smart_money_radar and get_token_whale_activity since both involve whale accumulation, but the descriptions distinguish broad scanning from token-specific analysis.
All names use snake_case and mostly follow a verb_noun pattern with get_, detect_, and profile_. The convention is predictable overall, though the verbs are not perfectly uniform.
Five tools is a well-scoped set for a focused crypto whale analytics server. Each tool appears to cover a necessary capability without excessive surface area.
The surface covers key analytics workflows: wallet profiling, token-level whale activity, smart-money trends, insider cluster detection, and billing/credits. Some adjacent operations such as alerting or broader historical queries are absent, but core usage paths are covered.