Skip to main content
Glama
enesjakozh
esshka

OKX MCP Server

by esshka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

OKX MCP 서버

OKX 거래소에서 실시간 암호화폐 가격 데이터를 제공하는 모델 컨텍스트 프로토콜 서버입니다.

특징

이 MCP 서버는 OKX API에 연결하여 간단한 도구 인터페이스를 통해 암호화폐 가격 정보를 제공합니다. OKX API를 통한 포괄적인 오류 처리, 요청 로깅 및 속도 제한 기능을 포함합니다.

도구

get_candlesticks

OKX의 모든 악기에 대한 과거 캔들스틱(OHLCV) 데이터를 검색합니다.

  • 입력 :

    • instrument : 문자열(필수) - 악기 ID(예: "BTC-USDT")

    • bar : 문자열(선택 사항) - 시간 간격(예: "1m", "5m", "1H", "1D"), 기본값은 "1m"입니다.

    • limit : Number (선택 사항) - 반환할 캔들스틱 수(최대 100개), 기본값 100개

  • 출력 : JSON 객체 배열, 각각 포함:

    • timestamp : 캔들스틱의 ISO 타임스탬프

    • open : 시작가

    • high : 가장 높은 가격

    • low : 가장 낮은 가격

    • close : 종가

    • volume : 거래량

    • volumeCurrency : 통화로 환산한 볼륨

사용 예:

지엑스피1

get_price

OKX에 상장된 모든 상품의 최신 가격과 24시간 시장 데이터를 가져옵니다.

  • 입력 :

    • instrument : 문자열(필수) - 악기 ID(예: "BTC-USDT")

  • 출력 : 다음을 포함하는 JSON 객체:

    • instrument : 요청된 악기 ID

    • lastPrice : 최신 거래 가격

    • bid : 현재 최고 입찰가

    • ask : 현재 가장 좋은 매도 가격

    • high24h : 24시간 최고가

    • low24h : 24시간 저렴한 가격

    • volume24h : 24시간 거래량

    • timestamp : 데이터의 ISO 타임스탬프

사용 예:

{
  "instrument": "BTC-USDT",
  "lastPrice": "65432.1",
  "bid": "65432.0",
  "ask": "65432.2",
  "high24h": "66000.0",
  "low24h": "64000.0",
  "volume24h": "1234.56",
  "timestamp": "2024-03-07T17:22:28.000Z"
}

Related MCP server: OKX MCP Server

개발

종속성 설치:

npm install

서버를 빌드하세요:

npm run build

자동 재빌드를 사용한 개발의 경우:

npm run watch

설치

Claude Desktop 또는 VSCode와 함께 사용하려면 MCP 설정에 서버 구성을 추가하세요.

macOS(VSCode):

~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

macOS(클로드 데스크톱):

~/Library/Application Support/Claude/claude_desktop_config.json

윈도우(VSCode):

%APPDATA%/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

Windows(Claude Desktop):

%APPDATA%/Claude/claude_desktop_config.json

구성:

