A side-by-side look at the Coincap MCP and Revinho MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Coincap MCP for finance & fintech work as a local process; choose Revinho for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Coincap MCP when
You need dedicated capabilities in the Finance & Fintech domain.
No tool names declared yet. Check the project README from the listing page.
Revinho 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.
Coincap MCP is categorized under Finance & Fintech and uses a local stdio subprocess. Revinho belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Coincap MCP for finance & fintech work and Revinho 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.
Coincap MCP is listed as free. Auth: no auth required. Revinho has no declared pricing — check the project's own site. 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 quantgeekdev-coincap-mcp and revinho as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Coincap MCP has a quality signal of 55/100 (Good) with 5 views, 0 installs and 92 GitHub stars. Revinho has 39/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.