CNEquity vs Dexscreener

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

CNEquity logoCNEquityFinance & Fintech · Local subprocess (stdio)China A-share data lake for AI agents: prices, fundamentals, flows and events, point-in-time.49FairAuth: no auth requiredDexscreener logoDexscreenerFinance & Fintech · Local subprocess (stdio)DEX Screener MCP — DEX price/liquidity/volume data41FairAuth: not declared

Verdict: choose CNEquity for finance & fintech work as a local process; choose Dexscreener 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?

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

Dexscreener logoChoose Dexscreener when

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCNEquity logoCNEquityDexscreener logoDexscreener
CategoryFinance & FintechFinance & Fintech
Quality signal49/100 · Fair41/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars8461
Directory activity 3 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

CNEquity tools

No tool names declared yet. Check the project README from the listing page.

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

CNEquity

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "cnequity": {
      "command": "uvx",
      "args": [
        "cnequity"
      ]
    }
  }
}

Dexscreener

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

Frequently asked questions

CNEquity is categorized under Finance & Fintech and uses a local stdio subprocess. Dexscreener belongs to Finance & Fintech and uses a local stdio subprocess. Pick CNEquity for finance & fintech work and Dexscreener 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.

CNEquity is listed as free. Auth: no auth required. Dexscreener 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 cnequity and dexscreener as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, CNEquity has a quality signal of 49/100 (Fair) with 3 views, 0 installs and 846 GitHub stars. Dexscreener has 41/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.