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.84-
- AlicenseAqualityCmaintenanceEnables agents to read live pump.fun coin calls, market and study data, and paper-trade results graded by net return after costs, plus backtest and run custom entry/exit strategies against published history. It exposes these as MCP tools, prompts, and a hosted or local server with no wallet or key required.1355 npm9MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents and command-line users to query pump.fun's full on-chain trade history, including pre-buy checks on a token's deployer, bundle and insiders, wallet classification and ranking, deployer records, and market-cap base rates. Results come back as structured JSON so an agent can answer questions about launches and wallets from recorded data rather than guesses.1MIT
- 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
- AlicenseAqualityBmaintenanceEnables AI assistants to watch live Solana token launches, research coins, devs and wallets, and optionally buy, sell, claim creator fees or launch tokens from chat. All data is read straight from on-chain pump.fun events and bonding curves, while trades are simulated first, capped, and signed locally so the private key never leaves the machine.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables coordinated pump.fun buys, sells, and token launches using encrypted local Rust wallets, with previews, simulation, Jito bundle submission, status tracking, and pump.fun API/RPC access through MCP tools.MIT
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.