Bithumb MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITHUMB_API_KEY | Yes | Your Bithumb API key | |
| BITHUMB_SECRET_KEY | Yes | Your Bithumb secret key |
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 |
|---|---|
| get_tickerC | Get cryptocurrency ticker information (Public) |
| get_orderbookC | Get order book information (Public) |
| get_transaction_historyB | Get recent transaction history (Public) |
| get_assets_statusC | Get asset deposit/withdrawal status (Public) |
| get_btciB | Get Bithumb Index (BTMI, BTAI) information (Public) |
| get_candlestickC | Get Candlestick data (Public) |
| post_accountC | Get member account information and fees (Private) |
| get_balanceC | Get account balance (Private) |
| post_wallet_addressC | Get member's coin deposit wallet address (Private) |
| post_ticker_userC | Get member's recent virtual asset transaction information (Private) |
| post_ordersC | Get member's order details (Private) |
| post_order_detailC | Get details of a specific member order (Private) |
| post_user_transactionsC | Get member's transaction completion history (Private) |
| post_placeC | Place a limit order (buy/sell) (Private) |
| post_cancelC | Cancel an order (Private) |
| post_market_buyC | Place a market buy order (Private) |
| post_market_sellC | Place a market sell order (Private) |
| post_withdrawal_coinC | Request a coin withdrawal (Private) |
| post_withdrawal_krwC | Request a KRW withdrawal (Private, Deprecated by Bithumb) |
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 19 tools
Most tools have distinct purposes targeting specific resources like balance, orders, or transactions, but there is some overlap between post_orders and post_order_detail, and post_ticker_user and post_user_transactions could be confused as both relate to member transaction information. Descriptions help clarify, but minor ambiguity exists.
Tools follow a consistent verb_noun pattern with 'get_' for public data and 'post_' for private actions, but the naming is slightly inconsistent as 'post_account' and 'post_place' use generic verbs, while others like 'post_market_buy' are more specific. Overall, the pattern is predictable and readable.
With 19 tools, the count is slightly high but reasonable for a cryptocurrency exchange server covering public data and private trading operations. It includes essential functions like order management, balance checks, and transactions, though it might feel a bit heavy compared to simpler servers.
The tool set provides comprehensive coverage for a cryptocurrency exchange domain, including public market data (e.g., ticker, orderbook), private account management (e.g., balance, wallet), and full order lifecycle (place, cancel, detail). No obvious gaps are present, enabling agents to handle typical trading workflows effectively.