arb-dex-mcp
The server provides live cross-DEX market data across six EVM chains (BSC, Polygon, Arbitrum, Base, Avalanche, Optimism), enabling an AI agent to compare prices, liquidity, and spread opportunities sourced directly from on-chain pool state. You can:
Discover supported chains, venues, and tokens (
get_chains,get_pairs) — list all chains with their native assets, supported tokens, and DEX venues; find which token pairs are priceable on a specific chain and where they trade.Fetch live per-venue prices with cross-DEX spreads (
get_prices) — get the real-time price, reserves, TVL, fee tier, best bid/ask, and gross cross-DEX spread for a pair across all venues on a chain.Rank cross-DEX spread opportunities chain-wide (
get_spreads) — sweep an entire chain to find and rank price dislocations by gross USD at optimal trade size; choose between a free hourly snapshot or a live on-chain sweep (requires RapidAPI key).Access historical price and spread data (
get_history_summary,get_history) — view the measurement archive’s coverage and retrieve per-venue price/liquidity series and gross cross-venue spread over 24h, 7d, or 30d.
All spreads are gross (before gas, MEV, and slippage) and are not profit estimates. Tools using free snapshots work without an API key; paid live routes require a RapidAPI key.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@arb-dex-mcp What's the cross-DEX spread on Arbitrum for USDC/ETH?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
arb-dex-mcp
Live cross-DEX crypto prices for your AI agent — per-venue pool price, pool liquidity and the gross cross-venue spread on 6 EVM chains, read straight from on-chain pool state.
Chains: BSC · Polygon · Arbitrum · Base · Avalanche · Optimism. Venues: PancakeSwap (v2 + v3), Uniswap v3, SushiSwap, QuickSwap, Biswap, ApeSwap, BaseSwap, Trader Joe, Pangolin — every v2-style pool and every v3 fee tier separately, because a $12k 1% pool and a $19M 0.01% pool are not the same quote.
Nothing is modelled, estimated or backfilled. Every payload states its own block number and carries its own scope note, so an agent that quotes a figure also has the caveats attached to it.
Works with no API key against a free hourly public snapshot. Docs · npm
Quickstart
Nothing to clone or build. Your MCP client fetches the package. Requires Node 18+.
Claude Desktop
claude_desktop_config.json — macOS ~/Library/Application Support/Claude/,
Windows %APPDATA%\Claude\:
{
"mcpServers": {
"arb-dex": {
"command": "npx",
"args": ["-y", "arb-dex-mcp"],
"env": {
"RAPIDAPI_KEY": "your-rapidapi-key-here"
}
}
}
}Restart Claude Desktop; the six tools appear under the connectors icon.
Drop the env block entirely to run keyless — the server still starts and the
free-snapshot tools still answer.
Claude Code
claude mcp add arb-dex --env RAPIDAPI_KEY=your-rapidapi-key-here -- npx -y arb-dex-mcpKeyless:
claude mcp add arb-dex -- npx -y arb-dex-mcpThen /mcp to confirm it connected.
Cursor
~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):
{
"mcpServers": {
"arb-dex": {
"command": "npx",
"args": ["-y", "arb-dex-mcp"],
"env": {
"RAPIDAPI_KEY": "your-rapidapi-key-here"
}
}
}
}Cursor → Settings → MCP shows the server and its tools once the file is saved.
Any other MCP client
Same three facts: command npx, args ["-y", "arb-dex-mcp"], transport stdio,
optional env RAPIDAPI_KEY.
Related MCP server: ProfitSpot MCP
Try it
Real prompts, and the real shape that comes back. Payloads below were measured live on 2026-08-15; they are trimmed for width but nothing is invented.
1. "What is WBNB/USDT trading at on every BSC venue right now?"
get_prices reads every pool holding the pair — v2 pairs and each v3 fee tier separately —
at one stated block:
{
"pair": "WBNB/USDT",
"network": "bsc",
"chainId": 56,
"blockNumber": 116151268,
"pricesByVenue": [
{ "venue": "pancake", "surface": "v2", "feeBps": 25, "price": 611.7347, "tvlUsd": 56834814.36 },
{ "venue": "biswap", "surface": "v2", "feeBps": 10, "price": 610.8278, "tvlUsd": 415733.94 },
{ "venue": "apeswap", "surface": "v2", "feeBps": 20, "price": 611.1244, "tvlUsd": 3659.06 },
{ "venue": "pancakeV3:1", "surface": "v3", "feeBps": 1, "price": 610.5684, "tvlUsd": 18596810.32 },
{ "venue": "pancakeV3:5", "surface": "v3", "feeBps": 5, "price": 610.6531, "tvlUsd": 4941099.44 },
{ "venue": "pancakeV3:25", "surface": "v3", "feeBps": 25, "price": 610.6304, "tvlUsd": 52534.35 },
{ "venue": "pancakeV3:100", "surface": "v3", "feeBps": 100, "price": 609.1025, "tvlUsd": 12206.21 }
],
"bestBuy": { "venue": "pancakeV3:100", "price": 609.1025 },
"bestSell": { "venue": "pancake", "price": 611.7347 },
"midSpreadBps": 43.22,
"crossDex": {
"grossSpreadBps": 0,
"grossUsd": 0,
"optimalInput": { "amount": 0, "token": "WBNB", "usd": 0 },
"buyVenue": "-",
"sellVenue": "-"
},
"liquidity": { "venues": 7, "totalTvlUsd": 80856857.67 },
"source": "rpc"
}Read the two spread numbers against each other. The raw mid spread is 43 bps — and the
gross capturable spread is 0. The 609.10 quote lives in a $12k pool; the size that would
actually clear it moves the price past the gap before you get there. A tool that reported only
the 43 bps would be handing an agent a number it cannot trade. This one reports both, and
optimalInput is where the honesty lands.
2. "Show me the cross-DEX spreads on Base — are any actually capturable?"
get_spreads sweeps a whole chain and ranks by gross USD at the optimal size, not by
headline basis points:
{
"network": "base",
"chainId": 8453,
"scannedPairs": 11,
"opportunities": [],
"found": 0,
"filters": { "minSpreadBps": 10, "minVenueTvlUsd": 1000, "minGrossUsd": 0.01, "limit": 5 },
"ranking": "gross USD at the optimal trade size, NOT raw spread — a large spread with a tiny optimal size is not an opportunity",
"scope": "GROSS cross-venue spread from live pool state, BEFORE gas, MEV and any slippage beyond the optimal size. Not a profit estimate and not trade advice. Venues below the liquidity floor are excluded because a spread against a dust pool is an artefact, not an opportunity.",
"elapsedMs": 2847
}found: 0 is a real answer and it is the common one. Eleven pairs scanned, nothing cleared
the floor. Venues under $1,000 TVL are dropped outright. When rows do come back, each carries
capturable, warning and shallowestSideTvlUsd so a big basis-point number cannot mislead on
its own. This tool will tell your agent there is nothing there — which is the whole point of
asking it.
3. "How much history does arb-dex actually have, and for which chains?"
get_history_summary sizes the archive before you query it:
{
"rows": 133,
"rowsWithPairDetail": 103,
"rowsByEra": { "digest-totals-only": 30, "top-list-pairs": 5, "full-sweep": 98 },
"pairsTracked": 107,
"firstAt": "2026-08-10T17:35:09.355Z",
"lastAt": "2026-08-15T20:54:34.417Z",
"spanHours": 123.32,
"chainsSeen": ["arbitrum", "avalanche", "base", "bsc", "optimism", "polygon"],
"pairs": [
{ "chain": "polygon", "pair": "WBTC/USDC", "observations": 103, "qualifiedObservations": 39 },
{ "chain": "bsc", "pair": "BTCB/USDT", "observations": 99, "qualifiedObservations": 15 },
{ "chain": "arbitrum", "pair": "ARB/USDC", "observations": 98, "qualifiedObservations": 0 }
]
}Coverage is only what was measured. A gap stays a gap — rowsByEra says how much detail each
era of rows carries, and ARB/USDC having 98 observations but 0 qualified is the archive
telling you that pair has never once cleared the spread floor.
Tools
Tool | What it answers | Access |
| Which chains are covered, their chain IDs, tokens and DEX venues | Any key · keyless returns the chain list only, and says so |
| What is priceable on one chain: token universe, venues, pair syntax | Any key · keyless returns the measured subset, labelled as such |
| One pair's price at every venue holding a pool for it, plus reserves, TVL, fee tier and the cross-DEX spread | Any key |
| A whole chain's cross-venue dislocations, ranked by gross USD at the optimal size | Any key for |
| What the measurement archive covers: rows, pairs tracked, chains seen, span, retention | Any key (free tier included) |
| One pair's per-venue price/liquidity series and gross cross-venue spread over 24h / 7d / 30d | PRO plan — see Plans |
The two history tools read the service's own measurement archive, so they answer the question
the live tools cannot: whether a dislocation persisted or was a single sample. Sampling is
roughly hourly, and gaps are never interpolated or backfilled. Call get_history_summary first
to see what span exists before asking for a window.
What it will not do
Spreads are gross — before gas, MEV and slippage beyond the optimal size. Not a profit estimate and not trade advice.
It never fabricates a row. Without a key,
get_chains,get_pairsandget_spreadsanswer from the free public surface and each carries alimitationfield naming exactly what a key would add.get_prices,get_history_summaryandget_historyreturn an explicit key-required error with the signup link rather than a thinner answer dressed up as a full one.It does not execute trades, hold funds, or touch a wallet. It is read-only market data.
This package ships no credentials of any kind. The key is yours and stays in your config.
Get a key
The paid tools call the API through RapidAPI using your own key.
Subscribe — there is a free tier: https://rapidapi.com/donnydev/api/multi-chain-dex-prices-liquidity
Copy your
X-RapidAPI-Keyfrom the RapidAPI dashboard.Put it in
RAPIDAPI_KEYin the config above — never in code, and never in a commit.
Plans
Five of the six tools work on the free tier. Only the per-pair history series is gated:
Plan | Adds |
BASIC ($0) | Live quotes on every chain, plus |
PRO ($15/mo) |
|
ULTRA ($49/mo) | No window limit and no history meter, plus depth/slippage and spread alerts |
MEGA ($149/mo) | Bulk paging over the complete archive for your own store |
Calling get_history below PRO returns an explicit tier_required error naming the plan and
the upgrade URL — it does not fail silently or return an empty series.
Configuration
Env var | Default | Purpose |
| — | Your RapidAPI key. Required for the paid tools. |
|
| Request timeout. A live full-chain sweep is a real on-chain read and can take ~30s. |
| production origin | Override the free-surface host. |
|
| Override the RapidAPI host. |
Set these in your MCP client's env block (see the configs above). .env.example ships in the
package and documents the same variables for local runs from a clone.
Test
The test suite is not in the npm tarball — run it from a clone:
git clone https://github.com/donnywin85/arb-dex-mcp.git
cd arb-dex-mcp && npm install
npm run selftest # keyless: exercises the free fallbacks
RAPIDAPI_KEY=... npm run selftest # keyed: exercises the paid routesThe test spawns the server over stdio and calls every tool against the real production API — nothing is mocked. It asserts on live values (block number, per-venue prices, scanned-pair counts), so a run that passes is evidence the data path works end to end.
Links
Official MCP Registry:
io.github.donnywin85/arb-dex-mcpTensorBlock MCP Index: https://www.tensorblock.co/mcp/servers/github-donnywin85-arb-dex-mcp-7dd9a70c
The API behind it: https://rapidapi.com/donnydev/api/multi-chain-dex-prices-liquidity
License
MIT — see LICENSE.
Available Tools
4 toolsget_chainsList supported chains, their tokens and DEX venuesA
List every blockchain this API covers, with its chain ID, native asset, default trading pair, the token tickers it prices, and the DEX venues it reads (both Uniswap-v2-style pools and Uniswap-v3-style concentrated-liquidity pools). Call this first to discover valid chain values for the other tools. With a RapidAPI key you get the full per-chain token and venue lists; without one it falls back to the free public snapshot, which names the chains but not their token universes, and says so in the response. Paid route: needs your own RapidAPI key in RAPIDAPI_KEY (free tier available at https://rapidapi.com/donnydev/api/multi-chain-dex-prices-liquidity).
Inputs: no named parameters.
get_pairsWhat can be priced on one chainA
Show what is queryable on a single chain: the token tickers the API prices, the DEX venues it reads, and the chain default pair. A pair for get_prices is written as TOKEN_A/TOKEN_B from these tickers (first symbol is the base, second is the quote) — any ERC-20 contract address on the chain also works in place of a ticker. This returns the token universe, not a fixed enumerated pair list: the API prices whatever pair of these you ask for that has live pool liquidity, and returns 404 when no pool exists. Without a RapidAPI key it falls back to the free snapshot and returns only the pairs actually measured in the latest scan of that chain, labelled as such. Paid route: needs your own RapidAPI key in RAPIDAPI_KEY (free tier available at https://rapidapi.com/donnydev/api/multi-chain-dex-prices-liquidity).
Inputs: chain (required).
get_pricesPer-venue live pool prices for one pairA
Live price of one trading pair at EVERY DEX venue on a chain that holds a pool for it, read directly from pool state at a stated block number. Returns per-venue price (quote token per 1 base token), pool reserves, pool TVL in USD and the venue fee tier; plus the best bid/ask venues, the raw mid spread in basis points, aggregate liquidity, and the cross-DEX gross spread with its optimal trade size. Use this when you need the actual number a swap would price against on a specific venue, or to compare one pair across venues. For ranking opportunities across a whole chain, use get_spreads instead. Spreads are GROSS — before gas, MEV and slippage beyond the optimal size — and are not a profit estimate or trade advice. Paid route: needs your own RapidAPI key in RAPIDAPI_KEY (free tier available at https://rapidapi.com/donnydev/api/multi-chain-dex-prices-liquidity).
Inputs: pair (required), chain (required), fee.
get_spreadsRank cross-DEX spread opportunities on a chainA
Sweep a whole chain and rank its cross-venue price dislocations, each with the buy venue, sell venue, spread in basis points, the optimal trade size, and the gross USD that size would capture. Ranking is by GROSS USD AT THE OPTIMAL SIZE, not by headline basis points — a 160bps spread against a $1,470 pool is worth about a cent, and the payload says so per row (capturable, warning, shallowestSideTvlUsd). Venues below the liquidity floor are excluded because a spread against a dust pool is an artefact, not an opportunity. Numbers are GROSS: before gas, MEV and any slippage beyond the optimal size. Not a profit estimate and not trade advice. With a RapidAPI key and live=true this runs a fresh on-chain sweep (slow, ~30s, most current). Otherwise it serves the free hourly public snapshot, which is keyless and fast — the response always states which, and when it was generated. Paid route: needs your own RapidAPI key in RAPIDAPI_KEY (free tier available at https://rapidapi.com/donnydev/api/multi-chain-dex-prices-liquidity).
Inputs: chain (required), live, limit, minSpreadBps.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a distinct purpose: get_chains discovers chains, get_pairs reveals a chain's token/venue universe, get_prices returns per-venue prices for one pair, and get_spreads ranks cross-venue opportunities chain-wide. Descriptions explicitly reference when to use each tool, eliminating boundary ambiguity.
All tools follow the exact `get_<plural_noun>` pattern in snake_case (get_chains, get_pairs, get_prices, get_spreads). The naming is perfectly uniform and predictable.
Four tools are well-scoped for the server's purpose: chain discovery, pair/token discovery, per-pair pricing, and spread scanning. Each tool earns its place without bloat or excessive granularity.
The toolset covers the full workflow from discovering chains and tokens to querying live prices and scanning for arbitrage opportunities across all venues. No obvious missing operation for the stated domain.
Related MCP Connectors
Evidence-based market data for AI agents deploying capital in DeFi. Empirical, not advertised.
ChainRay provides multi-chain blockchain data and intelligence for AI agents through 79 MCP tools across 57 supported networks, covering gas, chain data, wallets, DeFi, market, security, monitoring, and verifiable proofs. MCP access is available at https://mcp.chainray.online/mcp; paid HTTP capabilities settle via x402 on Base.
Agent MCP for DeFi: cross-chain LINQ fan-out, AMM quotes/swaps, bridge, AI. Solana+EVM. Free+x402.
Crypto market & research MCP for AI agents: prices, derivatives, options, on-chain, sentiment, news.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceReal-time DeFi data for AI agents. Provides yields, TVL, prices, DEX volumes, fees, and contract data via 8 MCP endpoints, powered by DeFiLlama.-
- AlicenseAqualityCmaintenanceCross-chain DeFi intelligence MCP server for AI agents. 7 tools for yield discovery, pool analysis, profit simulation, risk scoring, whale tracking, impermanent loss calculation, and DeFi overview across 86 chains and 6,500+ liquidity pools.71AGPL 3.0

Monorail MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI agents to fetch real-time quotes, token information, and trade transaction data from Monorail's aggregation of 11 exchanges and 7000+ tokens.2MIT- AlicenseAqualityDmaintenanceAn MCP server that gives Claude, Cursor, and any MCP-compatible agent live on-chain market data from DexScreener — search pairs, inspect tokens and pools, and pull trending/boosted tokens across every chain.6109 npmMIT