fomo-mcp
Related Servers
Alternatives to fomo-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read multi-chain memecoin launchpad data including coins, burns, staking, fee boards, and read-only perps markets, while calculating quotes and preparing buys, sells, stakes, unstakes, and launches for the user’s own wallet to sign.MIT
- AlicenseNot gradedqualityBmaintenanceAutonomous Solana trading bot with 281 MCP tools across Meme sniping (Pump.fun), Spot trading (Jupiter), Perpetual futures, and Mirror copy-trading modes.145 PyPIAcademic Free v1.1
- AlicenseNot gradedqualityBmaintenanceRead-only token intelligence for Robinhood Chain and Solana, providing safety checks, ticker resolution, deployer records, whale wallet tracking, and outcome measurements via a hosted MCP server.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to research, trade and move money across crypto spot and perpetuals, stocks, commodities, forex, prediction markets, onchain swaps and bridging, and memecoins through a single remote MCP connection with no installation or hosting required. It also supports wallet management, fiat on-ramps and token launches, with every write action asking the user for approval first.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the Monad blockchain. Provides tools for balances, transfers, swaps, and DeFi with Privy wallet signing.120 npm2MIT
TDQS
Scored across 42 tools
Multiple tools overlap: fomo_token_warnings, fomo_token_allow_list, and fomo_verified_tokens all describe token status/allowlist data; fomo_token_thesis and fomo_token_sorted_thesis are near-duplicates; fomo_get_user_swaps, fomo_get_trades, fomo_trading_activity, and fomo_token_feed all expose trade/swap feeds. An agent would need to understand subtle scope differences to choose the right tool.
Most tools share the fomo_ prefix and snake_case, and many use verb-first names like fomo_get_* and fomo_search_*. However, a substantial minority use bare noun phrases (fomo_ohlcv, fomo_token_details, fomo_top_holders, fomo_token_allow_list) and fomo_transfers_with is an odd verb form, so the pattern is readable but inconsistent.
With 42 tools, the surface is well above the 25-tool threshold and creates significant selection overhead. Several tools could be consolidated, such as the thesis variants, token allowlist variants, and overlapping trade/swap feeds.
Read coverage is extensive across users, clans, trades, tokens, watchlist, and transfers, but the surface has dead ends: comments can be read but not created, swap quoting is present without swap execution, and transfer tools only query history. Core analytics workflows are covered, but transactional/social actions are missing.