Codex MCP vs WalletFollow
A side-by-side look at the Codex MCP and WalletFollow MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
WalletFollowFinance & Fintech · Remote HTTP/SSEConnect AI assistants to Hyperliquid wallet and portfolio research over Streamable HTTP at https://mcp.walletfollow.ai/mcp. The hosted connector exposes 62 read-only tools for wallet metrics, positions, retained trade history, market observations and published copy portfolios. Responses include source timestamps and coverage limits. Browser OAuth requires a verified WalletFollow account and an eligible research API key; existing plan quotas and permissions apply. This connector cannot execute trades, request wallet signatures or move funds. Public client plugin and skills: https://github.com/AperiAnalytics/walletfollow-plugin.47FairAuth: oauth 2.0Verdict: choose Codex MCP for finance & fintech work as a local process; choose WalletFollow for finance & fintech over a hosted endpoint. You can also run both side by side in one block.