Web3 Research MCP vs CPZAI
A side-by-side look at the Web3 Research MCP and CPZAI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Web3 Research MCP for finance & fintech work as a local process; choose CPZAI 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 Web3 Research 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.
- You want tools like
search, create-research-plan, research-with-keywords.
Choose CPZAI when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
hedge_ratio, tolerance_band, benchmark_symbol.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 68/100 · Great | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 168 | 1 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 13 | 4 |
| Full listing | View Web3 Research MCP | View CPZAI |
Tools & capabilities
Web3 Research MCP tools 13
searchcreate-research-planresearch-with-keywordsupdate-statusfetch-contentsearch-sourcelist-resourcesresearch-sourcecoingecko-datacoingecko-searchcoingecko-tickersdefillama-data- +1 more on the listing page
CPZAI tools 4
hedge_ratiotolerance_bandbenchmark_symbollist_overlays
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.
Web3 Research MCP
{
"mcpServers": {
"aaronjmars-web3-research-mcp": {
"command": "npx",
"args": [
"-y",
"web3-research-mcp@latest"
]
}
}
}
CPZAI
{
"mcpServers": {
"cpzai": {
"url": "https://mcp.cpz-lab.com/mcp"
}
}
}
Frequently asked questions
Web3 Research MCP is categorized under Finance & Fintech and uses a local stdio subprocess. CPZAI belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Web3 Research MCP for finance & fintech work and CPZAI 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.
Web3 Research MCP is listed as free. Auth: no auth required. CPZAI 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 aaronjmars-web3-research-mcp and cpzai as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Web3 Research MCP has a quality signal of 68/100 (Great) with 4 views, 0 installs and 168 GitHub stars. CPZAI has 51/100 (Good) with 1 views, 0 installs and 1 GitHub stars.