{
  "mcpServers": {
    "okx": {
      "command": "node",
      "args": ["/path/to/okx-mcp-server/build/index.js"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

오류 처리

서버는 포괄적인 오류 처리를 구현합니다.

  • 네트워크 오류는 캡처되어 컨텍스트와 함께 반환됩니다.

  • 잘못된 기기 ID는 적절한 오류 메시지를 반환합니다.

  • API 속도 제한은 Axios 시간 초과 구성을 통해 준수됩니다.

  • 모든 오류는 디버깅 목적으로 기록됩니다.

Available Tools

2 tools
get_candlesticksC

Get candlestick data for an OKX instrument

ParametersJSON Schema
NameRequiredDescriptionDefault
instrumentYesInstrument ID (e.g. BTC-USDT)
barNoTime interval (e.g. 1m, 5m, 1H, 1D)1m
limitNoNumber of candlesticks (max 100)

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states what the tool does without mentioning rate limits, authentication needs, response format, or pagination behavior. It doesn't explain what 'candlestick data' includes (e.g., OHLC values) or any constraints beyond the implied data retrieval.

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, efficient sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded and appropriately sized for a simple data retrieval tool, with every word contributing to clarity.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete for a tool with three parameters. It doesn't cover behavioral aspects like response format, error handling, or usage context, leaving significant gaps for an AI agent to understand how to effectively invoke and interpret results.

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?

Schema description coverage is 100%, so the schema fully documents all three parameters. The description adds no additional meaning beyond the schema, such as explaining the significance of candlestick intervals or instrument IDs in context. This meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the verb ('Get') and resource ('candlestick data for an OKX instrument'), making the purpose immediately understandable. However, it doesn't differentiate from the sibling tool 'get_price', which likely provides different market data, leaving room for improvement in distinguishing between similar data retrieval functions.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus the sibling 'get_price' or any alternatives. It lacks context about when candlestick data is appropriate (e.g., for charting, technical analysis) versus price data, offering no usage boundaries or prerequisites.

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

get_priceC

Get latest price for an OKX instrument

ParametersJSON Schema
NameRequiredDescriptionDefault
instrumentYesInstrument ID (e.g. BTC-USDT)

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but lacks details on traits like rate limits, authentication needs, error handling, or response format. This is a significant gap for a tool with no annotation coverage.

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, efficient sentence with zero waste. It is appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain behavioral traits, return values, or usage context, which are essential for a tool that fetches financial data. This leaves clear gaps in understanding.

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?

Schema description coverage is 100%, so the schema already documents the 'instrument' parameter. The description adds no additional meaning beyond what the schema provides, such as examples or constraints, meeting the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the verb 'Get' and resource 'latest price for an OKX instrument', making the purpose specific and understandable. It doesn't explicitly distinguish from the sibling 'get_candlesticks', which provides historical price data, so it misses full differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get_candlesticks'. There is no mention of prerequisites, context, or exclusions, leaving usage unclear.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv1.0.0
    • Addedget_candlesticks
    • Addedget_price
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0

Scored across 2 tools

Disambiguation4/5

The two tools have distinct purposes: get_candlesticks retrieves historical price data in candlestick format, while get_price fetches the latest price. There is minimal overlap as they target different data types (historical vs. current), though both relate to instrument pricing which could cause slight confusion in some contexts.

Naming Consistency5/5

Both tools follow a consistent verb_noun naming pattern (get_candlesticks, get_price) with clear, descriptive names. The snake_case style is uniform throughout, making the tools easy to identify and predict.

Tool Count2/5

With only 2 tools, the server feels severely under-scoped for a financial trading platform like OKX. This minimal set lacks essential operations such as placing orders, managing accounts, or accessing market depth, which are core to trading workflows.

Completeness2/5

The tool surface is highly incomplete for an OKX server, covering only price data retrieval. There are significant gaps in trading functionality (e.g., no create_order, cancel_order), account management, or market data beyond basic prices, which will likely cause agent failures in typical trading scenarios.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Bybit MCP Server

    sammcj
    A
    license
    B
    quality
    F
    maintenance
    A Model Context Protocol server that provides read-only access to Bybit's cryptocurrency exchange API, allowing users to query real-time cryptocurrency data using natural language.
    12
    11
    16
    MIT

  • OKX MCP Server

    badger3000
    A
    license
    B
    quality
    D
    maintenance
    Provides real-time and historical cryptocurrency price data from the OKX exchange, including live WebSocket updates, candlestick charts, and visual price analysis for trading pairs.
    5
    7
    3
    MIT

  • Tastytrade MCP Server

    tnngnc
    F
    license
    B
    quality
    D
    maintenance
    Provides access to Tastytrade historical price data via the Model Context Protocol. It enables users to retrieve historical candle data for specific financial symbols and time intervals.
    1
    -

Appeared in Searches