Prerequisites
Cryptohopper MCP configured in an MCP client (Claude Code, Claude desktop, Cursor, or similar) — see the setup overview.
An active Cryptohopper subscription. The free Pioneer tier is sufficient.
A delivery channel for the report — Telegram, Discord, email, or a markdown file. Optional but recommended.
Setup steps
Open your MCP client and start a new conversation
Issue the core scan prompt
Use the template below as a starting point:Using the Cryptohopper MCP, pull tickers for the top 50 pairs on Binance by 24h volume.
Identify:
- The 5 biggest gainers (highest positive 24h change %)
- The 5 biggest losers (largest negative 24h change %)
- Any pair with 24h volume more than 3× its typical level
For each pair, include:
- Symbol
- Last price
- 24h change %
- 24h volume
Output format: Present the results as a markdown table with three clearly separated sections.Refine based on the first output
Increase the universe size (top 50 → top 100) if the signal is thin. Switch exchanges if your pairs live elsewhere. Adjust the volume threshold — in calm periods, 2× may be more useful than 3×.
Save the finalised prompt
Store it in a markdown file, Notion page, or wherever you keep reusable prompts.
Automate the run
Schedule the prompt to fire each weekday morning via cron (macOS/Linux), Task Scheduler (Windows), or GitHub Actions (cloud). See how to schedule Cryptohopper MCP workflows.
Wire the output to a delivery channel
Append a delivery instruction to your prompt or script — e.g. "Send the resulting report to my Telegram channel {channel_id}." See how to send MCP reports to Telegram, Discord, or email.
Full prompt template
A complete scheduled prompt suitable for daily use:
Using the Cryptohopper MCP, produce a daily top-movers report for Binance.
1. Pull data
Pull tickers for the top 100 pairs on Binance by 24h volume.
2. Identify the following
- The 5 biggest gainers by 24h change %, excluding any pair with 24h volume under $10m equivalent.
- The 5 biggest losers by 24h change %, using the same volume filter.
- Up to 5 pairs with unusually high volume (24h volume materially above recent typical level).
3. Output format
Present the results as three markdown tables, each with the following columns:
- Symbol
- Last price
- 24h change %
- 24h volume (in quote asset)
4. Summary
At the top, write a one-sentence summary of the day's market tone (e.g. broadly risk-on, mixed, sharp selloff in altcoins).
Note on the volume filter: The $10m threshold removes illiquid micro-caps that often show 100%+ moves on tiny volume — these are almost always noise. Adjust the threshold to match the market segment you actually care about.
Cost profile
This workflow runs comfortably within the Pioneer free tier's 6,000 calls/week.
Action | Call units |
Top 100 ticker sweep | 100 |
Daily run, 5 weekdays | 500 |
Weekly total | 500 |
Scanning multiple exchanges or running more than once per day scales linearly. See rate limits explained.
Troubleshooting
The agent returns pairs you don't care about
Tighten the filter. Add to the prompt: "exclude stablecoin-stablecoin pairs and any pair with 24h volume under $10m equivalent." Or maintain a whitelist: "only consider pairs from this list: BTC, ETH, SOL, …"
The output is inconsistent day to day
The model is making different small judgement calls each run. Make the prompt more explicit — use exact thresholds rather than adjectives ("gainers above +5%" rather than "notable gainers") and require a fixed output format with specified columns and order.
The scheduled run fails silently
Log the output to a file on every run and check it periodically. Add a step that sends a notification on failure, not just on success. See how to schedule Cryptohopper MCP workflows.
RATE_LIMIT_EXCEEDED during the scan
You're pulling too many tickers in too short a window. Add a brief delay between calls, or ask the agent to fetch in smaller batches (top 50 at a time). See rate limits explained.
The report is too long or too short
Adjust the top N and the number of entries per section. Five entries per category is a good default — ten is usually more than you'll read.
You want multi-exchange coverage
Run the scan on each exchange and combine. This multiplies the call cost — 3 exchanges = 3× the ticker calls. The Pioneer 6,000-calls/week budget accommodates a 3-exchange daily scan comfortably.