Delv
CommunityAbandoned· 1.1y4.3by kukapay

Whale Tracker MCP

Tracks large cryptocurrency transactions through the Whale Alert API for on-chain whale movement monitoring.

C
Safety & Trust

Delv Safety Grade: C

Score 58/100 · assessed 2026-04-28

Maintainer45
Permissions85
Supply chain55
Transparency60
Incidents100

Whale Tracker MCP is a community-built server that queries the Whale Alert API to monitor large cryptocurrency transactions. The maintainer 'kukapay' appears to be a solo developer with limited public profile and sparse repository activity. The server requires a Whale Alert API key stored in environment variables, which introduces credential management risk. Permissions are appropriately scoped to read-only API calls with outbound network access, making the attack surface relatively narrow. Supply chain concerns include installation via npx with the Smithery CLI rather than a direct npm package, and the repository shows minimal maintenance history. Transparency is moderate with basic documentation but limited community engagement. No security incidents are known. The primary risks stem from the unknown maintainer provenance and the need to manage a third-party API key, though the functional scope remains safely constrained to data fetching.

Lethal Trifecta (prompt-injection exposure)

ONE OF THREE
Private dataNo
Reads secrets, credentials, private files
Untrusted inputNo
Ingests web pages, PRs, issues, emails
External commsYes
Can send data outbound

Public chain data.

Green flags

  • Read-only API integration with no write permissions
  • Narrow functional scope limited to whale transaction monitoring
  • Open source repository available for inspection
  • No known security incidents or malicious behaviour
  • Clear documentation of required API key

Red flags

  • Solo maintainer 'kukapay' with minimal public profile or track record
  • Requires third-party API key (WHALE_ALERT_API_KEY) stored in environment
  • Installation via Smithery CLI rather than direct npm package
  • Limited repository activity and maintenance signals
  • No verification of maintainer identity or organizational backing

Permissions requested

Outbound networkAccess secrets
Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

npx -y @smithery/cli install @kukapay/whale-tracker-mcp --client claude
Env vars needed: WHALE_ALERT_API_KEY

Review

Whale Tracker MCP hooks Claude up to the Whale Alert API, letting you query large crypto transactions without leaving your editor. You ask for recent whale movements on a specific blockchain, and it returns transaction hashes, amounts, timestamps, and wallet addresses. It's a straightforward data fetch tool that does one thing well: surfacing on-chain activity that might signal market moves or institutional behaviour. I'd reach for this when researching a token's holder concentration or checking if a sudden price swing correlates with a big transfer. The workflow is simple: ask Claude to fetch recent whale transactions for Ethereum or Bitcoin, scan the results for patterns, then follow up with questions about specific wallets or transaction sizes. It saves you from tabbing over to a blockchain explorer every time you want context on a large transfer. The main quirk is that you're entirely dependent on Whale Alert's API limits and data quality. If you're on a free tier, you'll hit rate limits quickly. The server doesn't cache responses, so repeated queries for the same timeframe will burn through your quota. It also won't interpret the data for you: Claude can summarise and contextualise, but the raw transaction data is just addresses and amounts. You still need to know what constitutes a 'whale' move for the asset you're tracking. This is useful for anyone doing on-chain research, tracking institutional flows, or writing market commentary. If you're building a trading bot or need real-time alerts, this isn't it. It's a query tool, not a monitoring service. You ask, it fetches, you interpret. If you're not already familiar with on-chain analysis or don't have a Whale Alert API key, the setup friction probably isn't worth it unless you're serious about tracking large transfers. For everyone else, it's a clean, focused tool that does exactly what the name suggests.
Verdict

Install this if you regularly analyse on-chain activity and want transaction data inside your Claude workflow. Skip it if you're not already doing crypto research or don't have a Whale Alert API key. It's a narrow tool that does its job well but won't teach you on-chain analysis.

Good at

  • Focused scope: it fetches whale transactions and nothing else, so there's no feature bloat.
  • Works directly in Claude Desktop, so you can query and interpret on-chain data without switching tools.
  • Returns structured transaction data (hashes, amounts, timestamps) that Claude can parse and summarise.
  • Supports multiple blockchains through Whale Alert's coverage, so you're not locked to Ethereum.

Watch out

  • Entirely dependent on Whale Alert's API limits, which can be restrictive on free tiers.
  • No caching, so repeated queries for the same timeframe will burn through your quota unnecessarily.
  • Requires an external API key, which adds setup friction and ongoing cost for heavy users.
  • Won't interpret or contextualise the data beyond what Claude can infer from raw transaction details.

Use cases

  • whale movement alerts
  • on-chain research
  • market impact analysis
  • token holder tracking

Getting started

1. Get a Whale Alert API key from their website (free tier available but limited). 2. Run `npx -y @smithery/cli install @kukapay/whale-tracker-mcp --client claude` to install. 3. Add `WHALE_ALERT_API_KEY` to your environment variables in the Claude Desktop config. 4. Restart Claude Desktop, then ask it to fetch recent whale transactions for a specific blockchain to verify the connection. 5. Watch your API rate limits: repeated queries for the same data will count against your quota, so be deliberate about what you ask for.

Works with

Claude DesktopClaude CodeCursor

Similar MCPs