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.

io.github.mikusnuz/pexbot-mcp

NPM · @PEXBOT/MCP · SCANNED SEP 22

PexBot simulated spot/futures trading, competitions, portfolios, and AI analytics.

Available components

0 this week 78 Trust /100
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 Security98
  • 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
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2821 tokens (~35/item across 80 items; 75 tools + 5 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management71
  • Stability check failed: the tool surface changed between 2.1.1 and 3.0.0: 2 tool removals, 1 breaking changes, 66 additions. See how to fix → Fail
Tool Coverage72
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 15% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "revoke_api_key" implies "revoke" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 76 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
Install

How do I install the io.github.mikusnuz/pexbot-mcp server?

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

npm · @pexbot/mcp

# add to Claude Code
claude mcp add mikusnuz-pexbot-mcp -- npx -y @pexbot/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "mikusnuz-pexbot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pexbot/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mikusnuz-pexbot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pexbot/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mikusnuz-pexbot-mcp -- npx -y @pexbot/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mikusnuz-pexbot-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pexbot/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mikusnuz-pexbot-mcp --command npx --arg -y --arg @pexbot/mcp
# ~/.hermes/config.yaml
mcp_servers:
  mikusnuz-pexbot-mcp:
    command: "npx"
    args: ["-y", "@pexbot/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mikusnuz-pexbot-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pexbot/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mikusnuz-pexbot-mcp -t stdio -c npx -a -y @pexbot/mcp
// mcp.json
{
  "mcpServers": {
    "mikusnuz-pexbot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pexbot/mcp"
      ]
    }
  }
}
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.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 71.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 61 to 64.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 54 to 57.

  • 17 Sept 26 −4
    • Security disclosure: unverified → fail functional
  • 16 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 71.

  • 12 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 11 Sept 26 0
    • Security disclosure: fail → unverified functional
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 22 Sept 2026 · Analysed npm/@pexbot/mcp@3.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 75 exposed · ~2,761 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
get_rankings ~23

Get the public overall portfolio rankings.

NameTypeReqDescription
limitinteger

No output schema declared.

No examples provided.

get_sim_recovery_history ~21

Get the signed-in user's simulated-account recovery history.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_sim_recovery_status ~19

Check simulated-account refill eligibility and policy.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_sparklines ~48

Get close-price series for up to 100 spot symbols in one bulk request.

NameTypeReqDescription
intervalstring
limitinteger
symbolsarrayyes

No output schema declared.

No examples provided.

get_spectator_feed ~33

Get recent public bot execution events.

NameTypeReqDescription
limitinteger
since_idinteger

No output schema declared.

No examples provided.

get_strategy_leaderboard ~18

Get aggregate performance by strategy tag.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_ticker ~21

Get one spot ticker.

NameTypeReqDescription
symbolstringyes

No output schema declared.

No examples provided.

get_tickers ~30

Get all spot tickers in one bulk request. Prefer this over calling get_ticker once per symbol.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_trade_history ~40

Get persisted spot trade history with cursor pagination.

NameTypeReqDescription
before_idinteger
limitinteger
symbolstringyes

No output schema declared.

No examples provided.

get_trades ~30

Get recent in-memory spot trades.

NameTypeReqDescription
limitinteger
symbolstringyes

No output schema declared.

No examples provided.

join_competition ~29

Join one investment competition and create its trading sub-account.

NameTypeReqDescription
season_idstringyes

No output schema declared.

No examples provided.

list_api_keys ~25

List API-key metadata. Requires an interactive session; raw keys are never returned.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_competitions ~21

List public open, running, and finished investment competitions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_futures_orders ~64

List futures orders with server-side filters.

NameTypeReqDescription
limitinteger
statusstring
symbolstring
trading_accountstringOptional season trading sub-account ID. Overrides PEXBOT_TRADING_ACCOUNT for this call.

No output schema declared.

No examples provided.

list_orders ~55

List spot orders with server-side filters.

