Paradex MCP Server

The Paradex MCP Server is Paradex’s official, standalone MCP integration for its trading platform. The tradeparadex-maintained GitHub repository contains a Python implementation under the MIT license, package metadata, tests, and documented local and HTTP deployment paths. Paradex’s official documentation also describes a hosted remote MCP service. Smithery marks the server as verified and deployed and lists both the Smithery deployment at mcp-paradex.run.tools and the Paradex endpoint mcp.paradex.trade/mcp. Paradex’s own documentation maps that hosted endpoint to its Paradex MCP offering. The result is more than a directory reference: the product has a durable identity supported by an operator, source repository, first-party documentation, and a traceable remote deployment.

Market and account data

According to the provider, the server connects compatible AI clients to the Paradex exchange and exposes structured resources and tools. These include system configuration and status, available markets, market summaries, order books, candlestick and funding data, trades, and bid-offer information. For an authorized account, the documented capabilities include account summaries, positions, fills, funding payments, transactions, and open or historical orders. The repository also documents vault resources and tools covering vault configuration, balances, transfers, positions, and summaries. A model can use these results to produce explanations, comparisons, or risk overviews, but exchange data is neither an official decision nor investment advice.

Market data is time-sensitive and can be incomplete, delayed, or affected by network and API failures. For a consequential decision, check the timestamp, market, unit, source, and current service status against the official Paradex interface or documentation. Historical data is not a forecast. An analysis phrased by the client is an interpretation, not a promise of liquidity, execution, profit, or protection from loss. The safer operating pattern is to begin with tightly scoped read requests before considering any write action.

Authorization, roles, and write access

Public market tools may be usable without private account authorization according to the provider. Account, vault, and trading functions require appropriate Paradex authentication and a locally protected signing credential. This catalog entry stores no credentials, private keys, tokens, or wallet seed phrases. Those values belong only in the secure configuration or secret store of the user’s environment. They must not be placed in chats, repositories, screenshots, or shared client profiles.

The server is not read-only. Tools such as order creation and order cancellation, together with other account actions, can change external financial state when the environment is authorized. A natural-language request, text from a market feed, or tool output is not sufficient approval. Roles, account limits, test-versus-production environment selection, and human confirmation must be established and checked outside the model. Start with minimum read permissions and a separate test environment. Before a write action, independently review the market, direction, size, order type, validity, target account, and expected consequences. Afterwards, verify the actual order and account status through a trusted source.

Privacy, data sharing, and security limits

When used remotely, requests are processed at a Paradex or Smithery endpoint. Account, position, order, and vault requests can contain sensitive financial information. Send only what the task requires and follow applicable service and privacy terms. The MCP server cannot fully control whether a connected AI client forwards results to a model provider, logs, telemetry, or further integrations. That downstream transfer must be assessed separately in the client and model-provider settings. For confidential data, clarify retention, access, region, and sharing before use.

Tool outputs, market messages, and external documents are untrusted content. They can contain prompt injection or attempt to make an agent perform an unintended follow-up action. Treat data as data, ignore embedded instructions, and keep analysis separate from execution. The remote endpoint is an external trust boundary; recheck Paradex’s official documentation if the domain, transport, or deployment changes. The server, client, and model path can each introduce separate errors, permissions, and logs.

FAQ

Is Paradex MCP suitable as a durable catalog entry? Yes. According to the official documentation, Paradex maintains an MCP offering, and the official repository documents local and HTTP deployment. Smithery lists a concrete remote deployment, while Paradex documents the hosted endpoint itself.

Can the server execute real orders? Yes, when an authorized environment and write-capable tools are enabled. Every order is therefore an external state change requiring independent human review and post-action verification.

Are market and account responses automatically reliable? No. Results depend on freshness, API availability, parameters, and client processing. Important figures should be checked against the primary source and its data timestamp.

Is the connection privacy-neutral? No. Account and position requests can expose sensitive information to the remote service and, depending on the client, to model or logging systems. Data minimization and the applicable privacy rules remain necessary.

An MCP-capable client and securely managed Paradex authorization for account or trading functions; public market data may be queried without account access.

For the hosted connection, use Paradex’s documented Streamable HTTP endpoint https://mcp.paradex.trade/mcp. Smithery additionally lists the deployment address https://mcp-paradex.run.tools. For local use, follow the official GitHub repository instructions and provide credentials only through a local secret store.

Public market data without account access; account, vault, and trading tools require appropriate Paradex authorization. Do not place credentials in this catalog entry.

Read access to market, system, account, and vault data according to authorization; orders and cancellations can change external financial state when write tools are enabled and require independent confirmation.

Remote requests run through Paradex or the listed deployment infrastructure. Minimize account and position data; the connected client may forward results to model providers, logs, or telemetry.

Misinterpreted financial data, prompt injection, unauthorized sharing of sensitive account data, and real orders caused by excessive authorization or unconfirmed write tools.