get_latest_trading_volume_by_dexLABSCO SUMMARY
Segmentation is the point, not the raw total.
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.
What it is
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.
What you get
- 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
limitparameter on every tool, defaulting to 1000 rows
Requirements
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 <YOUR_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.
Setup effort
Build from source — git clone https://github.com/kukapay/dex-metrics-mcp.git
USE CASES
Seeing which venues are taking flow right now
Pull the latest 24-hour and 7-day rankings side by side to tell a spike apart from a trend.
Comparing chains rather than exchanges
Read daily volume by blockchain to see where activity is concentrating, independently of which DEX captured it.
Tracking how aggregator share moved over a year
Pull year-over-year monthly volume by aggregator instead of stitching together monthly snapshots.
Measuring the interfaces users actually trade through
Look at volume by frontend and by Telegram bot, which separates the routing layer from the venue that settled the trade.
10 tools
Listed in project docs. Your client may show a different list.
get_latest_trading_volume_by_aggregatorget_daily_trading_volume_by_chainget_daily_trading_volume_by_dexget_weekly_trading_volume_by_dexget_monthly_trading_volume_by_dexget_yoy_monthly_trading_volume_by_aggragatorget_weekly_solana_trading_volume_by_dexget_weekly_trading_volume_by_frontendget_daily_trading_volume_by_telegram_botBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
- Python 3.10
- DUNE_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
Clone the Repository
git clone https://github.com/kukapay/dex-metrics-mcp.git
cd dex-metrics-mcpInstall Dependencies
uv syncInstalling to Claude Desktop
uv run mcp install main.py --name "DEX Metrics"MCP Clients
Claude Desktop
{
"mcpServers": {
"DEX Metrics": {
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_DEX_METRICS_MCP>",
"run",
"main.py"
],
"env": {
"DUNE_API_KEY": "<YOUR_DUNE_API_KEY>"
}
}
}
}