What is the main functional difference between Coincap MCP and WalletFollow?

Coincap MCP is categorized under Finance & Fintech and uses a local stdio subprocess. WalletFollow belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Coincap MCP for finance & fintech work and WalletFollow for finance & fintech.

How do I install Coincap MCP or WalletFollow in Claude Desktop, Cursor, or Windsurf?

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Are Coincap MCP and WalletFollow free to use, or do they require API keys?

Coincap MCP is listed as free. Auth: no auth required. WalletFollow is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Can I run both Coincap MCP and WalletFollow at the same time in my AI client?

Yes. MCP clients support multiple servers: add quantgeekdev-coincap-mcp and walletfollow as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Coincap MCP has a quality signal of 55/100 (Good) with 5 views, 0 installs and 92 GitHub stars. WalletFollow has 47/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.

Coincap MCP vs WalletFollow

A side-by-side look at the Coincap MCP and WalletFollow MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Coincap MCPFinance & Fintech · Local subprocess (stdio)Real-time cryptocurrency market data integration using CoinCap's public API, providing access to crypto prices and market information without API keys55GoodAuth: no auth required

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.0

Verdict: choose Coincap MCP for finance & fintech work as a local process; choose for finance & fintech over a hosted endpoint. You can also run both side by side in one block.

Spec	Coincap MCP	W WalletFollow
Category	Finance & Fintech	Finance & Fintech
Quality signal	55/100 · Good	47/100 · Fair
Install command	Confirmed	Confirmed
Transport	Local subprocess (stdio)	Remote HTTP/SSE
Auth	No auth required	OAuth 2.0
Pricing	Free	Freemium
Required env vars	None listed	None listed
Verified owner	Community listing	Community listing
GitHub stars	92	—
Directory activity	5 views 0 installs 0 upvotes	2 views 0 installs 0 upvotes
Tools	Not listed	Not listed
Full listing	View Coincap MCP	View WalletFollow

Coincap MCP vs WalletFollow

Which MCP server should you choose?

Choose Coincap MCP when

W
Choose WalletFollow when

Feature & specification comparison

Tools & capabilities

Coincap MCP tools

WalletFollow tools

Ready-to-paste client configs

Coincap MCP

WalletFollow

Frequently asked questions