Fast MCP server for interacting with Upbit (public market data and optional private trading tools).
Mixed quality across 19 tools. All tools have names and descriptions, but schema completeness varies significantly. Read-only public tools (GET_TICKER, GET_ORDERBOOK, GET_TRADES) have minimal but correct schemas. Private/write tools (CREATE_ORDER, CREATE_WITHDRAWAL, CREATE_DEPOSIT_ADDRESS) have more complete parameter definitions with enums and constraints. Output schemas are not documented for any tool. Descriptions are brief (10-150 chars typically) and lack context about prerequisites, return types, and when to use each tool versus alternatives. Parameter descriptions are often missing entirely for optional fields. No examples of error handling guidance visible in tool definitions. Security-sensitive operations (private API calls) are present but lack explicit permission warnings in descriptions.
Cancel an existing Upbit order (requires private API)
Cancel a digital asset withdrawal by UUID (requires private API)
Request creation of a deposit address (requires private API)
Create an Upbit order (requires private API)
Request a digital asset withdrawal (requires private API)
Get Upbit account balances (requires private API enabled)
Get a single deposit by UUID (requires private API)
Output schemas not documented. No tool specifies what fields are returned, their types, or structure. LLMs cannot plan downstream operations or extract required data.
LIST_* tools lack pagination parameters. LIST_WITHDRAWALS, LIST_DEPOSITS, LIST_WITHDRAWAL_ADDRESSES, LIST_DEPOSIT_ADDRESSES have no limit, page/offset, or cursor parameters. Large result sets will blow context windows.
Private API tools (CREATE_ORDER, CREATE_WITHDRAWAL, etc.) lack explicit permission warnings. Descriptions say 'requires private API' but don't explain that UPBIT_ENABLE_TRADING=true and keys must be configured, or what happens if they're not.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 0 | 2026-07-28+ | v2 |
| 2026-03-09 | D | 58 | - | v1 |
Get a single deposit address for a currency and net_type (private)
Get deposit availability information for a currency (private)
Get a single Upbit order (requires private API)
Get orderbook snapshot for a given market
List Upbit orders (requires private API)
Get the latest ticker data from Upbit for a single market
Get recent trades for a market
Get a single withdrawal by UUID (requires private API)
List deposits (requires private API)
List deposit addresses (requires private API)
List withdrawals (requires private API)
List withdrawal addresses (requires private API)
No error recovery guidance in any tool description. If a tool fails, LLM has no hint about what to try next (retry? alternative tool? ask user?).
Optional parameters lack descriptions. GET_ORDERS (page, limit, market, state), GET_DEPOSIT_CHANCE (net_type), and others have undocumented optional fields. LLMs cannot know what they control.
Destructive operations (CANCEL_ORDER, CANCEL_WITHDRAWAL, CREATE_WITHDRAWAL) lack confirmation or dry-run support. No pattern to prevent accidental execution.
GET_ACCOUNTS returns unspecified structure. No documentation of account object fields, balance types, or formats (string vs number for amounts).
Enum values in CREATE_ORDER (ord_type, time_in_force, smp_type) lack descriptions. What does 'ioc' mean vs 'fok'? What is 'reduce' smp_type?