claude mcp add signal-scanner -- npx -y signal-scanner
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
0 ★ · cstamigo-droid/signal-scanner · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository cstamigo-droid/signal-scanner;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Third-party quality signals
signal-scanner — rule-based stock/crypto screener with alerts
Define a **watchlist** and a **ruleset** (plain YAML); the scanner pulls market data, computes indicators, and tells you which symbols match — on the console, in **Telegram**, or from any **MCP host** (Claude Desktop / Claude Code). > Built once, reskinned per client: swap watchlist.txt + rules.yaml, ship. Why it's different - **Keyless by default.** Market data via yfinance — no API key. Works for stocks, ETFs, FX (EURUSD=X) and crypto (BTC-USD). Demo it anywhere. - **No-code rules.** Clients edit rules.yaml (conditions on indicators) — never the code. - **Honest signals.** Indicators are computed from *closed* bars (no look-ahead); a symbol with no data is reported, never faked. - **Delivery that degrades.** Telegram alerts when a bot token is set; otherwise prints to console. The scanner always runs. - **Three surfaces, one engine.** CLI (one-shot or --watch), Telegram push, and an MCP scan tool. Indicators & rules Indicators per symbol: price, pct_change, rsi, sma_fast, sma_slow, sma_cross (golden/death), vol_ratio (vs 20-day avg), pct_from_52w_high, pct_from_52w_low. A rule fires when **all** its conditions are true: Quickstart Telegram (optional) Create a bot with @BotFather, get the token; get your chat id from @userinfobot. Then in .env: As an MCP server (Claude Desktop) Use the full path to your Python (e.g. the one where you ran pip install -r requirements.txt) if python isn't on PATH. Then ask Claude: *"Run my scanner"* or *"Any signals on NVDA and BTC-USD?"* — it calls the scan tool. Configuration All knobs in config.py / .env (see .env.example): RSI period, SMA fast/slow, volume window, lookback, poll interval, data backend, Telegram. A client reskin is usually just watchlist.txt + rules.yaml. Architecture Reuses the mcp-factory contract (Result, formatting, cache) so it composes with the rest of the catalog.