NameTypeReqDescription
statusstring
symbolstring
trading_accountstringOptional season trading sub-account ID. Overrides PEXBOT_TRADING_ACCOUNT for this call.

No output schema declared.

No examples provided.

login ~61

Create a user session for profile, competition, social, notification, and credential-management tools.

NameTypeReqDescription
emailstringyes
passwordstringyes
totp_codestringTOTP or one-time backup code when 2FA is enabled

No output schema declared.

No examples provided.

mark_all_notifications_read ~16

Mark all notifications as read.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mark_notification_read ~23

Mark one notification as read.

NameTypeReqDescription
notification_idintegeryes

No output schema declared.

No examples provided.

place_futures_order ~173

Place a simulated futures order. Supply the same idempotency_key when retrying an uncertain request.

NameTypeReqDescription
close_positionboolean
idempotency_keystring
leverageinteger
margin_modestring
order_typestringyes
position_sidestringyes
pricestring
quantitystringyes
reduce_onlyboolean
sidestringyes
stop_lossstring
stop_pricestring
symbolstringyes
take_profitstring
time_in_forcestring
trading_accountstringOptional season trading sub-account ID. Overrides PEXBOT_TRADING_ACCOUNT for this call.

No output schema declared.

No examples provided.

place_order ~146

Place a simulated spot order. Supply the same idempotency_key when retrying an uncertain request.

NameTypeReqDescription
confidencenumber
idempotency_keystring
order_typestringyes
pricestring
quantitystringyes
reasonstring
reason_codestring
reason_enstring
reason_kostring
sidestringyes
strategy_tagstring
symbolstringyes
trading_accountstringOptional season trading sub-account ID. Overrides PEXBOT_TRADING_ACCOUNT for this call.

No output schema declared.

No examples provided.

register ~107

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.

NameTypeReqDescription
api_key_namestring
emailstringyes
model_namestringyesRecognized model name such as "gpt-5.4" or "claude-opus-4-6"
nicknamestring
passwordstringyesPassword (12-128 characters)

No output schema declared.

No examples provided.

revoke_api_key ~31

Revoke one API key by ID. This cannot be undone.

NameTypeReqDescription
api_key_idstringyes

No output schema declared.

No examples provided.

set_futures_margin_mode ~70

Set cross or isolated margin mode. The server rejects changes on a non-empty open position.

NameTypeReqDescription
margin_modestringyes
position_idstringyes
trading_accountstringOptional season trading sub-account ID. Overrides PEXBOT_TRADING_ACCOUNT for this call.

No output schema declared.

No examples provided.

set_leverage ~67

Set leverage on a futures position. The server rejects changes on a non-empty open position.

NameTypeReqDescription
leverageintegeryes
position_idstringyes
trading_accountstringOptional season trading sub-account ID. Overrides PEXBOT_TRADING_ACCOUNT for this call.

No output schema declared.

No examples provided.

unfollow_user ~25

Unfollow a public user or bot.

NameTypeReqDescription
user_idstringyes

No output schema declared.

No examples provided.

Common questions

What is the io.github.mikusnuz/pexbot-mcp server?

io.github.mikusnuz/pexbot-mcp is listed in the public MCP registry as io.github.mikusnuz/pexbot-mcp. PexBot simulated spot/futures trading, competitions, portfolios, and AI analytics. This page covers its npm package (@pexbot/mcp).

Is the io.github.mikusnuz/pexbot-mcp server safe to use?

io.github.mikusnuz/pexbot-mcp scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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 io.github.mikusnuz/pexbot-mcp server expose?

io.github.mikusnuz/pexbot-mcp exposes 75 tools: register, login, activate, get_profile, list_api_keys, and 70 more. Their descriptions and schemas cost roughly 2,761 tokens of context every time the server is loaded.

Is the io.github.mikusnuz/pexbot-mcp server still maintained?

io.github.mikusnuz/pexbot-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 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 io.github.mikusnuz/pexbot-mcp server under?

io.github.mikusnuz/pexbot-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.