Yubit Exchange Skill
The Yubit Exchange MCP Server lets AI assistants query market data, manage funds, check balances across spot, TradFi, and earn accounts, and execute perpetual trades using natural language.
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @yubit/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add yubit-exchange-skill -- npx -y @yubit/exchange-skill@1.0.6Execute em um terminal.
{ "mcpServers": { "yubit-exchange-skill": { "command": "npx", "args": [ "-y", "@yubit/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
The Yubit Exchange MCP Server lets AI assistants query market data, manage funds, check balances across spot, TradFi, and earn accounts, and execute perpetual trades using natural language.
Yubit exchange MCP Server for market data, wallet, perp trading, and diagnostics
It works with OpenClaw, Claude Code, OpenAI Codex, Cursor, LobeChat Desktop, and any other AI tool compatible with the MCP protocol.
Full usage rules, account semantics, trading constraints, and troubleshooting rules are in
skills/yubit/SKILL.md.
Prerequisites: Node.js >= 19
Recommended installation paths:
OpenClaw Hub: For OpenClaw users. Install the runtime first, then install the public yubit skill.npm / npx: Recommended for most MCP clients, including Claude Code, Codex, Cursor, LobeChat Desktop, and local OpenClaw integration.Source install: Best for local development, debugging, or running directly from the repository.npm install -g @yubit/exchange-skill
yubit setup --client openclaw
openclaw skills install yubit
After setup finishes, start a new OpenClaw session for the yubit skill so the MCP server is loaded.
# Global npm install
npm install -g @yubit/exchange-skill
yubit setup
# Or npx (no install required)
npx @yubit/exchange-skill setup
The setup wizard automatically detects supported AI tools, configures your API credentials, and registers the MCP server. During first-time setup, you will be prompted for:
API KeyAPI SecretAPI Base URLCredentials are stored in ~/.exchange-skill/config.json and shared across all clients. To rotate your keys, run yubit config init.
git clone https://github.com/yubit-exchange/exchange-skill.git
cd exchange-skill
./setup/install.sh
Use this path when running from source or doing local development and debugging.
If you prefer not to use yubit setup, or want to control the MCP configuration manually, use the following methods.
openclaw mcp set yubit '{
"command": "yubit",
"args": ["start"],
"env": { "EXCHANGE_ENABLE_TRADE": "true" }
}'
rm -rf ~/.openclaw/skills/yubit ~/.openclaw/skills/yubit-*
cp -r skills/yubit ~/.openclaw/skills/
openclaw gateway restart
claude mcp add --transport stdio yubit --env EXCHANGE_ENABLE_TRADE=true -- yubit start
# ~/.codex/config.toml
[mcp_servers.yubit]
command = "yubit"
args = ["start"]
[mcp_servers.yubit.env]
EXCHANGE_ENABLE_TRADE = "true"
// ~/.cursor/mcp.json
{
"mcpServers": {
"yubit": {
"command": "yubit",
"args": ["start"],
"env": { "EXCHANGE_ENABLE_TRADE": "true" }
}
}
}
The web version does not support STDIO MCP. You must use the desktop app.
Open the plugin menu → Add MCP Plugin → Quick Import JSON → paste the same JSON shown for Cursor above → select STDIO as the connection type.
Usage recommendations:
- Open new position →
perpCreateOrder- Add to existing position →
perpAddToPosition- Especially in separate-position mode, do not treat "add to existing position" as simply calling
perpCreateOrderagain
EXCHANGE_ENABLE_TRADE=true)perpCancelAllOrders/perpClosePosition by settleCoin requires confirmBatch=trueperpAddToPosition queries current positions on the server first; in separate-position mode, it auto-targets the unique position or requires explicit pzLinkId, then reads back to verify no accidental new sub-position was openedFilled but perpGetPositions(symbol) returns empty, first check perpGetOrderHistory + perpGetExecutions + perpGetClosedPnl to determine whether the position was closed by a later reverse order; do not start by guessing about symbol mapping or position delays.data/audit.log (JSON Lines), with sensitive information automatically redacted.data/trace-records.jsonl, including raw HTTP request/response, retained for 7 days / max 1000 entries~/.exchange-skill/config.json; client configs do not contain API KeyIf a market order to open a position succeeds and an execution is recorded, but the subsequent position query is empty, follow this sequence:
perpGetOrderHistory(symbol, orderId): Confirm open order status is FilledperpGetExecutions(symbol, orderId): Confirm actual fill qty, price, and timeperpGetPositions(symbol): Confirm the position is indeed emptyperpGetClosedPnl(symbol, limit='10'): Check whether a closed-P&L record with the same size and opposite direction appeared within secondsperpGetOrderHistory(symbol, closeOrderId) to check if the close order has reduceOnly=trueNotes:
M1ETHUSDT in order history are usually just the exchange's internal symbol format. They do not mean the position is hidden under a different symbol.exchange-skill/
├── mcp-server.js # MCP Server entry point
├── bin/cli.js # CLI
├── lib/
│ ├── signer.js # HMAC-SHA256 signing
│ ├── http.js # HTTP client (with rate limiting)
│ ├── config.js # Config loader
│ ├── validate.js # Parameter validation
│ ├── normalize.js # Response normalization
│ ├── audit.js # Audit logging
│ ├── trace-store.js # Trace storage/retrieval
│ ├── capabilities.js # Capability snapshot builder
│ └── setup/ # Client management
├── tools/
│ ├── market.js # Market (9 tools)
│ ├── spot.js # Spot query (1 tool)
│ ├── tradfi.js # TradFi query (1 tool)
│ ├── earn.js # Earn query (1 tool)
│ ├── perp-query.js # Perp query (9 tools)
│ ├── perp.js # Perp trade (12 tools)
│ ├── wallet.js # Wallet (3 tools)
│ └── diagnostics.js # Diagnostics (3 tools)
├── skills/ # AI Agent behavior specs
└── test/ # Unit tests + smoke tests
npm test # Unit tests (no network required)
npm run test:smoke # Smoke tests (requires API Key, executes real trades)
npm run test:all # All tests
Smoke tests will place real orders, cancel them, and close positions. Use a dedicated test account.
New tools should follow the existing naming convention: {product}{Action} camelCase. Product-specific tools get a prefix (perp/spot/tradfi/earn/tapTrading); shared tools have no prefix.
npm test && npm run test:smoke # Must pass after any changes
payload = timestamp + apiKey + recvWindow + payload
signature = HMAC-SHA256(apiSecret, payload).hex()
Yubit exchange MCP Server for market data, wallet, perp trading, and diagnostics
{ "mcpServers": { "yubit-exchange-skill": { "command": "npx", "args": [ "-y", "@yubit/[email protected]" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
@yubit/exchange Skill roda localmente via stdio.
Última verificação: 2026-11-17. Yubit exchange MCP Server for market data, wallet, perp trading, and diagnostics