dex-metrics-mcp
Related Servers
Alternatives to dex-metrics-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that tracks and analyzes DEX liquidity pools to power intelligent DeFi agents and automated strategies.12MIT
- AlicenseAqualityDmaintenanceAn MCP server that provides AI agents with real-time access to DEX liquidity pool data, enabling smarter trading, analytics, and automated strategies.101MIT
- AlicenseAqualityDmaintenanceAn MCP server that tracks daily activity and graduate metrics across multiple Solana launchpads.41MIT
- AlicenseAqualityDmaintenanceAn MCP server that analyzes cross-chain activity on the Wormhole protocol, providing insights into transaction volumes, top assets, source-destination chain pairs, and key performance indicators (KPIs).7MIT
- AlicenseAqualityDmaintenanceAn MCP server that analyzes wallets’ trading activity and profitability on Pump.fun and PumpSwap.41MIT
- AlicenseAqualityFmaintenanceAn MCP server that provides real-time data and insights from the Hyperliquid perp DEX for use in bots, dashboards, and analytics.1729MIT
TDQS
Scored across 10 tools
The tools have overlapping purposes with multiple variations of trading volume retrieval by different dimensions (DEX, chain, frontend, etc.), which could cause confusion. However, the descriptions clearly specify the breakdown dimension and timeframe, helping to distinguish them. There is some ambiguity between similar tools like get_weekly_trading_volume_by_dex and get_weekly_solana_trading_volume_by_dex, but the descriptions clarify the scope.
All tools follow a consistent snake_case naming pattern with a clear get_<timeframe>_trading_volume_by_<dimension> structure. The naming is predictable and uniform across all 10 tools, making it easy to understand what each tool does based on its name alone.
With 10 tools, the count is reasonable for a metrics server focused on trading volume data. However, there is some redundancy with multiple tools covering similar dimensions (e.g., multiple DEX-focused tools with different timeframes), which makes the set feel slightly heavy but still within appropriate bounds for the domain.
The server covers various dimensions (DEX, chain, frontend, aggregator, Telegram bot) and timeframes (daily, weekly, monthly, latest, YoY), but there are notable gaps. For example, there is no tool for creating, updating, or deleting data, and coverage is inconsistent across dimensions (e.g., no monthly data for chains or frontends). The surface is focused on retrieval only, which limits completeness for a full metrics management system.