upbit-mcp-server

Provides an MCP server exposing Upbit trading and market/technical-analysis functionality as callable tools (account queries, buy/sell orders, order management, market summaries/trends, candle data, and several technical indicators like MA/MACD/Bollinger/RSI/OBV).

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ Automation mcp upbit trading technical-analysis indicators orders go

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Uses API access/secret keys provided via environment variables (better than hardcoding). However, the excerpt lacks details on TLS requirements, least-privilege/scopes, protection against logging secrets, and dependency/security posture (license is null and repo health indicators are limited in the provided data).

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want an agent to call structured MCP tools for Upbit data retrieval and order actions, and you can supply API keys via environment variables.

Avoid When

You need clearly documented rate limits, standardized error contracts, pagination behavior, and explicit retry/idempotency guidance for trading operations.

Use Cases

• Agent-driven access to Upbit account/order workflows via MCP
• Automated retrieval of market data and technical indicators for analysis/trading assistance
• Trading bots or research assistants that need indicator data and order execution through tool calls

Not For

• Use as a production trading safety layer without additional guardrails (risk checks, validation, idempotency, and confirmations)
• Environments where strong operational documentation (tool schemas, error codes, rate limits, pagination) is required
• Use cases needing REST/GraphQL/gRPC access directly (this is primarily MCP-focused)

Interface

REST API

GraphQL

gRPC

MCP Server

SDK

Webhooks

Authentication

Methods: API key / secret key via environment variables (UPBIT_ACCESS_KEY, UPBIT_SECRET_KEY)

OAuth: No Scopes: No

Auth method details (scope granularity, least-privilege, rotation guidance) are not described in the provided README excerpt.

Pricing

Free tier: No

Requires CC: No

No pricing information provided.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Trading operations (PlaceBuyOrder/PlaceSellOrder/CancelOrder) can have side effects; without documented idempotency or safety checks, agents may duplicate actions on retries.
⚠ No explicit schema details are provided for tool inputs/outputs, so the agent may need to infer parameters or rely on MCP runtime tool definitions.
⚠ Rate limits, backoff strategy, and error codes are not documented in the provided excerpt.

Alternatives

Use the Upbit REST API directly (with your own tool wrapper) Build a thin MCP wrapper around a maintained Upbit SDK/client Use a dedicated trading/bot framework with built-in Upbit integration

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for upbit-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.