CryptoSignals MCP Server
MCP server for real-time crypto volume anomaly detection across 50+ tokens. Detects unusual trading activity, whale movements, and pump signals.
Features
- 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
Tools
| Tool | Description |
|---|---|
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) |
Quick Start
Install
pip install crypto-signals-mcp
Run
uvx crypto-signals-mcp
Or with pip:
fastmcp run server.py
Configure in Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"crypto-signals": {
"command": "uvx",
"args": ["crypto-signals-mcp"]
}
}
}
Example Usage
Ask your AI assistant:
- "Scan all crypto tokens for volume anomalies"
- "Analyze Bitcoin for unusual trading activity"
- "Show me high-confidence crypto alerts"
- "Which tokens have whale movement signals right now?"
How It Works
The server connects to CoinGecko's free API and monitors trading volume across 50+ cryptocurrencies. It calculates volume-to-market-cap ratios to identify statistically unusual trading activity — often an early indicator of price movement, whale accumulation, or pump activity.
Also Available On
- PyPI —
pip install crypto-signals-mcp - Apify Store — Pay-per-scan serverless Actor
- MCPize — Hosted MCP gateway
- Glama.ai — MCP directory
- awesome-mcp-servers — 82K+ stars directory
License
MIT
Metadata
Release files for crypto-signals-mcp 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| crypto_signals_mcp-1.0.2.tar.gz | 4.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| crypto_signals_mcp-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.9 kB
Release files / crypto_signals_mcp-1.0.2.tar.gz
| Download URL | crypto_signals_mcp-1.0.2.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
43b52c5ec721141719769a43fc4f6e3ce45c0284ef9c54fa92ab412aac692c05
|
|
BLAKE2b-256 checksum How to use checksums |
b8854c02ce9581581eebc375123df5d780b10dc0b2b3dc8ac2c2e57d4c1467fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / crypto_signals_mcp-1.0.2-py3-none-any.whl
| Download URL | crypto_signals_mcp-1.0.2-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3b4c9f8263449f046076301c7d2810d413219e9fc3e75cf51f36b89a4f9245fc
|
|
BLAKE2b-256 checksum How to use checksums |
be35c097cc553b4eefd650bd618d9d43fefe74ddfc001462704a880a7914cd50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for crypto-signals-mcp 1.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.