ClawHub

OKX MCP Skill

v1.0.1

Use OKX OnchainOS MCP through UXC for token discovery, market data, wallet balance, and swap execution planning. Use when tasks need OKX MCP tools such as to...

⭐ 0· 420·2 current·2 all-time
by@jolestar
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The skill's name/description (OKX MCP via UXC) matches the instructions (calls to web3.okx.com via uxc/okx-mcp-cli). However the metadata declares no required binaries or env vars while the runtime instructions explicitly require the 'uxc' CLI, a linked 'okx-mcp-cli', network access to https://web3.okx.com/api/v1/onchainos-mcp, and an OKX API key. That mismatch (declared nothing vs. instructions needing tools/keys) is incoherent.
!
Instruction Scope
SKILL.md instructs the agent to run commands (uxc, okx-mcp-cli) and to configure credentials using either an env var (OKX_ACCESS_KEY) or an operator secret path (op://Engineering/okx/OK-ACCESS-KEY). Those instructions access environment/secret sources that are not declared in metadata. The docs also embed a literal demo API key for read-only trials — useful for testing but increases risk if users copy it unintentionally into production credentials.
✓
Install Mechanism
This is an instruction-only skill with no install spec; nothing is downloaded or written by the skill itself. The included scripts/validate.sh are repo-validation helpers and not part of runtime installation, so install risk is low.
!
Credentials
Requesting an OKX API key is appropriate for the stated purpose, but the skill metadata lists no required env vars and no primary credential while the SKILL.md references OKX_ACCESS_KEY and an op:// secret source. The example op:// path (op://Engineering/okx/...) suggests an operator vault path — it's only an example, but it could confuse users into granting or pointing to broader secrets than necessary. Overall the credential handling is plausible but not proportionately declared or explained.
✓
Persistence & Privilege
The skill does not request always:true or other elevated persistent privileges. It does not modify other skills or system-wide settings in the instructions. Default autonomous invocation is allowed (platform default) and is not, by itself, a red flag here.
What to consider before installing
Key issues to consider before installing: (1) SKILL.md requires the 'uxc' CLI and uses a linked command 'okx-mcp-cli' but the skill metadata advertises no required binaries — ensure you have uxc installed and trust that CLI. (2) The skill expects an OKX API key (examples show OKX_ACCESS_KEY or op:// vault paths) but metadata doesn't declare required env vars; do not store sensitive keys in places you don't control. (3) The README includes a public demo API key — fine for read-only testing but replace it for production. (4) The op:// example references an organizational secret path; confirm you understand where secrets would be stored and that you won't accidentally grant access to broader vaults. (5) If you need stronger assurance, ask the publisher to update metadata to declare required binaries (uxc, okx-mcp-cli) and env vars, and to remove or clearly label any demo keys / example secret paths. Run this skill in a restricted environment until you verify behavior.

Like a lobster shell, security has layers — review code before you run it.

latestvk974mfkxeb0wfcvy16fz7sz46h8289nf
420downloads
0stars
2versions
Updated 1mo ago
v1.0.1
MIT-0
@jolestar
latest
Download

OKX MCP Skill

Use this skill to run OKX MCP operations through uxc.

Reuse the uxc skill for shared protocol discovery, output parsing, and generic auth/binding flows.

Prerequisites

  • uxc is installed and available in PATH.
  • Network access to https://web3.okx.com/api/v1/onchainos-mcp.
  • OKX Onchain API key is available for real calls.

Quick Trial Key

For quick read-only trial, OKX docs currently expose a shared demo key:

  • d573a84c-8e79-4a35-b0c6-427e9ad2478d

Example:

  • uxc auth credential set okx-mcp --auth-type api_key --api-key-header OK-ACCESS-KEY --secret d573a84c-8e79-4a35-b0c6-427e9ad2478d

Use your own key for regular usage, stability, and production workflows.

Core Workflow

  1. Confirm endpoint and protocol with help-first probing:
    • uxc https://web3.okx.com/api/v1/onchainos-mcp -h
  2. Configure credential/binding for repeatable auth:
    • uxc auth credential set okx-mcp --auth-type api_key --api-key-header OK-ACCESS-KEY --secret-env OKX_ACCESS_KEY
    • uxc auth credential set okx-mcp --auth-type api_key --api-key-header OK-ACCESS-KEY --secret-op op://Engineering/okx/OK-ACCESS-KEY
    • uxc auth binding add --id okx-mcp --host web3.okx.com --path-prefix /api/v1/onchainos-mcp --scheme https --credential okx-mcp --priority 100
  3. Use fixed link command by default:
    • command -v okx-mcp-cli
    • If missing, create it: uxc link okx-mcp-cli https://web3.okx.com/api/v1/onchainos-mcp
    • okx-mcp-cli -h
  4. Inspect operation schema before execution:
    • okx-mcp-cli dex-okx-market-price -h
    • okx-mcp-cli dex-okx-market-token-search -h
    • okx-mcp-cli dex-okx-balance-total-value -h
    • okx-mcp-cli dex-okx-dex-quote -h
  5. Prefer read operations first, then high-impact operations.

Capability Map

  • Market:
    • dex-okx-market-price
    • dex-okx-market-trades
    • dex-okx-market-candlesticks
    • dex-okx-market-candlesticks-history
    • dex-okx-index-current-price
    • dex-okx-index-historical-price
  • Token discovery/enrichment:
    • dex-okx-market-token-search
    • dex-okx-market-token-ranking
    • dex-okx-market-token-holder
    • dex-okx-market-token-basic-info
    • dex-okx-market-token-price-info
  • Wallet:
    • dex-okx-balance-chains
    • dex-okx-balance-total-value
    • dex-okx-balance-total-token-balances
    • dex-okx-balance-specific-token-balance
  • Swap:
    • dex-okx-dex-aggregator-supported-chains
    • dex-okx-dex-liquidity
    • dex-okx-dex-quote
    • dex-okx-dex-approve-transaction
    • dex-okx-dex-swap
    • dex-okx-dex-solana-swap-instruction

ChainIndex Quick Reference

  • Ethereum: 1
  • BSC: 56
  • XLayer: 196
  • Solana: 501
  • Base: 8453
  • Arbitrum: 42161

Always prefer runtime discovery (dex-okx-market-price-chains / dex-okx-dex-aggregator-supported-chains / dex-okx-balance-chains) when possible.

Guardrails

  • Keep automation on JSON output envelope; do not rely on --text.
  • Parse stable fields first: ok, kind, protocol, data, error.
  • Use okx-mcp-cli as default command path.
  • okx-mcp-cli <operation> ... is equivalent to uxc https://web3.okx.com/api/v1/onchainos-mcp <operation> ....
  • If call result contains Request header OK-ACCESS-KEY can not be empty:
    • confirm auth binding matches endpoint with uxc auth binding match https://web3.okx.com/api/v1/onchainos-mcp
    • update credential with explicit header: uxc auth credential set okx-mcp --auth-type api_key --api-key-header OK-ACCESS-KEY --secret-env OKX_ACCESS_KEY
    • confirm credential has a secret source (--secret-env, --secret-op, or literal --secret)
  • For high-impact operations require explicit user confirmation:
    • dex-okx-dex-approve-transaction
    • dex-okx-dex-swap
    • dex-okx-dex-solana-swap-instruction
  • Solana caveat from OKX docs:
    • for market candles/trades, use wSOL token address So11111111111111111111111111111111111111112
    • for some price contexts, SOL system address 11111111111111111111111111111111 may also appear in docs
    • when data is empty on Solana, verify operation-level address expectation first.

References

  • Invocation patterns:
    • references/usage-patterns.md

Comments

Loading comments...