Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Okx

NPM · @PIPEWORX/MCP-OKX · 2 COMPONENTS

OKX v5 public MCP.

+3 this week 81 Trust /100

Last scanned (13 hours ago)

Scores higher than 69% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-okx). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1493 tokens (~87/item across 17 items; 17 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 23% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 −13
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: fail → unverified ▼ functional
    • Stability: unverified → 0.17 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 78

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-okx@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-okx
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-okx/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3679684878
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:aee66247f1e90346ff34afd16bc9b55eb1f71d5a61e8233c06c6cb7a04c40dc814bc255396c4f4692016af369518a94b334fac5eaaeca5fd1d79978d0

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 17 exposed · ~1,441 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
candles ~79

OKX crypto exchange OHLC candles for a spot/perp/futures instrument. Bars 1m through 1M. Use for charting and backtesting OKX instruments.

NameTypeReqDescription
afterstring––
barstring––
beforestring––
instIdstringyes–
limitnumber––

No output schema declared.

No examples provided.

funding_rate ~52

OKX crypto exchange current perpetual swap funding rate for a SWAP instrument (e.g. 'BTC-USDT-SWAP'): funding rate, next settlement time, and method.

NameTypeReqDescription
instIdstringyes–

No output schema declared.

No examples provided.

funding_rate_history ~83

OKX crypto exchange historical perpetual swap funding rates for a SWAP instrument (e.g. 'BTC-USDT-SWAP'). Optional before/after (ms epoch) cursors and limit. Use for funding cost analysis.

NameTypeReqDescription
afterstring––
beforestring––
instIdstringyes–
limitnumber––

No output schema declared.

No examples provided.

index_tickers ~64

OKX crypto exchange index tickers — current index price and 24h change for OKX index instruments. Filter by quote currency (e.g. 'USD') or specific instId.

NameTypeReqDescription
instIdstring––
quoteCcystring––

No output schema declared.

No examples provided.

instruments ~85

OKX crypto exchange — list instruments by type: 'SPOT', 'MARGIN', 'SWAP', 'FUTURES', or 'OPTION'. Returns instrument IDs, tick sizes, lot sizes, and trading rules for each.

NameTypeReqDescription
instFamilystring––
instIdstring––
instTypestringyes–
ulystring––

No output schema declared.

No examples provided.

long_short_ratio ~139

Long/short account ratio for a crypto perpetual contract on the OKX venue — the ratio of accounts holding longs to accounts holding shorts, bucketed by period. A value above 1 means more accounts sit long. Use for positioning and crowd-sentiment reads on a perp.

NameTypeReqDescription
bucketsnumber–Recent buckets to return. Default 24, max 100.
instIdstringyes–
periodstring–5m, 15m, 30m, 1H, 2H, 4H, 6H, 12H or 1D. Default 5m.

No output schema declared.

No examples provided.

mark_price ~73

OKX crypto exchange mark price for derivatives: pass instType (e.g. 'SWAP') and optionally uly or instId. Returns the mark price used for unrealised P&L and liquidation calculations.

NameTypeReqDescription
instIdstring––
instTypestringyes–
ulystring––

No output schema declared.

No examples provided.

market_24hr ~54

OKX crypto exchange 24-hour rolling stats for an instrument: open, high, low, last, volume, vol-ccy. Use for daily summary on OKX.

NameTypeReqDescription
instIdstringyes–

No output schema declared.

No examples provided.

open_interest ~96

Open interest for a crypto perpetual swap or dated futures contract on the OKX venue — contracts outstanding, coin-denominated size and USD notional, with timestamp. Accepts 'MASKUSDT', 'MASK' or 'MASK-USDT-SWAP'. Use to size how much leverage is riding on a perp.

NameTypeReqDescription
instIdstringyes–
instTypestring–SWAP (default), FUTURES or OPTION.

No output schema declared.

No examples provided.

order_book ~56

OKX crypto exchange order book (bids + asks) for a spot/perp/futures instrument. Use for live depth-of-book on OKX-listed instruments.

NameTypeReqDescription
instIdstringyes–
sznumber––

No output schema declared.

No examples provided.

perp_metrics ~236

Crypto perpetual futures snapshot in one call: funding rate, open interest, taker buy/sell volume (CVD) and long/short account ratio for a perpetual swap. Accepts exchange-style symbols such as 'MASKUSDT', 'MASK' or 'MASK-USDT-SWAP'. Figures come from the OKX venue and the response states that venue, so a symbol quoted on Binance or Bybit is answered with OKX's own contract for that coin, labelled as such.

NameTypeReqDescription
bucketsnumber–How many recent buckets of taker flow to sum for CVD. Default 24, max 100.
instIdstringyesPerpetual symbol — 'MASKUSDT', 'MASK', 'MASK-USDT' and 'MASK-USDT-SWAP' all resolve to the same OKX contract.
periodstring–Bucket size for taker flow and long/short ratio: 5m, 15m, 30m, 1H, 2H, 4H, 6H, 12H, 1D. Default 5m.

No output schema declared.

No examples provided.

status ~26

OKX exchange system status — current operational state and any scheduled or ongoing maintenance windows affecting trading.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

taker_volume ~166

Taker buy versus taker sell volume for a crypto perpetual contract on the OKX venue, bucketed by period. Returns the per-bucket series, the buy/sell ratio and cumulative volume delta (CVD) across the window — the aggressor-flow input for order-flow and CVD analysis.

NameTypeReqDescription
bucketsnumber–Recent buckets to return and sum. Default 24, max 100.
instIdstringyes–
periodstring–5m, 15m, 30m, 1H, 2H, 4H, 6H, 12H or 1D. Default 5m.
unitstring–'0' for contracts (default), '1' for coin.

No output schema declared.

No examples provided.

ticker ~64

OKX crypto exchange — single instrument ticker (e.g. "BTC-USDT", "BTC-USD-SWAP"). Returns bid/ask, last, 24h vol/change. Use for current pricing of an OKX-listed instrument.

NameTypeReqDescription
instIdstringyes–

No output schema declared.

No examples provided.

tickers ~89

OKX crypto exchange — bulk tickers by instrument type ("SPOT", "MARGIN", "SWAP", "FUTURES", "OPTION"). Use to enumerate all spot or all perp instruments. NOT a general stock-ticker search — use polygon-io/tickers for that.

NameTypeReqDescription
instFamilystring––
instTypestringyes–
ulystring––

No output schema declared.

No examples provided.

time ~27

OKX exchange server time in Unix milliseconds. Use to synchronise request timestamps or verify API connectivity.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

trades ~52

OKX crypto exchange recent trade tape for an instrument. Returns price, size, side, timestamp. Use for tick-level execution analysis on OKX.

NameTypeReqDescription
instIdstringyes–
limitnumber––

No output schema declared.

No examples provided.

Install

How do I install the Okx MCP server?

Okx runs locally as an npm package, launched with npx -y @pipeworx/mcp-okx. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-okx

# add to Claude Code
claude mcp add pipeworx-io-okx -- npx -y @pipeworx/mcp-okx
Common questions

What is the Okx MCP server?

Okx is an MCP server listed in the public MCP registry as io.github.pipeworx-io/okx. OKX v5 public MCP. This page covers its npm package (@pipeworx/mcp-okx).

Is the Okx MCP server safe to use?

Okx scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Okx MCP server expose?

Okx exposes 17 tools: instruments, ticker, tickers, order_book, candles, and 12 more. Their descriptions and schemas cost roughly 1,441 tokens of context every time the server is loaded.

Is the Okx MCP server still maintained?

Okx is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Okx MCP server under?

Okx declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Okx MCP server?

VerifyMCP ran 16 checks on Okx, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.