Pump Fun Data MCP Server
Related Servers
Alternatives to Pump Fun Data MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityCmaintenanceReal-time Solana pump.fun token scanner with MCP stdio transport and HTTP API. Enables AI agents to monitor and trade pump.fun tokens via natural language.83-
- AlicenseNot gradedqualityDmaintenanceSolana on-chain intelligence API — token scans, wallet PnL, bundle detection, fresh wallets, dev profiling. MCP server for Claude, Cursor & AI agents. Live PumpFun/Raydium streams1MIT
- AlicenseAqualityAmaintenanceSolana KOL trading intelligence and deployer analytics. Query real-time trades from 946 tracked KOL wallets, convergence signals, PnL leaderboards, and elite Pump.fun deployer alerts — paid per request with USDC via x402.511912MIT
- AlicenseAqualityAmaintenanceSolana memecoin rug check and token risk for trading agents in the trenches: pump.fun launches, calibrated rug probability with a published hit rate, sniper, insider and bundle detection, holder clusters, KOL trades, wallet history and a live sellability check for memecoins. Available as a remote MCP endpoint (OAuth or API key) and as an npm stdio package.26230MIT
- AlicenseAqualityDmaintenanceReal-time radar for Solana memecoins, Pump.fun launches, and KOL trades.82MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol server enabling AI assistants to create, buy, and sell tokens on the Pump.fun platform on Solana.622-
TDQS
Scored across 3 tools
The tools have some overlap in purpose, as both get_coins and get_featured_coins retrieve lists of coins, which could cause confusion about when to use each. However, get_coin_info is clearly distinct for retrieving detailed information about a specific coin, and the descriptions help differentiate the list tools by indicating one is for general coins and the other for featured ones.
All tool names follow a consistent verb_noun pattern with 'get_' as the prefix and snake_case throughout (e.g., get_coin_info, get_coins, get_featured_coins). There are no deviations or mixed conventions, making the naming predictable and readable.
With only 3 tools, the server feels under-scoped for a data server, as it lacks essential operations like creating, updating, or deleting coins, which are typical for managing data. This minimal set may limit agent functionality and suggests an incomplete surface for the domain.
The tool surface is severely incomplete for a data server, covering only read operations (get) with no ability to create, update, or delete coins. This creates significant gaps that will likely cause agent failures when trying to perform full data management workflows, such as adding new coins or modifying existing ones.