Skip to main content
Glama
Eurobertics

MCP Pionex Management

by Eurobertics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP Pionex Management

No user-submitted related servers found.

    Related Servers

    • mcp-pionex

      alejandrorodm
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with the Pionex exchange through MCP, providing market data, account info, spot trading, grid bots, and Dual Investment tools with strict anti-hallucination guardrails including two-phase order confirmation and live symbol/price validation.
      43
      MIT

    • htx-mcp

      TeacherLi07
      F
      license
      A
      quality
      B
      maintenance
      Enables natural-language access to HTX exchange spot and USDT-margined futures market data, accounts, orders, positions, and trading operations, with safety confirmations and a read-only mode.
      15
      -

    • Bybit Server

      dlwjdtn535
      A
      license
      B
      quality
      D
      maintenance
      Interact seamlessly with the Bybit API to fetch market data, manage your account, and execute trades. Leverage powerful tools to enhance your trading experience and automate your strategies effortlessly. If you wish to use an API key restricted to your personal IP address, you must configure the MCP
      15
      9
      MIT
    • gate-local-mcp by gate

      gate-local-mcpofficial

      gate
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes the full Gate API v4 to MCP clients with 384 tools for spot, futures, margin, wallet, and more. Supports both public endpoints (no auth) and authenticated trading operations.
      48 npm
      1
      MIT

    • Dragonglass TradingView MCP

      nightwing-7
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI co-pilots to interact with TradingView charts, manage alerts via REST API, automate morning briefs with custom trading rules, and perform real-time market analysis.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 70 tools

    Disambiguation4/5

    Most tools have clear resource+action boundaries (market data vs. orders vs. bots vs. earn), and the many dry-run variants are marked with a `_check` suffix. However, there are several easily confused pairs: `get_bot_orders` vs. `get_futures_grid_order`/`get_spot_grid_order`, `adjust_futures_grid_params` vs. `add_margin_futures_grid`, and `reduce_futures_grid` vs. `reduce_margin_futures_grid`.

    Naming Consistency3/5

    The server broadly follows a `pionex_<domain>_<action>` snake_case pattern, which is readable and predictable. But verb conventions are mixed: `new_order` vs. `create_*`, `fetch_products` vs. `get_*`, several earn endpoints lack a verb (`dual_symbols`, `dual_products`, `dual_prices`), and `signal_listener` is a noun rather than an action.

    Tool Count1/5

    With 70 tools, the server is far beyond a reasonable MCP surface and exceeds the 50+ threshold for extreme mismatch. Even though the domain is broad (market, orders, wallet, bots, earn), this should be split into several focused servers or consolidated.

    Completeness4/5

    Coverage is broad: market data, order lifecycle, balances, grid/copy bots, signals, and earn products are all represented. Minor gaps remain, such as wallet deposit/withdraw/transfer operations and order modification, but core trading workflows are largely complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources