Home / MCP registry index / com.cryptowhaleinsights/whale-insights

com.cryptowhaleinsights/whale-insights

com.cryptowhaleinsights/whale-insights in the official MCP registry. Endpoint https://cryptowhaleinsights.com/mcp.

The registry describes it as: Free read-only crypto whale-tracking & market-data MCP tools across 14 chains. No auth.

We read its 56 tools on 2026-10-27. 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

platform_stats status live_stats recent_whales trending gas funding_rates stablecoin_flows liquidations airdrops tax_rates fear_greed market_heatmap narratives bridge_flows burn_tracker sentiment_history funding_rates_history whale_daily_summary stablecoin_history social_summary whale_activity analysts analysts_signals analysts_signals_all analysts_top analyst_archive whale_movements whale_movements_summary feed_archive reports_index golden_alerts_snapshot analyst_monthly_performance golden_alerts_history golden_alerts_monthly whale_monthly_archive fear_greed_monthly sentiment_monthly stablecoin_monthly funding_rate_monthly signal_history_monthly analyst_top_tokens arbitrage_history analyst_daily_summary analyst_summary_history market_context arbitrage_monthly leverage_history leverage_picks_summary leverage_radar market_pulse_history gas_price_history narrative_history bridge_flow_history whale_score_history fear_greed_history

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-cryptowhaleinsights-whale-insights/badge.svg)](https://lazaretto.dev/mcp-registry/com-cryptowhaleinsights-whale-insights)

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.

Related

Crypto and Web3 MCP servers

The Stall
ai.intuitek.the-stall/the-stall
200 tools, nothing matched
2026-10-22
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
200 tools, nothing matched
2026-10-22
Citiview Agent Market
com.citiviewgroup.mcp/agent-market
200 tools, nothing matched
2026-10-26
ScorpTech x402 API
com.it.scorptech/x402
200 tools, nothing matched
2026-10-26
Apex Edge — x402-paid machine services
dev.pages.nonsynthetic/apex-edge
200 tools, nothing matched
2026-10-23
io.github.praneeth12098/x402-factory
io.github.praneeth12098/x402-factory
200 tools, nothing matched
2026-10-26