Skip to main content
Glama
badger3000

OKX MCP Server

by badger3000

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OKX_API_KEYNoYour OKX API key (optional, only needed for authenticated endpoints)
OKX_API_SECRETNoYour OKX API secret (optional, only needed for authenticated endpoints)
OKX_API_PASSPHRASENoYour OKX API passphrase (optional, only needed for authenticated endpoints)

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

NameDescription
get_priceC

Get latest price for an OKX instrument with formatted visualization

get_candlesticksC

Get candlestick data for an OKX instrument with visualization options

subscribe_tickerC

Subscribe to real-time ticker updates for an instrument

get_live_tickerC

Get the latest ticker data from WebSocket subscription

unsubscribe_tickerC

Unsubscribe from real-time ticker updates for an instrument

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 5 tools

Disambiguation4/5

The tools are mostly distinct with clear purposes: get_candlesticks for historical data, get_live_ticker for real-time data, get_price for current price, and subscribe/unsubscribe_ticker for WebSocket management. However, get_live_ticker and get_price could be confused as both provide current price information, though one is WebSocket-based and the other is a simple fetch.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case, such as get_candlesticks, get_live_ticker, and subscribe_ticker. This predictability makes it easy for an agent to understand and use the tools without confusion.

Tool Count5/5

With 5 tools, the server is well-scoped for its purpose of providing OKX market data and real-time updates. Each tool serves a specific function, and there are no redundant or unnecessary additions, making the count appropriate for the domain.

Completeness4/5

The toolset covers core market data operations well, including historical data, real-time updates, and subscription management. A minor gap exists in the lack of tools for order placement or account management, but for a data-focused server, the coverage is sufficient for typical agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues