CPZAI vs PubFi MCP

A side-by-side look at the CPZAI and PubFi MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

CPZAI logoCPZAIFinance & Fintech · Remote HTTP/SSEBuild, backtest, and deploy quantitative trading strategies from your AI agent.51GoodAuth: not declaredPubFi MCP logoPubFi MCPFinance & Fintech · Local subprocess (stdio)Route crypto data needs through PubFi capability and gateway tools.44FairAuth: not declared

Verdict: choose CPZAI for finance & fintech work over a hosted endpoint; choose PubFi 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?

CPZAI logoChoose 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.
Explore CPZAI

PubFi MCP logoChoose PubFi MCP when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
Explore PubFi MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCPZAI logoCPZAIPubFi MCP logoPubFi MCP
CategoryFinance & FintechFinance & Fintech
Quality signal51/100 · Good44/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars10
Directory activity 1 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools4Not listed

Tools & capabilities

CPZAI tools 4

  • hedge_ratio
  • tolerance_band
  • benchmark_symbol
  • list_overlays

PubFi 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.

CPZAI

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "cpzai": {
      "url": "https://mcp.cpz-lab.com/mcp"
    }
  }
}

PubFi MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "pubfi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mint@latest"
      ]
    }
  }
}

Frequently asked questions

CPZAI is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. PubFi MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick CPZAI for finance & fintech work and PubFi 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. PubFi MCP 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 cpzai and pubfi-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. PubFi MCP has 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.