CPZAI vs Web3 Research MCP
A side-by-side look at the CPZAI and Web3 Research MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CPZAI for finance & fintech work over a hosted endpoint; choose Web3 Research 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 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.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 51/100 · Good | 68/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 168 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 4 | 13 |
| Full listing | View CPZAI | View Web3 Research MCP |
Tools & capabilities
CPZAI tools 4
hedge_ratiotolerance_bandbenchmark_symbollist_overlays
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
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.
CPZAI
{
"mcpServers": {
"cpzai": {
"url": "https://mcp.cpz-lab.com/mcp"
}
}
}
Web3 Research MCP
{
"mcpServers": {
"aaronjmars-web3-research-mcp": {
"command": "npx",
"args": [
"-y",
"web3-research-mcp@latest"
]
}
}
}
Frequently asked questions
CPZAI is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Web3 Research MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick CPZAI for finance & fintech work and Web3 Research 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.
CPZAI has no declared pricing — check the project's own site. Web3 Research 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 cpzai and aaronjmars-web3-research-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CPZAI has a quality signal of 51/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Web3 Research MCP has 68/100 (Great) with 4 views, 0 installs and 168 GitHub stars.