Cspr Trade MCP

What make-software/cspr-trade-mcp MCP server does

The make-software/cspr-trade-mcp MCP server exposes CSPR.trade capabilities to MCP-compatible agents operating on the Casper Network. It covers read-only market and account information, transaction construction for swaps and liquidity operations, and analysis that can help an agent evaluate a trade before submitting it.

The hosted service is available at https://mcp.cspr.trade/mcp. It provides 24 public tools according to the README. Market and analysis operations do not require a wallet. Swap, token approval, and liquidity transaction-building operations are marked as requiring one, but the public service does not receive private keys.

How it works

A typical workflow can retrieve token and pair data, request a quote, inspect price impact or slippage, build a transaction, sign it locally, and submit the signed transaction. The remote service constructs deploys and transaction payloads; signing remains on the user's machine when the optional local signer is enabled.

The separate signer instance runs in --signer mode and provides sign_deploy. It loads keys from the local machine and is intended for local-only deploy signing. The hosted endpoint does not support file-based deploy input: submit_transaction accepts inline signed JSON and cannot read deploy files from its own filesystem.

Setup and configuration

The simplest setup uses the public MCP URL:

{
  "mcpServers": {
    "cspr-trade": {
      "url": "https://mcp.cspr.trade/mcp"
    }
  }
}

This configuration is documented for Claude Desktop, Cursor, and other MCP clients. No local installation is needed for the hosted endpoint.

For self-hosting, install the npm package @make-software/cspr-trade-mcp and run it through npx. The README shows CSPR_TRADE_NETWORK set to testnet for testnet access. Self-hosting documentation also covers HTTP server setup, local signer mode, production deployment, and an optional file-path workflow.

Tools and capabilities

The make-software/cspr-trade-mcp MCP server organizes its public tools into these groups:

• Market data: token, currency, pair, pair-detail, quote, and token or pair price-history queries.
• Trading: swap construction, token-approval construction, and signed-transaction submission.
• Liquidity: add-liquidity and remove-liquidity transaction construction.
• Trade analysis: price-impact, slippage, trade, and optimal-liquidity-amount estimates.
• Account data: token balances, liquidity positions, impermanent loss, swap history, portfolio value, and position status.

The optional local signer contributes sign_deploy. The related SDK package contains TypeScript functionality for market data, price history, quotes, analysis, and transaction building, but it is distinct from the MCP server package.

Limitations and notes

The service is specific to CSPR.trade and the Casper Network. The hosted endpoint is non-custodial by design, but transaction submission still requires the caller to provide an inline signed JSON deploy. Agents that need local key handling must run the signer separately rather than expecting the public endpoint to sign for them.

The README distinguishes public tools from the optional signer tool, so the available surface depends on whether only the hosted server or a local signer is configured. Testnet access and private deployments require self-hosting configuration rather than the default public endpoint.