Skip to main content
Glama
flytam

Crypto Exchange SDK Documentation MCP

by flytam

Related Servers

Alternatives to Crypto Exchange SDK Documentation MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables interaction with OKX cryptocurrency exchange through account management, trading operations (place/cancel orders, close positions), and market data retrieval with support for both production and demo trading modes.
      11
      52 PyPI
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with access to Gate.io's cryptocurrency exchange for market data, trading, and account management, plus DEX, news, and research tools via multiple MCP endpoints.
      38
      MIT
    • 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
    • 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.
      36 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides tools to query OKX cryptocurrency exchange data including instruments, tickers, candles, funding rates, and mark prices via MCP.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time cryptocurrency market data from Binance API, including price queries, 24h statistics, K-line data, market trend analysis, and order book depth information for trading analysis.
      7 npm
      1
      MIT

    TDQS

    A4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool is clearly scoped to a specific exchange and operation: '_methods' lists available methods while '_method_detail' provides details for a selected method. Exchange names in the tool names eliminate any possible overlap or confusion.

    Naming Consistency5/5

    All tool names follow a predictable pattern: {exchange}_methods and {exchange}_method_detail. The naming is uniformly lowercase snake_case, and even the okx_dex_api variant still follows the same structural convention.

    Tool Count5/5

    With 12 tools covering 6 exchanges (2 per exchange), the count is well-scoped for a documentation server. Each tool has a distinct role, and the count is neither bloated nor thin.

    Completeness5/5

    The tool set fully covers its documentation purpose: for every supported exchange, you can retrieve a full method list and then drill into detailed documentation for any specific method. No obvious missing operations or dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues