Cryptoscholar MCP Server

Ask Claude "Is SOL set up for a swing trade?" and it fetches live data from Binance, runs a full indicator suite, scores it, and delivers a grounded bull/bear debate — all in one response. Exposed over MCP by the cryptoscholar mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

• watchlist_add — Add symbols to a named list (creates the list if needed)
• watchlist_remove — Remove symbols; also clears their alerts
• watchlist_show — Show all symbols + configured alerts for a list
• watchlist_lists — List all named watchlists with symbol counts
• watchlist_scan — Run a full TSS analysis on every coin in the list — parallel digest view
• alert_set — Set a tss_above, tss_below, or regime_change alert on any symbol
• alert_check — Fetch live TA for all alerted symbols, report which alerts fired, update baseline
• analyze_coin — Full technical analysis snapshot for any coin. Fetches 300 days of real OHLCV candles from Binance (with CoinGecko fallback) and computes:
• rank_coins — Pass a list of symbols and get them back ranked by TSS. Runs in parallel (up to 8 workers) for fast results on large lists. Each result includes TSS
• top_coins — No symbol list needed. Fetches the top 50 coins by market cap from CoinGecko and returns them ranked by TSS. Smart filtering automatically removes: -
• correlate_coins — Compute pairwise Pearson correlation of 30-day daily returns across 2–20 coins. Returns the full correlation matrix, high-correlation clusters
• market_context — Macro market signals to frame individual coin analysis. Uses CoinGecko global data, DefiLlama stablecoin supply, and Alternative.me Fear & Greed

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need one environment variable: ANTHROPIC_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cryptoscholar's toolset — watchlist_add, watchlist_remove, watchlist_show and 11 more — is a fair guide to whether it matches your workflow. It is maintained by cryptographer11; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• 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.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Cryptoscholar.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cryptoscholar mcp server does with a few real requests.