Prerequisites
Cryptohopper MCP configured in an MCP client — see the setup overview.
Explorer tier or higher if you want access to more than the three Pioneer exchanges (Binance, Coinbase, Kraken) — see subscription tiers and supported exchanges.
Setup steps
Open your MCP client
Decide on pairs and exchanges
Start with 5–10 pairs from your actual watchlist — 50+ introduces noise. For exchanges, Binance, Coinbase, Kraken, OKX, and Bybit cover most liquid trading.
Issue the core comparison prompt
Most pairs will show gaps of 2–8 basis points — normal microstructure noise. Gaps above 20bp are worth a second look.
Using the Cryptohopper MCP, pull the current ticker for each of these pairs from Binance, Coinbase, Kraken, OKX, and Bybit:
BTC/USDT
ETH/USDT
SOL/USDT
ARB/USDT
OP/USDT
For each pair
- Report the min and max last price across the venues.
- Identify which venue has each.
- Compute the gap in basis points: |max − min| / midpoint × 10000.
Flag any pair where the gap exceeds 20 basis points.
Output format: Present as a markdown table, sorted by gap size descending.Adjust the threshold based on what you see
If every pair flags, tighten to 30–50bp. If nothing ever flags, loosen to 10bp.
Escalate flagged pairs to an orderbook check (optional)
Add to the prompt for any pairs that flag:For any pair that flags above threshold, pull the orderbook from the two outlier venues and report the 0.5% depth on the side that would close the gap.
Then tell me whether the gap is actually executable given that depth.Automate on a schedule
Cross-exchange scans fit naturally into hourly or daily cron jobs. See how to schedule Cryptohopper MCP workflows.
Cost profile
Each scan costs pairs × venues in ticker calls.
Scan | Call units |
5 pairs × 5 venues | 25 |
10 pairs × 5 venues | 50 |
Hourly, 12 runs/day × 5 weekdays (5×5 case) | 3,000/week |
A 5-pair × 3-venue hourly scan fits comfortably within Pioneer's 6,000 calls/week. A 10-pair × 5-venue hourly scan is trivial on Explorer. See rate limits explained.
Troubleshooting
All gaps are under 10bp and nothing ever flags
This is often correct — liquid pairs on major exchanges are kept tight by market makers. Either loosen the threshold, add smaller-cap pairs (which drift more), or accept that your watchlist is well-arbed and gaps are rare events worth specifically waiting for.
EXCHANGE_NOT_SUPPORTED
Your tier does not include one of the requested exchanges. Pioneer is limited to Binance, Coinbase, and Kraken. See supported exchanges for the tier-specific allow list.
Gaps fluctuate wildly run to run
Normal behavior for fast-moving or thin-liquidity pairs. For stable readings, average across multiple runs (5 samples over 5 minutes) before flagging, or stick to liquid pairs where cross-venue gaps stabilize quickly.
The agent reports gaps that disappear when you check manually
By the time you refresh the exchange tab, the gap has closed. This is the main reason arbitrage research is not arbitrage execution. The research value is in understanding which pairs and venues are structurally loose, not in catching individual opportunities.
You want to know if the gap is actually tradable
Use step 5 above to escalate to orderbook depth checks. A gap that shows on top-of-book but has no depth behind it cannot be captured. See how to estimate slippage before placing a trade.
You want alerts on Telegram, Discord, or email instead of chat output
Wrap the scan in a scheduled script and deliver via how to send MCP reports to Telegram, Discord, or email. Common pattern: only send the message if at least one pair flagged — silence otherwise.