CSPR[dot]trade MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CSPR_TRADE_PORT | No | HTTP server port. | 3000 |
| CSPR_TRADE_NETWORK | No | Casper network to connect to ('mainnet' or 'testnet'). | mainnet |
| CSPR_TRADE_TRANSPORT | No | Transport mode: 'stdio' or 'http'. | http |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tokensB | List all tradable tokens on CSPR.trade with optional fiat pricing |
| get_pairsC | List trading pairs on CSPR.trade with reserves and pricing data |
| get_pair_detailsB | Get detailed information about a specific trading pair |
| get_quoteA | Get a swap quote for trading between two tokens. Returns amounts, price impact, and routing path. |
| get_currenciesA | List supported fiat currencies for price display |
| build_swapA | Build an unsigned swap transaction. Returns the deploy JSON for external signing, plus a human-readable summary. |
| build_approve_tokenA | Build an unsigned token approval transaction. Spender defaults to the CSPR.trade router. |
| submit_transactionA | Submit a signed transaction to the Casper network via node RPC. |
| build_add_liquidityB | Build an unsigned add-liquidity transaction for a token pair |
| build_remove_liquidityC | Build an unsigned remove-liquidity transaction |
| get_liquidity_positionsC | Get liquidity positions for an account |
| get_impermanent_lossC | Calculate impermanent loss for a liquidity position |
| get_swap_historyC | Get swap transaction history |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose with no overlap: transaction-building tools (build_*), data retrieval tools (get_*), and a submission tool (submit_transaction). The descriptions clearly differentiate between constructing transactions, fetching information, and submitting signed transactions.
Tool names follow a highly consistent verb_noun pattern throughout: all start with either 'build_' or 'get_' except 'submit_transaction', which still follows the same convention. This predictability makes it easy for agents to understand the action each tool performs.
With 13 tools, the count is well-scoped for a DeFi trading platform, covering core operations like swapping, liquidity management, data queries, and transaction submission. Each tool earns its place without redundancy or obvious omissions.
The toolset provides complete coverage for the DeFi trading domain: it supports full swap and liquidity workflows (quote, build, submit), comprehensive data access (tokens, pairs, history, positions), and utility functions (impermanent loss, currencies). No significant gaps are apparent for typical agent tasks.