Upbit MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 the latest ticker data from Upbit |
| get_orderbookC | Get orderbook snapshot for a given symbol |
| get_tradesC | Get recent trade ticks for a symbol |
| get_accountsB | |
| create_orderA | |
| get_ordersA | |
| get_orderC | |
| cancel_orderC | |
| get_market_summaryB | |
| get_deposits_withdrawalsB | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| explain_ticker | Create a prompt explaining ticker data |
| analyze_portfolio | 사용자의 포트폴리오를 분석하는 프롬프트를 생성합니다. |
| order_help | 주문 생성에 대한 도움말 프롬프트를 생성합니다. |
| trading_strategy | 트레이딩 전략 수립을 위한 프롬프트를 생성합니다. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| market://list |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the Upbit cryptocurrency exchange domain. For example, create_order, cancel_order, get_order, and get_orders handle different aspects of order management without overlap, while get_accounts, get_deposits_withdrawals, get_market_summary, get_orderbook, get_ticker, and get_trades each focus on unique data retrieval functions. No tools appear to do the same thing, making selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern using snake_case, such as get_accounts, create_order, and cancel_order. This predictable naming convention enhances readability and usability, with no deviations or mixed styles observed across the toolset. The consistency supports easy identification and reduces cognitive load for agents.
With 10 tools, the server is well-scoped for its purpose of interacting with the Upbit cryptocurrency exchange. Each tool earns its place by covering essential operations like account management, order handling, and market data retrieval. This count aligns with typical server sizes (3-15 tools) and avoids being too thin or heavy, providing comprehensive functionality without unnecessary complexity.
The tool surface offers near-complete coverage for the cryptocurrency exchange domain, including CRUD operations for orders (create, get, cancel, list), account and transaction management, and market data access. Minor gaps exist, such as the lack of tools for modifying orders or handling advanced trading features like stop-loss orders, but agents can work around these with the available tools. Overall, the set supports core workflows effectively.