CryptoSignals MCP Server

CryptoSignals MCP server exists for a simple reason — assistants are far more useful when they can act on CryptoSignals directly instead of describing what you should do. Real-time crypto volume anomaly detection across 50+ tokens for whale signals.

What you get

MCP server for real-time crypto volume anomaly detection across 50+ tokens. Detects unusual trading activity, whale movements, and pump signals.

• Volume anomaly detection — — Identifies tokens with unusual volume-to-market-cap ratios
• 50+ tokens monitored — — Continuous scanning across major cryptocurrencies
• Anomaly classification — — Signals rated LOW, MODERATE, HIGH, or CRITICAL
• High-confidence alerts — — Filter for only the most actionable signals
• Live data — — Real-time prices, 24h changes, volume, and market cap

Setting it up

The server ships on PyPI as crypto-signals-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once CryptoSignals is connected, these are the calls the assistant has available:

• scan_all_tokens — Scan all 50+ tokens for volume anomalies
• analyze_token — Detailed analysis for a specific token (BTC, ETH, SOL, etc.)
• get_anomaly_alerts — High-confidence alerts only (vol_mcap ratio above 5.0)

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cryptosignals mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. CryptoSignals's toolset — scan_all_tokens, analyze_token, get_anomaly_alerts — is a fair guide to whether it matches your workflow. It is maintained by MarcinDudekDev; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against CryptoSignals's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.