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
- AlicenseAqualityBmaintenanceReal-time crypto market & tokenized equity intelligence MCP over x402 USDC on Base mainnet (eip155:8453) by Keith S. (kwizzlesurp.com · Sevtech · Dragon&PandaDuo). Includes price feeds, volatility, sentiment, risk scores, NAV deviation, and peg-gap radar. Verified provider on x402-trust.com.213MIT

Vike Data MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to query crypto data through a hosted remote endpoint: on-chain wallet and token analytics across Ethereum, BNB Chain, Base and HyperEVM, Hyperliquid perp positions and market stats, cohort-based long/short positioning, and Polymarket markets and smart-money flows. Connects via OAuth 2.1 or an API key header from Claude, Cursor, VS Code, and other MCP clients.1MIT- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to access aggregated cryptocurrency market data, technical analysis, derivatives intelligence, TradingView screeners, funding-rate comparisons, local ML forecasts, and optional Bitget account operations through a single MCP connection.MIT
- AlicenseAqualityDmaintenanceA comprehensive cryptocurrency market-data MCP server with 49 tools across six data sources, enabling LLMs to answer market questions via natural language.49MIT
- AlicenseNot gradedqualityCmaintenanceProvides 59 pay-per-call AI tools covering crypto prices and audits, market and whale data, LLM chat, image generation, web search/fetch/summarize, and utility services, with automatic x402 USDC-on-Base payments and on-chain receipts. It works with Claude Code/Desktop, Cursor, and other MCP clients without API keys or subscriptions.53 npmMIT
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.