Home / MCP registry index / ai.shumi/mcp
ai.shumi/mcp
ai.shumi/mcp in the official MCP registry.
Endpoint https://mcp.shumi.ai/mcp. Source: github.com/shumi-ai/shumi-mcp.
The registry describes it as: Crypto market intelligence: prices, funding rates, narratives, regime, and delta-neutral research.
We read its 33 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_coin_risk lookup_coin resolve_coin get_coin_sentiment get_coin_historical get_market_health get_global_market get_market_crossing 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 ask_shumi search_web
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-shumi-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.