Skip to main content
Glama
IQAIcom

Upbit MCP Server

by IQAIcom

LIST_DEPOSIT_ADDRESSES

Retrieve deposit addresses for all currencies on Upbit. Requires private API authentication.

Instructions

List deposit addresses for all currencies (requires private API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool definition including the 'execute' handler that calls the Upbit API /deposits/coin_addresses endpoint
    export const listDepositAddressesTool = {
    	name: "LIST_DEPOSIT_ADDRESSES",
    	description:
    		"List deposit addresses for all currencies (requires private API)",
    	parameters: z.object({}),
    	execute: async () => {
    		ensurePrivateEnabled();
    		const baseURL = `${config.upbit.baseUrl}${config.upbit.apiBasePath}`;
    		const client = createHttpClient(baseURL);
    		const token = signJwtToken();
    		const data = await fetchJson<unknown>(client, "/deposits/coin_addresses", {
    			headers: { Authorization: `Bearer ${token}` },
    		});
    		return JSON.stringify(data, null, 2);
    	},
    } as const;
  • Input parameter schema - empty object (z.object({})), meaning no parameters required
    parameters: z.object({}),
  • src/index.ts:18-47 (registration)
    Import of the tool on line 18 and registration via server.addTool on line 47
    import { listDepositAddressesTool } from "./tools/list-deposit-addresses.js";
    import { listDepositsTool } from "./tools/list-deposits.js";
    import { listWithdrawalAddressesTool } from "./tools/list-withdrawal-addresses.js";
    import { listWithdrawalsTool } from "./tools/list-withdrawals.js";
    
    async function main() {
    	console.log("Initializing Upbit MCP Server...");
    
    	const server = new FastMCP({
    		name: "Upbit MCP Server",
    		version: "0.0.1",
    	});
    
    	server.addTool(getTickerTool);
    	server.addTool(getOrderbookTool);
    	server.addTool(getTradesTool);
    	server.addTool(getAccountsTool);
    	server.addTool(createOrderTool);
    	server.addTool(getOrdersTool);
    	server.addTool(getOrderTool);
    	server.addTool(cancelOrderTool);
    	server.addTool(listWithdrawalAddressesTool);
    	server.addTool(createWithdrawalTool);
    	server.addTool(getWithdrawalTool);
    	server.addTool(listWithdrawalsTool);
    	server.addTool(cancelWithdrawalTool);
    	server.addTool(getDepositChanceTool);
    	server.addTool(createDepositAddressTool);
    	server.addTool(getDepositAddressTool);
    	server.addTool(listDepositAddressesTool);
  • ensurePrivateEnabled() helper used to check private API access before executing the tool
    export function ensurePrivateEnabled(): void {
    	if (!config.upbit.enablePrivate) {
    		throw new Error(
    			"Private trading tools are disabled. Set UPBIT_ENABLE_TRADING=true to enable.",
    		);
    	}
    	if (!config.upbit.accessKey || !config.upbit.secretKey) {
    		throw new Error(
    			"Upbit API keys are not configured. Set UPBIT_ACCESS_KEY and UPBIT_SECRET_KEY.",
    		);
    	}
    }
    
    export function signJwtToken(
    	params?: Record<string, string | number | boolean | undefined>,
    ): string {
    	const payload: Record<string, unknown> = {
    		access_key: config.upbit.accessKey,
    		nonce: crypto.randomUUID(),
    	};
    
    	if (params && Object.keys(params).length > 0) {
    		const searchParams = new URLSearchParams();
    		const sortedKeys = Object.keys(params).sort();
    		for (const key of sortedKeys) {
    			const value = params[key];
    			if (value === undefined) continue;
    			searchParams.append(key, String(value));
    		}
    		const encoded = searchParams.toString();
    		const queryHash = crypto.createHash("sha512").update(encoded).digest("hex");
    		payload.query_hash = queryHash;
    		payload.query_hash_alg = "SHA512";
    	}
    
    	return jwt.sign(payload, config.upbit.secretKey as string);
    }
  • signJwtToken() helper used to generate authentication JWT for the Upbit API call
    export function signJwtToken(
    	params?: Record<string, string | number | boolean | undefined>,
    ): string {
    	const payload: Record<string, unknown> = {
    		access_key: config.upbit.accessKey,
    		nonce: crypto.randomUUID(),
    	};
    
    	if (params && Object.keys(params).length > 0) {
    		const searchParams = new URLSearchParams();
    		const sortedKeys = Object.keys(params).sort();
    		for (const key of sortedKeys) {
    			const value = params[key];
    			if (value === undefined) continue;
    			searchParams.append(key, String(value));
    		}
    		const encoded = searchParams.toString();
    		const queryHash = crypto.createHash("sha512").update(encoded).digest("hex");
    		payload.query_hash = queryHash;
    		payload.query_hash_alg = "SHA512";
    	}
    
    	return jwt.sign(payload, config.upbit.secretKey as string);
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It only states it lists addresses and requires private API, without disclosing behaviors like whether it returns active/inactive addresses, rate limits, or error scenarios. Minimal disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, front-loaded with the action and resource. No wasted words; every part serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and no output schema, the description provides the essential context but lacks details on return format, pagination, or edge cases. Adequate but not enriched.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters and 100% schema coverage (trivially). The description adds no parameter information because none exist. Baseline 3 applies as per guidelines for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists deposit addresses for all currencies, with a specific verb ('List') and resource ('deposit addresses'). It distinguishes from siblings like GET_DEPOSIT_ADDRESS (singular) and LIST_DEPOSITS (deposits, not addresses).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions 'requires private API' indicating authentication need, but does not explicitly explain when to use this tool versus alternatives like GET_DEPOSIT_ADDRESS. Usage context is implied but not elaborated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IQAIcom/mcp-upbit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server