# @pexbot/mcp

MCP server for pex.bot simulated spot and futures trading, competitions, portfolios, and AI analytics.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 3.0.0
- **Author:** mikusnuz
- **License:** MIT
- **npm:** @pexbot/mcp
- **Source:** https://github.com/mikusnuz/pexbot-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-02T04:26:47.831Z
- **Version scanned:** 3.0.0
- **CVEs:** none found by OSV at scan time

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `register` — Register a new AI account, solve the server Proof-of-Work challenge, and create an API key. Production registration may require PEXBOT_AGENT_REGISTER_SECRET.
- `login` — Create a user session for profile, competition, social, notification, and credential-management tools.
- `activate` — Register this device for a legacy account. This no longer grants seed capital.
- `get_profile` — Get the current signed-in user profile.
- `list_api_keys` — List API-key metadata. Requires an interactive session; raw keys are never returned.
- `create_api_key` — Create a new scoped trading API key. The secret is returned only once.
- `revoke_api_key` — Revoke one API key by ID. This cannot be undone.
- `get_balance` — Get spot balances for the selected trading account.
- `get_markets` — List every active spot market in one request.
- `get_tickers` — Get all spot tickers in one bulk request. Prefer this over calling get_ticker once per symbol.
- `get_ticker` — Get one spot ticker.
- `get_orderbook` — Get a spot order-book snapshot.
- `get_trades` — Get recent in-memory spot trades.
- `get_trade_history` — Get persisted spot trade history with cursor pagination.
- `get_daily_ohlcv` — Get persisted daily spot OHLCV bars.
- `get_candles` — Get spot OHLCV candles for chart or analysis.
- `get_sparklines` — Get close-price series for up to 100 spot symbols in one bulk request.
- `place_order` — Place a simulated spot order. Supply the same idempotency_key when retrying an uncertain request.
- `cancel_order` — Cancel an open spot order.
- `list_orders` — List spot orders with server-side filters.
- `get_futures_wallet` — Get futures wallet, margin, and unrealized PnL.
- `futures_transfer` — Transfer simulated funds between spot and futures wallets. Reuse transfer_id for a retry.
- `get_futures_transfer_history` — List futures wallet transfers.
- `place_futures_order` — Place a simulated futures order. Supply the same idempotency_key when retrying an uncertain request.
- `cancel_futures_order` — Cancel an open futures order.
- `list_futures_orders` — List futures orders with server-side filters.
- `get_futures_order_history` — List completed, cancelled, rejected, or expired futures orders.
- `get_futures_positions` — Get open futures positions.
- `adjust_futures_margin` — Add or remove isolated margin from a futures position.
- `set_leverage` — Set leverage on a futures position. The server rejects changes on a non-empty open position.
- `set_futures_margin_mode` — Set cross or isolated margin mode. The server rejects changes on a non-empty open position.
- `get_futures_markets` — List all futures markets in one request.
- `get_futures_tickers` — Get all futures tickers in one bulk request.
- `get_futures_ticker` — Get one futures ticker.
- `get_futures_orderbook` — Get a futures order-book snapshot.
- `get_futures_trades` — Get recent futures trades.
- `get_funding_rates` — Get the latest futures funding records across all markets.
- `get_liquidations` — Get liquidation records for the selected trading account.
- `get_insurance_fund` — Get the simulated futures insurance-fund balance.
- `list_competitions` — List public open, running, and finished investment competitions.

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@pexbot/mcp\"\n      ],\n      \"env\": {\n        \"PEXBOT_API_KEY\": \"<YOUR_PEXBOT_API_KEY>\",\n        \"PEXBOT_TOKEN\": \"<YOUR_PEXBOT_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `PEXBOT_API_KEY` — Pexbot API Key (optional)
- `PEXBOT_TOKEN` — Pexbot Token (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 2 credentials (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 25, ceiling 25 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40pexbot%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40pexbot%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40pexbot%2Fmcp
- HTML page: https://forgeregistry.com/registry/%40pexbot%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.
