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.hummingbot/mcp

OCI · DOCKER.IO/HUMMINGBOT/HUMMINGBOT-MCP:0.1.0 · SCANNED SEP 20

MCP server exposing Hummingbot API for automated multi-exchange trading

0 this week 41 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 Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency30
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2998 tokens (~199/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (87% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy_bot_with_controllers" implies "deploy" 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 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the io.github.hummingbot/mcp server?

io.github.hummingbot/mcp runs locally as a container image, launched with docker run --rm -i docker.io/hummingbot/hummingbot-mcp:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · docker.io/hummingbot/hummingbot-mcp:0.1.0

# add to Claude Code
claude mcp add hummingbot-mcp -- docker run --rm -i docker.io/hummingbot/hummingbot-mcp:0.1.0
// .cursor/mcp.json
{
  "mcpServers": {
    "hummingbot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/hummingbot/hummingbot-mcp:0.1.0"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hummingbot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/hummingbot/hummingbot-mcp:0.1.0"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add hummingbot-mcp -- docker run --rm -i docker.io/hummingbot/hummingbot-mcp:0.1.0
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hummingbot-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "docker.io/hummingbot/hummingbot-mcp:0.1.0"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  hummingbot-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "docker.io/hummingbot/hummingbot-mcp:0.1.0"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hummingbot-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "docker.io/hummingbot/hummingbot-mcp:0.1.0"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "hummingbot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/hummingbot/hummingbot-mcp:0.1.0"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 −4
    • Stability: pass → 0.77 functional
  • 18 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail functional
  • 17 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 12 Sept 26 −3
    • Security disclosure: fail → unverified functional
    • Stability: pass → 0.80 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 20 Sept 2026 · Analysed oci/docker.io/hummingbot/hummingbot-mcp:0.1.0

Provenance No attestation

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

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 15 exposed · ~2,998 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
deploy_bot_with_controllers ~179

Deploy a bot with specified controller configurations. Args: bot_name: Name of the bot to deploy controllers_config: List of controller configs to use for the bot deployment. account_name: Account name to use for the bot (default: master_account) max_global_drawdown_quote: Maximum global drawdown in quote currency (optional) defaults to None. max_controller_drawdown_quote: Maximum drawdown per controller in quote currency (optional) defaults to None. image: Docker image to use for the bot (default: "hummingbot/hummingbot:latest")

NameTypeReqDescription
account_name
bot_namestringyes
controllers_configarrayyes
imagestring
max_controller_drawdown_quote
max_global_drawdown_quote
NameTypeReqDescription
resultstringyes

No examples provided.

explore_controllers ~453

Explore and understand controllers and their configs. Use this tool to discover what's available and understand how things work. Progressive flow: 1. action="list" → List all controllers and their configs 2. action="list" + controller_type → List controllers of that type with config counts 3. action="describe" + controller_name → Show controller code + list its configs + explain parameters 4. action="describe" + config_name → Show specific config details + which controller it uses Common Enum Values for Controller Configs: Position Mode (position_mode): - "HEDGE" - Allows holding both long and short positions simultaneously - "ONEWAY" - Allows only one direction position at a time - Note: Use as string value, e.g., position_mode: "HEDGE" Trade Side (side): - 1 or "BUY" - For long/buy positions - 2 or "SELL" - For short/sell positions - 3 - Other trade types - Note: Numeric values are required for controller configs Order Type (order_type, open_order_type, take_profit_order_type, etc.): - 1 or "MARKET" - Market order - 2 or "LIMIT" - Limit order - 3 or "LIMIT_MAKER" - Limit maker order (post-only) - 4 - Other order types - Note: Numeric values are required for controller configs Args: action: "list" to list controllers or "describe" to show details of a specific controller or config. controller_type: Type of controller to filter by (optional, e.g., 'directional_trading', 'market_making', 'generic'). controller_name: Name of the controller to describe (optional, only required for describe specific controller). config_name: Name of the config to describe (optional, only required for describe specific config).

NameTypeReqDescription
actionstringyes
config_name
controller_name
controller_type
NameTypeReqDescription
resultstringyes

No examples provided.

get_active_bots_status ~43

Get the status of all active bots. Including the unrealized PnL, realized PnL, volume traded, latest logs, etc.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_candles ~159

Get the real-time candles for a trading pair on a specific exchange connector. Args: connector_name: Exchange connector name (e.g., 'binance', 'binance_perpetual') trading_pair: Trading pair to get candles for (e.g., 'BTC-USDT') interval: Candle interval (default: '1h'). Options include '1m', '5m', '15m', '30m', '1h', '4h', '1d'. days: Number of days of historical data to retrieve (default: 30).

NameTypeReqDescription
connector_namestringyes
daysinteger
intervalstring
trading_pairstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_funding_rate ~111

Get the latest funding rate for a trading pair on a specific exchange connector. Only works for perpetual connectors so the connector name must have _perpetual in it. Args: connector_name: Exchange connector name (e.g., 'binance_perpetual', 'hyperliquid_perpetual') trading_pair: Trading pair to get funding rate for (e.g., 'BTC-USDT')

NameTypeReqDescription
connector_namestringyes
trading_pairstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_order_book ~203

Get order book data for a trading pair on a specific exchange connector, if the query type is different than snapshot, you need to provide query_value and is_buy Args: connector_name: Connector name (e.g., 'binance', 'binance_perpetual') trading_pair: Trading pair (e.g., BTC-USDT) query_type: Order book query type ('snapshot', 'volume_for_price', 'price_for_volume', 'quote_volume_for_price', 'price_for_quote_volume') query_value: Only required if query_type is not 'snapshot'. The value to query against the order book. is_buy: Only required if query_type is not 'snapshot'. Is important to see what orders of the book analyze.

NameTypeReqDescription
connector_namestringyes
is_buyboolean
query_typestringyes
query_value
trading_pairstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_orders ~231

Get the orders manged by the connected accounts. Args: account_names: List of account names to filter by (optional). If empty, returns all accounts. connector_names: List of connector names to filter by (optional). If empty, returns all connectors. trading_pairs: List of trading pairs to filter by (optional). If empty, returns all trading pairs. status: Order status to filter by can be OPEN, PARTIALLY_FILLED, FILLED, CANCELED, FAILED (is optional). start_time: Start time (in seconds) to filter by (optional). end_time: End time (in seconds) to filter by (optional). limit: Number of orders to return defaults to 500, maximum is 1000. cursor: Cursor for pagination (optional, should be used if another request returned a cursor).

NameTypeReqDescription
account_names
connector_names
cursor
end_time
limit
start_time
status
trading_pairs
NameTypeReqDescription
resultstringyes

No examples provided.

get_portfolio_balances ~225

Get portfolio balances and holdings across all connected exchanges. Returns detailed token balances, values, and available units for each account. Use this to check your portfolio, see what tokens you hold, and their current values. If passing accounts and connectors it will only return the filtered accounts and connectors, leave it empty to return all accounts and connectors. You can also get the portfolio distribution by setting `as_distribution` to True, which will return the distribution of tokens and their values across accounts and connectors and the percentage of each token in the portfolio. Args: account_names: List of account names to filter by (optional). If empty, returns all accounts. connector_names: List of connector names to filter by (optional). If empty, returns all connectors. as_distribution: If True, returns the portfolio distribution as a percentage of each token in the portfolio and their values across accounts and connectors. Defaults to False.

NameTypeReqDescription
account_names
as_distributionboolean
connector_names
NameTypeReqDescription
resultstringyes

No examples provided.

get_positions ~99

Get the positions managed by the connected accounts. Args: account_names: List of account names to filter by (optional). If empty, returns all accounts. connector_names: List of connector names to filter by (optional). If empty, returns all connectors. limit: Number of positions to return defaults to 100, maximum is 1000.

NameTypeReqDescription
account_names
connector_names
limit
NameTypeReqDescription
resultstringyes

No examples provided.

get_prices ~91

Get the latest prices for the specified trading pairs on a specific exchange connector. Args: connector_name: Exchange connector name (e.g., 'binance', 'binance_perpetual') trading_pairs: List of trading pairs to get prices for (e.g., ['BTC-USDT', 'ETH-USD'])

NameTypeReqDescription
connector_namestringyes
trading_pairsarrayyes
NameTypeReqDescription
resultstringyes

No examples provided.

modify_controllers ~431

Create, update, or delete controllers and their configurations. If bot name is provided, it can only modify the config in the bot deployed with that name. IMPORTANT: When creating a config without specifying config_data details, you MUST first use the explore_controllers tool with action="describe" and the controller_name to understand what parameters are required. The config_data must include ALL relevant parameters for the controller to function properly. Controllers = are essentially strategies that can be run in Hummingbot. Configs = are the parameters that the controller uses to run. Args: action: "upsert" (create/update) or "delete" target: "controller" (template) or "config" (instance) confirm_override: Required True if overwriting existing config_data: For config creation, MUST contain all required controller parameters. Use explore_controllers first! Workflow for creating a config: 1. Use explore_controllers(action="describe", controller_name="<name>") to see required parameters 2. Create config_data dict with ALL required parameters from the controller template 3. Call modify_controllers with the complete config_data Examples: - Create new controller: modify_controllers("upsert", "controller", controller_type="market_making", ...) - Create config: modify_controllers("upsert", "config", config_name="pmm_btc", config_data={...}) - Modify config from bot: modify_controllers("upsert", "config", config_name="pmm_btc", config_data={...}, bot_name="my_bot") - Delete config: modify_controllers("delete", "config", config_name="old_strategy")

NameTypeReqDescription
actionstringyes
bot_name
config_data
config_name
confirm_overrideboolean
controller_code
controller_name
controller_type
targetstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

place_order ~258

Place a buy or sell order (supports USD values by adding at the start of the amount $). Args: connector_name: Exchange connector name (e.g., 'binance', 'binance_perpetual') trading_pair: Trading pair (e.g., BTC-USDT, ETH-USD) trade_type: Order side ('BUY' or 'SELL') amount: Order amount (is always in base currency, if you want to use USD values, add a dollar sign at the start, e.g., '$100') order_type: Order type ('MARKET' or 'LIMIT') price: Price for limit orders (required for limit orders) position_action: Position action ('OPEN', 'CLOSE'). Defaults to 'OPEN' and is useful for perpetuals with HEDGE mode where you can hold a long and short position at the same time. account_name: Account name (default: master_account)

NameTypeReqDescription
account_name
amountstringyes
connector_namestringyes
order_typestring
position_action
price
trade_typestringyes
trading_pairstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

set_account_position_mode_and_leverage ~173

Set position mode and leverage for an account on a specific exchange. If position mode is not specified, will only set the leverage. If leverage is not specified, will only set the position mode. Args: account_name: Account name (default: master_account) connector_name: Exchange connector name (e.g., 'binance_perpetual') trading_pair: Trading pair (e.g., ETH-USD) only required for setting leverage position_mode: Position mode ('HEDGE' or 'ONE-WAY') leverage: Leverage to set (optional, required for HEDGE mode)

NameTypeReqDescription
account_namestringyes
connector_namestringyes
leverage
position_mode
trading_pair
NameTypeReqDescription
resultstringyes

No examples provided.

setup_connector ~207

Setup a new exchange connector for an account with credentials using progressive disclosure. This tool guides you through the entire process of connecting an exchange with a four-step flow: 1. No parameters → List available exchanges 2. Connector only → Show required credential fields 3. Connector + credentials, no account → Select account from available accounts 4. All parameters → Connect the exchange (with override confirmation if needed) Args: connector: Exchange connector name (e.g., 'binance', 'binance_perpetual'). Leave empty to list available connectors. credentials: Credentials object with required fields for the connector. Leave empty to see required fields first. account: Account name to add credentials to. If not provided, prompts for account selection. confirm_override: Explicit confirmation to override existing connector. Required when connector already exists.

NameTypeReqDescription
account
confirm_override
connector
credentials
NameTypeReqDescription
resultstringyes

No examples provided.

stop_bot_or_controllers ~135

Stop and archive a bot forever or stop the execution of a controller of a runnning bot. If the controllers to stop are not specified, it will stop the bot execution and archive it forever, if they are specified, will only stop the execution of those controllers and the bot will still be running with the rest of the controllers. Args: bot_name: Name of the bot to stop controller_names: List of controller names to stop (optional, if not provided will stop the bot execution)

NameTypeReqDescription
bot_namestringyes
controller_names

No output schema declared.

No examples provided.

Common questions

What is the io.github.hummingbot/mcp server?

io.github.hummingbot/mcp is listed in the public MCP registry as io.github.hummingbot/mcp. MCP server exposing Hummingbot API for automated multi-exchange trading. This page covers its container image (docker.io/hummingbot/hummingbot-mcp:0.1.0).

Is the io.github.hummingbot/mcp server safe to use?

io.github.hummingbot/mcp scores 41 out of 100 on VerifyMCP. 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.hummingbot/mcp server expose?

io.github.hummingbot/mcp exposes 15 tools: setup_connector, get_portfolio_balances, place_order, set_account_position_mode_and_leverage, get_orders, and 10 more. Their descriptions and schemas cost roughly 2,998 tokens of context every time the server is loaded.

Is the io.github.hummingbot/mcp server still maintained?

io.github.hummingbot/mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.