Surf MCP Server
OfficialRelated Servers
Alternatives to Surf MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI tools to access local crypto market data, run analyses, perform 66-item deep research, search RAG context, and retrieve generated reports and prompts via MCP.10MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to access real-time crypto market data, volatility alerts, sentiment analysis, risk scores, and market reports through micropayment-gated MCP tools with on-chain settlement.-
- AlicenseAqualityDmaintenanceA comprehensive cryptocurrency market-data MCP server with 49 tools across six data sources, enabling LLMs to answer market questions via natural language.49MIT
- FlicenseNot gradedqualityDmaintenanceExposes Musashi market intelligence as MCP tools for clients like Claude and ChatGPT, enabling text analysis, arbitrage detection, market movers, wallet activity, and smart money tracking.-
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI clients to access live crypto market data and AI-driven quantitative analysis, with structured outputs and full observability.-

NEX MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables any MCP client to access 11 AI inference and data tools, including chat, code, vision, embeddings, crypto prices, weather, geolocation, currency exchange, and WHOIS, with a free tier and paid USDC-on-Base endpoints.Apache 2.0
TDQS
Scored across 15 tools
Each top-level tool has a distinct domain prefix (dex, exchange, market, prediction_market, etc.), but there is some overlap: surf_dex and surf_hyperliquid both provide DEX data, and surf_market vs surf_exchange could be confused for price/derivatives data. Descriptions generally help clarify the boundaries.
All tools follow the consistent 'surf_<domain>' naming pattern, and subcommands use lowercase hyphenated names. The convention is uniform across the entire set, making it predictable and easy to navigate.
15 tools is within the ideal 3-15 range, and each tool represents a coherent data domain (market, wallet, token, onchain, etc.). The count feels well-scoped for the server's broad crypto data aggregation purpose.
The tool surface covers a wide range of crypto data needs: market, exchange, DEX, prediction markets, onchain, wallet, token, project, fund, news, search, and web. Minor gaps exist (e.g., surf_dex only offers OHLCV, surf_x only fetches tweets by ID), but these are partial gaps within subdomains rather than severe dead ends.