Shumi AI
Shumi AI is a read-only crypto trade-intelligence MCP server: typed tools for prices, trends, funding, sentiment, regime and signals, plus free-form Q&A.
Coins & prices —
lookup_coin,resolve_coin(fuzzy),get_prices(bulk, with 4h/24h/7d baselines),scan_coins(filter by trend/category/mcap/exchange),get_coin_historical.Risk & verdicts —
get_coin_risk(price, funding APR, carry if long/short, trend, sentiment, BTC correlation),get_signal(trend+funding+sentiment+regime),get_signal_quality(Sharpe, win rate, reliability).Funding —
get_funding_momentum(market-wide or per symbol) andget_funding_alerts(trigger events).Market state —
get_market_health(UP/HODL/DOWN breadth, movers),get_global_market(BTC dominance, cap, volume),get_regime(active/signals/confidence, or per-symbol history).Trend scanning —
scan_trends(fresh, stale, aligned, extreme, historical; 1d/1w).Sentiment & narratives —
get_coin_sentiment,get_market_sentiment(market/narratives/categories/slopes/health),list_narratives,get_narrative,list_categories,get_category.Strategy ideas —
get_pair_suggestions(pair trades, delta-neutral funding arb, backtest history, per-pair state).Free-form —
ask_shumi(natural-language, auto-classified answers) andsearch_web.Token control — list tools accept
topandfieldsto trim output.Constraints — all tools read-only (
readOnlyHint), no task execution, auth viaSHUMI_TOKEN, tier gating server-side. The README also advertises RWA, unlock, holder, wallet, basket and transcript tools that are not present in the supplied schema.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
@shumi-ai/mcp
Shumi crypto trade-intelligence as an MCP server — the same
market intelligence the shumi CLI provides, for any MCP
client (Claude Desktop, Claude Code, Cursor, agents).
It's a thin wrapper over Shumi's data API: prices, trends, funding rates, sentiment, narratives, market regime, synthesized signals, pair / delta-neutral ideas, real-world assets, holder and wallet tracking, and transcript highlights. All tools are read-only.
Quick start
You need a Shumi API key (shumi_sk_…). Create one at https://shumi.ai.
Claude Desktop / Claude Code
Add to your MCP config (claude_desktop_config.json, or claude mcp add for Claude Code):
{
"mcpServers": {
"shumi": {
"command": "npx",
"args": ["-y", "@shumi-ai/mcp"],
"env": {
"SHUMI_TOKEN": "shumi_sk_your_key_here"
}
}
}
}Restart the client. The shumi tools (e.g. get_coin_risk, get_market_health, ask_shumi)
appear automatically.
Cursor
~/.cursor/mcp.json uses the same command / args / env shape as above.
Plugin directories
This repo also ships plugin.json and mcp.json at its root, so it installs as an
Agent Plugin from Cursor's directory and any other client on that
standard.
Set SHUMI_TOKEN in your environment before starting the client when you install this way. The
Agent Plugins schema takes literal environment values only — it has no placeholder for a secret —
so the manifest deliberately omits env rather than shipping a ${SHUMI_TOKEN} string that would
be passed through verbatim and fail as an invalid key.
Related MCP server: All-in-One Crypto Trading MCP Server
Tools
Typed (deterministic): get_coin_risk, lookup_coin, resolve_coin, get_coin_sentiment,
get_coin_historical, get_market_health, get_market_crossing, get_global_market,
get_prices, scan_trends, scan_coins, get_market_sentiment, list_narratives,
get_narrative, list_categories, get_category, get_funding_momentum, get_funding_alerts,
get_regime, get_signal, get_signal_quality, get_pair_suggestions, list_rwa_assets,
get_rwa_asset, get_unlocks, get_unlock_calendar, get_holders, get_wallets, get_futures_signals, get_basket,
get_transcripts.
Real-world assets (list_rwa_assets, get_rwa_asset) cover stocks, ETFs, commodities,
indices and FX trading as perps on Hyperliquid builder DEXes. They are not crypto tokens — the
coin tools will not find them.
Free-form: ask_shumi (natural-language questions — Shumi classifies, fetches, and synthesizes)
and search_web.
List-returning tools accept top (keep first N items) and fields (comma-separated keys to keep)
to save tokens.
Resources: shumi://capabilities (the data surface) and shumi://billing/tier (your current
entitlement).
Configuration
Env var | Default | Purpose |
| — | API key ( |
| production coinrotator-ai endpoint | Override the API base URL. |
| — | Wallet address to include in NLP query context. |
Gating (free / access / pro tiers and pay-per-call) is enforced server-side, exactly as for the CLI — out-of-quota responses come back as a structured error with an actionable hint.
Remote (HTTP)
For a hosted, multi-user deployment:
PORT=8787 SHUMI_MCP_ALLOWED_ORIGINS=https://yourapp.com npm run start:httpEach request authenticates with its own key header; that token is forwarded to the upstream API per
request. Endpoint: POST /mcp, health: GET /health.
Connecting from Claude (static_headers)
Claude supports a fixed credential entered as a request header, so no OAuth server is needed. In Add custom connector → request headers, an organisation administrator enters:
field | value |
URL |
|
Header name |
|
Header value |
|
x-api-key: shumi_sk_… works too, and so does an Authorization value with the Bearer prefix
omitted — an admin types this once by hand, and a mistyped pair fails closed with no error they can
see, so all three shapes are accepted. x-api-key wins if both are present, on the grounds that an
admin who set it meant it.
Do not put the key in the URL. The MCP authorization spec prohibits access tokens in the URI
query string and Anthropic documents a credential in a URL as a security vulnerability — URLs land in
server logs, proxies and browser history. The ?shumiToken= / ?config= query forms exist only
because Smithery injects session config that way.
One thing to know before buying for a team: a static_headers credential is shared by the
organisation, not per user. Everyone connecting through that connector shares one Shumi account,
one free-tier allowance and one quota. Per-user metering needs OAuth — see docs/oauth-plan.md.
An unauthenticated call is answered with 200 and an in-band AUTH_REQUIRED error, not 401.
That is deliberate: Claude treats a 401 as the start of an OAuth flow, and a server with no
authorization server behind it would send the client into a handshake that cannot complete. The
401 path exists but is gated behind SHUMI_MCP_AUTH_SERVER, so it lights up only once there is an
authorization server to point at.
The server is stateless. One endpoint serves both protocol revisions:
2026-07-28— noinitialize, noMcp-Session-Id. A request carries its own routing in headers (Mcp-Method, plusMcp-Nameontools/call) and its protocol envelope inparams._meta, so an intermediary can route and meter a call without parsing the body.2025-11-25and earlier — still served. Old clients keep theirinitializehandshake, but each exchange is answered by its own instance rather than a session.
Because nothing outlives a request, GET and DELETE (the 2025 session operations) return 405,
and the session tunables that used to live here — SHUMI_MCP_SESSION_TTL_MS, SHUMI_MCP_MAX_SESSIONS,
SHUMI_MCP_SESSION_SWEEP_MS — are gone. They are safe to delete from any deployment; unset they do
nothing. The idle-session reaper they configured existed to stop liveness probes from growing the
heap, which cannot happen when no session is kept.
Develop
npm install
npm test # unit tests (no network)
npm run inspect # open the MCP Inspector against the stdio server
SHUMI_TOKEN=… npm start # run the stdio serverDeliberately not exposed
Two CLI routes have no MCP tool, both on purpose:
walkforward— the route exists, but two of its three actions have nothing behind them while Engine B is paused: positions is empty and outcomes holds a single row from 2026-05-28. Shipping it would hand a caller an empty array with no reason attached. It goes in when the engine resumes.watch— server-sent events, which do not fit MCP tool semantics.
Everything else in the CLI's typed surface has a tool.
Available Tools
23 toolsask_shumiAsk Shumi (free-form)ARead-onlyInspect
Ask Shumi any crypto-market question in natural language. Shumi classifies the query, fetches the relevant data, and returns a synthesized answer. Use this when no specific typed tool fits, or for multi-part / comparative questions.
Inputs: query (required), archetype.
get_categoryCategory detailARead-onlyInspect
Detail for one category. view=info (trend breakdown), coins (member coins), sentiment.
Inputs: name (required), top, view, fields. Returns: data, meta, error
get_coin_historicalCoin historical metadataARead-onlyInspect
Historical metadata for a coin (holder cohorts, sentiment and funding history).
Inputs: symbol (required). Returns: data, meta, error
get_coin_riskCoin risk contextARead-onlyInspect
Bundled risk context for one or more coins: price, funding APR, deterministic funding_paying_side, funding_receiving_side, carry_if_long and carry_if_short fields, daily/weekly trend, sentiment stance, and BTC correlation. Funding applies to perpetual positions only; spot positions neither pay nor receive it. Relay the carry fields exactly rather than inferring direction from crowding. The best single tool for "should I be worried about X".
Inputs: symbols (required). Returns: data, meta, error
get_coin_sentimentCoin sentimentARead-onlyInspect
On-chain/social sentiment aggregates for a single coin.
Inputs: symbol (required). Returns: data, meta, error
get_funding_alertsFunding alertsARead-onlyInspect
Discrete funding-rate alert events (asset, trigger zone, funding at trigger, fired-at time).
Inputs: top, fields. Returns: data, meta, error
get_funding_momentumFunding momentumARead-onlyInspect
Perpetual funding-rate positioning context, market-wide or for one symbol. APR is already in percent units (1.7 = 1.7%). Positive funding means longs pay and shorts receive; negative funding means shorts pay and longs receive. Funding is context only, not a standalone directional, timing, or entry signal.
Inputs: symbol. Returns: data, meta, error
get_global_marketGlobal market aggregatesARead-onlyInspect
Global market aggregates: BTC dominance, total market cap, total volume.
Inputs: no named parameters. Returns: data, meta, error
get_market_healthMarket healthARead-onlyInspect
Overall market health: the UP/HODL/DOWN trend distribution and extreme movers. Set context for the full bundle.
Inputs: context. Returns: data, meta, error
get_market_sentimentMarket sentimentARead-onlyInspect
Aggregate market sentiment. view=market/latest/summary (overall), narratives, categories, slopes/entity-slopes (what is trending), health (pipeline status).
Inputs: top, view, fields. Returns: data, meta, error
get_narrativeNarrative sentimentARead-onlyInspect
Sentiment and momentum for a single named narrative.
Inputs: name (required). Returns: data, meta, error
get_pair_suggestionsPair / delta-neutral suggestionsARead-onlyInspect
Pair-trading and delta-neutral funding-arbitrage intelligence. mode=suggestions (pair ideas), delta-neutral (funding arb), history (backtest), signal (state for a specific pair — needs token_a & token_b).
Inputs: top, mode, limit, fields, +5 more. Returns: data, meta, error
get_pricesBulk live pricesARead-onlyInspect
Bulk live prices, optionally with 4h/24h/7d baseline overlays. Omit symbols for the full tracked set.
Inputs: top, fields, symbols, baselines. Returns: data, meta, error
get_regimeMarket regimeARead-onlyInspect
Market regime signals. view=active (current positions), signals (all), confidence (scores). Provide symbol to get that symbol's regime history instead.
Inputs: view, symbol. Returns: data, meta, error
get_signalSynthesized signalARead-onlyInspect
Synthesized verdict for a coin, combining trend, funding, sentiment and regime.
Inputs: symbol (required). Returns: data, meta, error
get_signal_qualitySignal qualityBRead-onlyInspect
Signal validation envelope for an asset: Sharpe ratio, win rate, sample size, reliability tier.
Inputs: asset (required), signal_type. Returns: data, meta, error
list_categoriesList categoriesARead-onlyInspect
List all tracked crypto categories (DeFi, Layer 2, memes, …).
Inputs: top, fields. Returns: data, meta, error
list_narrativesList narrativesARead-onlyInspect
List the currently active market narratives (e.g. "AI coins", "DeFi summer").
Inputs: top, fields. Returns: data, meta, error
lookup_coinLook up a coinARead-onlyInspect
Look up a single coin and its core metrics (price, trend, metadata) by symbol, name, CoinGecko/internal id, or on-chain contract address.
Inputs: identifier (required), by, chain. Returns: data, meta, error
resolve_coinResolve a coin (fuzzy)ARead-onlyInspect
Fuzzily resolve a symbol, name, or contract to canonical coin candidates. Use this first when the user input is ambiguous, before calling other tools.
Inputs: query (required), limit. Returns: data, meta, error
scan_coinsScan / filter coinsARead-onlyInspect
Filter the tracked universe by trend direction, category, market-cap band, and exchange.
Inputs: top, limit, trend, fields, +5 more. Returns: data, meta, error
scan_trendsScan trendsARead-onlyInspect
Trend scanner. state=fresh (newly started), stale (longest running), aligned (multi-timeframe agreement), extreme (biggest moves), historical.
Inputs: top, limit, state, fields, +1 more. Returns: data, meta, error
search_webSearch the webARead-onlyInspect
Search the web for crypto information, or get a direct answer. Backed by Shumi's web-search tool.
Inputs: query (required), answer.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 23 tools
Each tool targets a distinct aspect of crypto market analysis, from global metrics to coin-specific risk, sentiment, funding, signals, and natural language queries. Detailed descriptions prevent ambiguity.
All tools follow a consistent verb_noun pattern with lowercase underscores (e.g., get_global_market, scan_trends, list_narratives). No mixing of styles.
23 tools cover the broad domain of crypto market data without being overwhelming. Each tool serves a clear purpose and the count is well-scoped for the server's functionality.
The tool set covers all major areas: market aggregates, individual coins, trends, sentiment, categories, narratives, funding, signals, pairs, and a general query tool. No obvious gaps for the intended use.
Maintenance
Related MCP Connectors
Crypto fundamentals, sentiment, whale tracking and influencer call accuracy for traders and agents.
Crypto market intelligence: social sentiment, on-chain, trending narratives & analyst insights.
Crypto market intelligence for Projects, Topics, Intel, Reports, and Clusters.
Source-linked crypto research tools, market observations and user-owned agent tasks.
Related MCP Servers
- AlicenseAqualityBmaintenanceAI-native quantitative trading signal engine for crypto and TradFi perpetuals. Multi-factor composite BUY/SELL/HOLD signals, cross-venue funding rate arbitrage scanning, and market regime detection powered by Hyperliquid data.11882 npm10MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered cryptocurrency trading and analytics across multiple exchanges and blockchains, with integrated Telegram bot and live trading capabilities.3MIT
- AlicenseAqualityDmaintenanceProvides real-time Web3 research digest with macro news, KOL sentiment, market data, and personalized on-chain wallet analysis through four AI tools.4MIT
- AlicenseNot gradedqualityDmaintenanceDelivers real-time crypto market microstructure, derivatives, order flow CVD/OI regime classification, fear & greed sentiment, and whale tracking context, enabling traders to assess market regimes and complement charting tools.54 npmMIT