Shumi MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Shumi read-only crypto market-intelligence tools: Do synthesized signals remain labeled as intelligence rather than execution authority or investment recommendations?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Read-only crypto/market intelligence for research, risk and signal analysis.

What we know

Thin MCP wrapper over Shumi's data API for prices, trends, funding, sentiment, narratives, market regime, signals, pair ideas, wallets/holders and real-world-asset/perp intelligence.

Maintenance / activity evidence

@shumi-ai/mcp 1.2.1 published 2026-09-24T14:24:01.643Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Official docs explicitly describe MCP tools as read-only market/account intelligence.
Shumi API key.
Sensitive access: Market research queries, Wallet address context if configured, API key

Read-only surface, but financial data can drive high-stakes decisions; treat outputs as research.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do synthesized signals remain labeled as intelligence rather than execution authority or investment recommendations?

The bounded review of the publisher's documented Shumi read-only crypto market-intelligence tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Read-only surface, but financial data can drive high-stakes decisions; treat outputs as research.
Official docs explicitly describe MCP tools as read-only market/account intelligence.
Shumi API key.
Queries and optional wallet context go to Shumi; third-party social/news text is untrusted.
Sensitive access: Market research queries, Wallet address context if configured, API key
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Requires Shumi API key for most useful tools.
Tier/quota/pay-per-call gating is server-side.
Some free-form analysis endpoints may be slow/cost credits.
Market intelligence is not trade execution.

Original activity observations

@shumi-ai/mcp 1.2.1 published 2026-09-24T14:24:01.643Z

Technical identity

npm/@shumi-ai/mcp

Exact implementation source: https://www.npmjs.com/package/@shumi-ai/mcp ↗
Reviewed resource type: MCP Server
Repository identity: shumi-ai/shumi-mcp
Package identity: npm:@shumi-ai/mcp
Service endpoint: https://mcp.shumi.ai/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@shumi-ai/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Token required. Local stdio path documented; remote HTTP is key-header based not OAuth.
Configure npx -y @shumi-ai/mcp in MCP client with env SHUMI_TOKEN=shumi_sk_... . Hosted entry uses an Authorization header rather than URL query parameters.
publisher documented step or launch · Publisher instructions
npx -y @shumi-ai/mcp
Configure / authenticate
MCP100 setup guide
Use the publisher-provided MCP client registration for the stated transport; complete the authentication and prerequisites below. Do not treat npm package installation alone as a connected client. Token required. Local stdio path documented; remote HTTP is key-header based not OAuth.
Environment variables referenced by this route (respect the alternatives above): SHUMI_TOKEN
Check connection
Suggested check
Verify read-only `get_market_health` is discoverable. Do not treat HTTP 200 alone as authenticated success: publisher returns in-band AUTH_REQUIRED.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
SHUMI_TOKEN is a Shumi API key; provider-side revoke/rotation UI not verified in reviewed publisher README.

Official Documentation & Sources

https://www.npmjs.com/package/@shumi-ai/mcp ↗

What it does

Thin MCP wrapper over Shumi's data API for prices, trends, funding, sentiment, narratives, market regime, signals, pair ideas, wallets/holders and real-world-asset/perp intelligence.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing
Best fit: Read-only crypto/market intelligence for research, risk and signal analysis.

Representative uses

Assess coin risk and market health
Analyze funding and narratives
Inspect signals/pairs/wallets/holders
Ask synthesized market questions

Limitations

Requires Shumi API key for most useful tools.
Tier/quota/pay-per-call gating is server-side.
Some free-form analysis endpoints may be slow/cost credits.
Market intelligence is not trade execution.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Shumi API key.
Permissions: Official docs explicitly describe MCP tools as read-only market/account intelligence.
Data handling: Queries and optional wallet context go to Shumi; third-party social/news text is untrusted.
Cost: tiered_or_pay_per_call
Risk and cautions: Read-only surface, but financial data can drive high-stakes decisions; treat outputs as research.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Market research queries Wallet address context if configured API key
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Assess coin risk and market health; Analyze funding and narratives; Inspect signals/pairs/wallets/holders; Ask synthesized market questions.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @shumi-ai/mcp. Recorded endpoint: https://mcp.shumi.ai/mcp. Recorded transport: stdio, http. Recorded environment-variable notes: SHUMI_TOKEN; SHUMI_API_URL (optional); SHUMI_WALLET (optional context). No configuration values are supplied here. Prerequisites: MCP client; Shumi key. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Shumi API key via env or Authorization/x-api-key header for remote.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Official docs explicitly describe MCP tools as read-only market/account intelligence.

What data-handling boundary should I consider?

Queries and optional wallet context go to Shumi; third-party social/news text is untrusted. Recorded sensitive-access context: Market research queries; Wallet address context if configured; API key.

What limitations and risks should I check before use?

Read-only surface, but financial data can drive high-stakes decisions; treat outputs as research. Requires Shumi API key for most useful tools. Tier/quota/pay-per-call gating is server-side. Some free-form analysis endpoints may be slow/cost credits. Market intelligence is not trade execution. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is tiered or pay per call. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.