WalletFollow vs Coincap MCP
A side-by-side look at the WalletFollow and Coincap MCP 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 WalletFollow for finance & fintech work over a hosted endpoint; choose Coincap MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
WChoose WalletFollow when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Choose Coincap MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W WalletFollow | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 47/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | No auth required |
| Pricing | Freemium | Free |
| Required env vars | None listed | None listed |
Tools & capabilities
WalletFollow tools
No tool names declared yet. Check the project README from the listing page.
Coincap MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
WalletFollow
{
"mcpServers": {
"walletfollow": {
"url": "https://mcp.walletfollow.ai/mcp"
}
}
}
Coincap MCP
{
"mcpServers": {
"quantgeekdev-coincap-mcp": {
"command": "npx",
"args": [
"coincap-mcp"
]
}
}
}
Frequently asked questions
WalletFollow is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Coincap MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick WalletFollow for finance & fintech work and Coincap MCP for finance & fintech.
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.
WalletFollow is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. Coincap MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add walletfollow and quantgeekdev-coincap-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, WalletFollow has a quality signal of 47/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Coincap MCP has 55/100 (Good) with 5 views, 0 installs and 92 GitHub stars.