A side-by-side look at the Keel Trade and Coincap MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Keel Trade 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?
Choose Keel Trade when
You need dedicated capabilities in the Finance & Fintech domain.
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.
Keel Trade 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 Keel Trade 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.
Keel Trade is listed as free. 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 keel-trade-keel-trade and quantgeekdev-coincap-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Keel Trade has a quality signal of 49/100 (Fair) with 3 views, 0 installs and 2 GitHub stars. Coincap MCP has 55/100 (Good) with 5 views, 0 installs and 92 GitHub stars.