Model Context Protocol moderate risk

CCXT

CCXT MCP Server bridges language models to 20+ cryptocurrency exchanges, enabling real-time market data access and trading via a unified API and the Model Context Protocol.

Connections & Capabilities

Connects To

GitHub

Capabilities

readwrite

Quickstart

Install

npx -y @smithery/cli install @doggybee/mcp-server-ccxt --client claude

Config

{
  "mcpServers": {
    "ccxt": {
      "command": "mcp-server-ccxt"
    }
  }
}

Exposed MCP Tools (9)

safe

list-exchanges

Lists all cryptocurrency exchanges supported by the CCXT library.

Read-only operation with no side effects.

safe

get-ticker

Retrieves the current ticker information for a specified trading pair.

Read-only operation; retrieves market data.

safe

get-orderbook

Fetches the order book for a given trading pair on an exchange.

Read-only operation; retrieves market data.

moderate

account-balance

Retrieves the account balance from a specified cryptocurrency exchange.

Requires API keys, but only retrieves information.

high

place-market-order

Places a market order on a cryptocurrency exchange.

Executes trades with potential financial risk.

high

cancel-order

Cancels an existing order on a cryptocurrency exchange.

Modifies existing orders, potentially impacting trading strategies.

moderate

set-proxy-config

Configures proxy settings for accessing exchanges.

Incorrect proxy settings can expose traffic or introduce vulnerabilities.

moderate

clear-cache

Clears the CCXT cache, potentially impacting performance.

Can affect performance, but not destructive.

safe

set-log-level

Sets the logging level for the server.

Does not affect functionality, only logging verbosity.

Safety Assessment

The CCXT MCP Server is relatively safe for read-only operations using public APIs. However, using private APIs for trading carries significant financial risk and requires careful management of API keys and permissions. Always limit API key permissions and use secure storage practices.

Clear separation of public and private API tools.
API key permissions can be limited on the exchange side.
Proxy configuration available to mask IP address.
Rate limiting and caching mechanisms to prevent abuse.

Requires API keys for private API tools, increasing risk of exposure.
No built-in sandboxing; relies on exchange-level security.
Potential for financial loss through trading if used incorrectly.
Improperly configured proxies can introduce security vulnerabilities.