Total DEX volume is available everywhere; what is harder to get in one place is the same number cut by aggregator, by frontend and by Telegram bot, which is where routing behaviour actually shows up. Output arrives as markdown tables ready to read, and every response comes from Dune, so the numbers are only as fresh as the dashboards behind them.
A read-only window onto Dune Analytics' DEX volume dashboards. Each tool runs one prepared query and returns a markdown table, so a question about where trading volume sits gets answered in the conversation instead of in a browser tab.
- Latest 24-hour and 7-day volume ranked by DEX and by aggregator — `get_latest_trading_volume_by_dex`, `get_latest_trading_volume_by_aggregator`
- Daily volume by blockchain and by DEX — `get_daily_trading_volume_by_chain`, `get_daily_trading_volume_by_dex`
- Weekly and monthly volume by DEX, plus Solana-only weekly volume by DEX — `get_weekly_trading_volume_by_dex`, `get_monthly_trading_volume_by_dex`, `get_weekly_solana_trading_volume_by_dex`
- Year-over-year monthly volume by aggregator — `get_yoy_monthly_trading_volume_by_aggragator`
- 7-day volume by frontend and daily volume by Telegram bot — `get_weekly_trading_volume_by_frontend`, `get_daily_trading_volume_by_telegram_bot`
- A `limit` parameter on every tool, defaulting to 1000 rows
A Dune Analytics API key in `DUNE_API_KEY`. Python 3.10 or higher and `uv`. Install from a clone with `uv sync`, then run `uv --directory /path/to/dex-metrics-mcp run main.py`. The package is `dex-metrics-mcp` (0.1.0). Every tool is a read; nothing writes anywhere.
Build from source — clone the repository and build it, then point your client at the binary