Aster Finance MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASTER_API_KEY | Yes | Your Aster API key for authentication | |
| ASTER_API_SECRET | Yes | Your Aster API secret key for authentication |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingB | Test connectivity to the Rest API. |
| timeA | Get the current server time. |
| exchangeInfoB | Get current exchange trading rules and symbol information. |
| depthC | Get the order book for a symbol. |
| tradesC | Get recent market trades. |
| historicalTradesC | Get older market historical trades. |
| aggTradesC | Get compressed, aggregate market trades. |
| klinesC | Get Kline/candlestick bars for a symbol. |
| indexPriceKlinesC | Kline/candlestick bars for the index price of a pair. |
| markPriceKlinesC | Kline/candlestick bars for the mark price of a symbol. |
| premiumIndexB | Get Mark Price and Funding Rate. |
| fundingRateC | Get funding rate history. |
| fundingInfoC | Get funding rate config. |
| ticker_24hrC | 24 hour rolling window price change statistics. |
| ticker_priceC | Latest price for a symbol or symbols. |
| ticker_bookTickerB | Best price/qty on the order book for a symbol or symbols. |
| setPositionModeC | Change user's position mode (Hedge Mode or One-way Mode). |
| getPositionModeC | Get user's position mode. |
| setMultiAssetsModeC | Change user's Multi-Assets mode. |
| getMultiAssetsModeB | Get user's Multi-Assets mode. |
| placeOrderD | Send in a new order. |
| placeBatchOrdersC | Place multiple orders. |
| transferAssetC | Transfer between futures and spot. |
| queryOrderC | Check an order's status. |
| cancelOrderC | Cancel an active order. |
| cancelAllOpenOrdersB | Cancel all open orders on a symbol. |
| cancelBatchOrdersC | Cancel multiple orders. |
| countdownCancelAllC | Auto-cancel all open orders. |
| queryOpenOrderC | Query current open order. |
| getAllOpenOrdersC | Get all open orders on a symbol. |
| getAllOrdersC | Get all account orders; active, canceled, or filled. |
| getBalanceB | Get futures account balance. |
| getAccountInfoB | Get current account information. |
| setLeverageC | Change user's initial leverage. |
| setMarginTypeC | Change margin type. |
| modifyPositionMarginC | Modify isolated position margin. |
| getPositionMarginHistoryC | Get position margin change history. |
| getPositionInfoC | Get current position information. |
| getTradeListC | Get trades for a specific account and symbol. |
| getIncomeHistoryD | Get income history. |
| getLeverageBracketsC | Get notional and leverage brackets. |
| getAdlQuantileD | Get Position ADL Quantile Estimation. |
| getForceOrdersC | Get user's force orders. |
| getCommissionRateC | Get user's commission rate. |
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 44 tools
Most tools have distinct purposes, but some overlap exists. For example, 'getAllOpenOrders' and 'queryOpenOrder' could be confused, and 'ticker_24hr', 'ticker_bookTicker', and 'ticker_price' are all price-related but serve different functions. Descriptions help clarify, but the sheer number of tools increases the risk of misselection.
Naming conventions are mixed, with some tools using camelCase (e.g., 'getAccountInfo') and others using snake_case (e.g., 'ticker_24hr'). Verb styles vary, such as 'get', 'set', 'place', and 'modify', but they are generally readable. The inconsistency is noticeable but not chaotic.
With 44 tools, the count is too high for typical MCP server purposes, making it heavy and potentially overwhelming for agents. While the domain (finance/trading) is complex, the tool surface could benefit from consolidation or better scoping to reduce cognitive load.
The tool set provides comprehensive coverage for a trading platform, including order management, account info, market data, and configuration. It supports full CRUD/lifecycle operations (e.g., place, query, cancel orders) and covers various aspects like funding, leverage, and transfers, leaving no obvious gaps.