Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ai.shumi/mcp

REMOTE · MCP.SHUMI.AI · 2 COMPONENTS

Crypto market intelligence: prices, funding rates, narratives, regime, and delta-neutral research.

0 this week 87 Trust /100

Last scanned (19 hours ago)

Scores higher than 94% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4066 tokens (~116/item across 35 items; 33 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 33 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 35 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 14 Oct 26 0
    • Schema quality: 3579 → 4066 ▼ functional
    • Server version: 1.2.1 → 1.3.0 functional
    • New tool “get_unlocks” functional
    • New tool “get_unlock_calendar” functional
  • 7 Oct 26 0
    • Schema quality: pass → fail ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Aug 26 0
    • Tool coverage: 94% → 100% ▲ functional
    • Tool “ask_shumi” now declares an output schema ▲ functional
    • Tool “search_web” now declares an output schema ▲ functional
  • 19 Aug 26 0
    • Tool “get_coin_historical” rewrote its description, which is the text the model reads security
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Server version: 0.1.3 → 1.1.0 functional
    • “get_coin_historical” added an optional parameter “amount” cosmetic
    • “get_coin_historical” added an optional parameter “interval” cosmetic
    • Tool “get_coin_historical” changed its title: Coin historical metadata → Coin metrics at a past point in time cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://mcp.shumi.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.shumi.ai CN=WE1,O=Google Trust Services,C=US 10 Oct 2026 8 Jan 2027 ECDSA 256 ECDSA-SHA256 18f128c334f61c190e7ae4e2aa2156fe
SANs: mcp.shumi.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.shumi.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
shumi.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.shumi.ai/mcp Verified 200
http (plaintext) http://mcp.shumi.ai/mcp HTTPS enforced 301 https://mcp.shumi.ai/mcp
MCP tools · 33 exposed · ~3,935 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ask_shumi ~104

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.

NameTypeReqDescription
archetypestring–Specialization path (default "base"; e.g. "perp-dex").
querystringyesThe natural-language question, e.g. "is funding extreme on SOL right now?".
NameTypeReqDescription
answerstring–The synthesized natural-language answer. Absent only when the engine produced no prose.
steps––Raw engine steps. Present only as a fallback when `answer` is absent.

No examples provided.

get_basket ~65

Daily snapshots of the tracked basket — composition and performance over time.

NameTypeReqDescription
fieldsstring–Token-saving: comma-separated top-level fields to keep.
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_category ~99

Detail for one category. view=info (trend breakdown), coins (member coins), sentiment.

NameTypeReqDescription
fieldsstring–Token-saving: comma-separated top-level fields to keep.
namestringyesCategory name, e.g. "Layer 2".
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
viewstring–Which category view to return.
NameTypeReqDescription
data–yesThe tool payload, unwrapped from the CLI envelope.
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_coin_historical ~152

Market cap, volume, open interest, funding rate and price for a coin AS OF a chosen point in the past. Returns a single snapshot, not a series: call it once per point you want to compare (e.g. amount=7 interval=d for a week ago, then again with no offset for now). Use this to answer "how has funding/open interest changed since…".

NameTypeReqDescription
amountinteger–How far back to look, in units of `interval`. Omit for the most recent snapshot.
intervalstring–Unit for `amount`: h (hours) or d (days). Defaults to hours.
symbolstringyesCoin symbol, e.g. ETH.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_coin_risk ~133

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".

NameTypeReqDescription
symbols–yesSymbols as an array ["BTC","ETH","SOL"] or a comma-separated string "BTC,ETH,SOL". 1-15 of them.
NameTypeReqDescription
data–yes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_coin_sentiment ~34

On-chain/social sentiment aggregates for a single coin.

NameTypeReqDescription
symbolstringyesCoin symbol, e.g. BTC.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_funding_alerts ~74

Discrete funding-rate alert events (asset, trigger zone, funding at trigger, fired-at time).

NameTypeReqDescription
fieldsstring–Token-saving: comma-separated top-level fields to keep.
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_funding_momentum ~101

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.

NameTypeReqDescription
symbolstring–Restrict to one symbol, e.g. BTC. Omit for the market-wide view.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_futures_signals ~118

Perpetual-futures signal engine. view=state (currently open signals), log (recent fires), history (one asset's past signals — needs asset).

NameTypeReqDescription
assetstring–Asset symbol, e.g. BTC. Required when view="history".
fieldsstring–Token-saving: comma-separated top-level fields to keep.
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
viewstring–Which futures view to return.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_global_market ~23

Global market aggregates: BTC dominance, total market cap, total volume.

Input schema present but exposes no named parameters.

NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_holders ~128

Tracked token-holder cohorts. view=watchlist (which token contracts are tracked), movements (recent holder-count changes for one contract). Answers "is the holder base growing or bleeding?".

NameTypeReqDescription
contractstring–Token contract address. Required when view="movements".
fieldsstring–Token-saving: comma-separated top-level fields to keep.
limitinteger–Max results.
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
viewstring–Which holder view to return.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_market_crossing ~58

The most recent regime crossing — when one trend cohort (UP/HODL/DOWN) overtook another market-wide. Answers "has the market flipped?". Returns an empty `crossings` array plus a message when no crossing has fired.

Input schema present but exposes no named parameters.

NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_market_health ~55

Overall market health: the UP/HODL/DOWN trend distribution and extreme movers. Set context for the full bundle.

NameTypeReqDescription
contextboolean–Include the full market-context bundle (breadth velocity, regime age, leadership).
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_market_sentiment ~96

Aggregate market sentiment. view=market/latest/summary (overall), narratives, categories, slopes/entity-slopes (what is trending), health (pipeline status).

NameTypeReqDescription
fieldsstring–Token-saving: comma-separated top-level fields to keep.
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
viewstring–Which sentiment view to return.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_narrative ~36

Sentiment and momentum for a single named narrative.

NameTypeReqDescription
namestringyesNarrative name, e.g. "AI coins".
NameTypeReqDescription
data–yesThe tool payload, unwrapped from the CLI envelope.
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_pair_suggestions ~206

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).

NameTypeReqDescription
dex_onlyboolean–DEX exchanges only (delta-neutral).
exchangestring–Filter by exchange (delta-neutral).
fieldsstring–Token-saving: comma-separated top-level fields to keep.
limitinteger–Max results.
modestring–Which pair view to return.
symbolstring–Filter by symbol (suggestions / delta-neutral).
token_astring–First token (required for mode="signal"), e.g. ETH.
token_bstring–Second token (required for mode="signal"), e.g. SOL.
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_prices ~129

Bulk live prices, optionally with 4h/24h/7d baseline overlays. Omit symbols for the full tracked set.

NameTypeReqDescription
baselinesboolean–Include 4h/24h/7d baseline price overlay.
fieldsstring–Token-saving: comma-separated top-level fields to keep.
symbols––Symbols as an array ["BTC","ETH"] or a comma-separated string "BTC,ETH". Omit for all tracked coins.
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
NameTypeReqDescription
data–yesThe tool payload, unwrapped from the CLI envelope.
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_regime ~73

Market regime signals. view=active (current positions), signals (all), confidence (scores). Provide symbol to get that symbol's regime history instead.

NameTypeReqDescription
symbolstring–If set, returns regime history for this symbol.
viewstring–Which regime view to return (ignored when symbol is set).
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_rwa_asset ~143

Price, daily/weekly trend and perp funding for one real-world asset (stock, ETF, commodity, index, FX). Look up by ticker (AAPL, GOLD) or by namespaced id (xyz:AAPL). Funding belongs to the PERPETUAL CONTRACT, not the underlying — `funding.apr` is the annualized rate in percent, `funding.rate` is the raw per-hour fraction. Do not use the crypto coin tools for these.

NameTypeReqDescription
bystring–How `identifier` is interpreted.
identifierstringyesTicker (AAPL, GOLD, SP500) or namespaced id (xyz:AAPL).
NameTypeReqDescription
data–yesThe tool payload, unwrapped from the CLI envelope.
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_signal ~38

Synthesized verdict for a coin, combining trend, funding, sentiment and regime.

NameTypeReqDescription
symbolstringyesCoin symbol, e.g. SOL.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_signal_quality ~59

Signal validation envelope for an asset: Sharpe ratio, win rate, sample size, reliability tier.

NameTypeReqDescription
assetstringyesAsset symbol, e.g. BTC.
signal_typestring–Signal type (default: mean_reversion).
NameTypeReqDescription
data–yesThe tool payload, unwrapped from the CLI envelope.
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_transcripts ~110

Highlights mined from tracked video/podcast transcripts. view=highlights (extracted claims with the coins, sectors and macro tags they mention), sources (which channels are tracked). Answers "what are people actually saying about X?".

NameTypeReqDescription
fieldsstring–Token-saving: comma-separated top-level fields to keep.
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
viewstring–Which transcript view to return.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_unlock_calendar ~243

Upcoming token unlocks ACROSS THE MARKET when no single coin is named: each row has date, days until, coin, tokens, USD value, % of market cap, recipients and insider (team + investor) share, with its source. Defaults: next 7 days, top 500 coins, at least 0.5 % of market cap, ranked by % of market cap. Only coins DropsTab tracks; each recipient's next release only. Answers "biggest unlocks this week?", "big VC unlocks this month?". For one coin use get_unlocks.

NameTypeReqDescription
daysinteger–Window in days from today (default 7).
insidersOnlyboolean–Only unlocks with a team or investor leg.
limitinteger–Rows to return (default 15).
maxRankinteger–Only coins up to this market-cap rank (default 500).
minPctnumber–Minimum size in % of market cap (default and floor 0.5).
sortstring–pct = biggest share of market cap (default), usd = biggest dollar value, date = soonest.
NameTypeReqDescription
data–yesThe tool payload, unwrapped from the CLI envelope.
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_unlocks ~244

Scheduled token unlocks for ONE coin: the next unlock (date, days until, tokens, USD value, % of market cap, recipients such as team/investors/ecosystem, cliff or monthly tranche), what releases over 30 and 90 days, % unlocked and locked, the final unlock date, the last unlock, and how price moved in the 7 days before and after its last 3-6 unlocks (history, not a forecast). Sources: DropsTab cross-checked with DefiLlama, each figure with its source link and fetch time; `state` says `upcoming`, `fully_unlocked`, `no_unlock_data` or `not_covered` (then `publishedSchedule` may carry the project's own vesting terms). Answers "when is ARB's next unlock?", "who gets the OP unlock?", "how did SUI trade around its unlocks?".

NameTypeReqDescription
coinIdstring–Coin id (e.g. "arbitrum") when a previous result gave it; wins over the ticker when several coins share it.
symbolstringyesCoin ticker, e.g. ARB.
NameTypeReqDescription
data–yesThe tool payload, unwrapped from the CLI envelope.
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

get_wallets ~123

Tracked wallets. view=watchlist (which wallets are tracked), movements (recent balance changes for one wallet address). Answers "what did this wallet do recently?".

NameTypeReqDescription
addressstring–Wallet address. Required when view="movements".
fieldsstring–Token-saving: comma-separated top-level fields to keep.
limitinteger–Max results.
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
viewstring–Which wallet view to return.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

list_categories ~79

List tracked crypto categories by their exact names (e.g. "Meme", "Layer-2"), the names scan_coins expects.

NameTypeReqDescription
fieldsstring–Token-saving: comma-separated top-level fields to keep.
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
NameTypeReqDescription
dataarrayyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

list_narratives ~72

List the currently active market narratives (e.g. "AI coins", "DeFi summer").

NameTypeReqDescription
fieldsstring–Token-saving: comma-separated top-level fields to keep.
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

list_rwa_assets ~152

List the tradable real-world assets — stocks and ETFs (AAPL, NVDA, SPY), metals and commodities (GOLD, SILVER, BRENT), stock indices (SP500, JP225) and FX. These trade as perps on Hyperliquid builder DEXes and are NOT crypto tokens; the crypto tools will not find them. Use this to answer "which stocks/commodities can I look at?".

NameTypeReqDescription
dexstring–Filter by builder-DEX slug, e.g. "xyz".
topinteger–Max assets to return (server default 200; the full universe is ~94).
typestring–Filter by asset class.
NameTypeReqDescription
data–yesThe tool payload, unwrapped from the CLI envelope.
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

lookup_coin ~217

Look up a single coin and its core metrics (price, trend, metadata) by symbol, name, CoinGecko/internal id, or on-chain contract address. Read the coin's CURRENT trend from `currentTrend` ({ trend: UP|DOWN|HODL, since, days, asOf, incompleteDayExcluded }; `currentTrendWeekly` when present is the weekly one), not from the last row of `trends` — `trends` is the history of past trend runs. Quote it as "<trend> since <since> (<days> days, as of <asOf>)". Only when `currentTrend` is absent, fall back to the last `trends` row.

NameTypeReqDescription
bystring–How `identifier` is interpreted.
chainstring–Chain for contract lookups (ethereum, bsc, solana, base, …). Required when by="contract".
identifierstringyesThe symbol (BTC), name (Bitcoin), id (bitcoin), or contract address.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

resolve_coin ~65

Fuzzily resolve a symbol, name, or contract to canonical coin candidates. Use this first when the user input is ambiguous, before calling other tools.

NameTypeReqDescription
limitinteger–Max candidates to return.
querystringyesSymbol, name, or contract to resolve.
NameTypeReqDescription
dataobjectyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

scan_coins ~520

Filter the tracked universe by trend direction, category and market-cap band, and sort the result. For movers questions ("what's pumping", "top gainers/losers today", "biggest movers") use sort_by="change24h" ("change7d" for the week) — sort_order="desc" for gainers, "asc" for losers — and quote each row's change from the row itself (`change_24h_pct` / `change_7d_pct`, or `change24h` / `change7d`). With the default marketCap sort rows are plain coin names; a change sort may return `{ rows: [...] }` with a coverage summary instead of a bare list. Pass ONE category per call; the server ignores case and punctuation ("meme", "Layer 2" and "DeFi" all work) and rejects an unknown name with close matches (list_categories has the names). There is no exchange filter yet: `exchange` is rejected with an explanation, because the only venue data behind this scan is spot listings. Do not present a scan as "coins on <exchange>". An empty result means no coin matched all the filters.

NameTypeReqDescription
categorystring–ONE category, e.g. "Meme", "Layer 2" or "DeFi"; case and punctuation are ignored (list_categories has the names). Comma-joined values are rejected; call once per category.
exchangestring–Not supported yet: the server rejects it with an explanation (its venue data covers spot listings only, so a filtered answer would mislead). Leave unset.
fieldsstring–Token-saving: comma-separated top-level fields to keep.
intervalstring–Trend interval: 1d (daily) or 1w (weekly).
limitinteger–Max results.
mcap_maxnumber–Maximum market cap in USD.
mcap_minnumber–Minimum market cap in USD.
sort_bystring–Sort key (default marketCap). change24h / change7d = 24h / 7d price change, for movers / "what's pumping" questions.
sort_orderstring–desc (default) = largest first; asc = smallest first (e.g. biggest 24h losers).
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
trendstring–Filter by trend direction.
NameTypeReqDescription
data–yes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

scan_trends ~127

Trend scanner. state=fresh (newly started), stale (longest running), aligned (multi-timeframe agreement), extreme (biggest moves), historical.

NameTypeReqDescription
fieldsstring–Token-saving: comma-separated top-level fields to keep.
intervalstring–Trend interval: 1d (daily) or 1w (weekly).
limitinteger–Max results.
statestring–Which trend slice to return.
topinteger–Keep only the first N items (default 50). Raise for more, lower to save tokens.
NameTypeReqDescription
dataarrayyes–
meta––Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

No examples provided.

search_web ~59

Search the web for crypto information, or get a direct answer. Backed by Shumi's web-search tool.

NameTypeReqDescription
answerboolean–Return a direct synthesized answer instead of raw search results.
querystringyesWhat to search for.
NameTypeReqDescription
answerstring–The synthesized natural-language answer. Absent only when the engine produced no prose.
steps––Raw engine steps. Present only as a fallback when `answer` is absent.

No examples provided.

Install

How do I install the ai.shumi/mcp server?

ai.shumi/mcp is a hosted endpoint at https://mcp.shumi.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.shumi.ai

# add to Claude Code
claude mcp add --transport http ai-shumi-mcp 'https://mcp.shumi.ai/mcp'
Common questions

What is the ai.shumi/mcp server?

ai.shumi/mcp is listed in the public MCP registry as ai.shumi/mcp. Crypto market intelligence: prices, funding rates, narratives, regime, and delta-neutral research. This page covers its hosted endpoint (https://mcp.shumi.ai/mcp).

Is the ai.shumi/mcp server safe to use?

ai.shumi/mcp scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ai.shumi/mcp server expose?

ai.shumi/mcp exposes 33 tools: get_coin_risk, lookup_coin, resolve_coin, get_coin_sentiment, get_coin_historical, and 28 more. Their descriptions and schemas cost roughly 3,935 tokens of context every time the server is loaded.

Does the ai.shumi/mcp server require authentication?

No. We connected to ai.shumi/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ai.shumi/mcp server still maintained?

ai.shumi/mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.