Bitget Wallet MCP Server

39 tools. 6 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated:

6 can modify or destroy data
33 read-only
39 tools total

Community server · catalogue entry verified 11/06/2026

How to control Bitget Wallet MCP Server ↓

What Bitget Wallet MCP Server exposes to your agents

Read (33) Write / Execute (4) Destructive / Financial (2)
Critical Risk

The most dangerous Bitget Wallet MCP Server tools

6 of Bitget Wallet MCP Server's 39 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Bitget Wallet MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Bitget Wallet MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default
{
  "transfer_make_order": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Cap read operations
{
  "security_audit": {
    "limits": [
      {
        "counter": "security_audit_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Bitget Wallet MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON BITGET WALLET →

Free to start. No card required.

All 39 Bitget Wallet MCP Server tools

READ 33 tools
Read security_audit Run a security audit on a token contract (honeypot detection, permission checks, blacklist). Read balance balance Read batch_token_info Get info for multiple tokens in one call. Read batch_tx_info Batch get transaction statistics for multiple tokens. Read check_swap_token check_swap_token Read coin_dev coin_dev Read coin_market_info Get detailed market information for a token including price, market cap, FDV, liquidity, holders, price change Read get_token_list Get popular/recommended tokens for a specific chain. Read historical_coins Get token list by timestamp (paginated). Useful for discovering new tokens. Read holders_info holders_info Read kline Get K-line (candlestick) data for a token. Read launchpad_tokens launchpad_tokens Read liquidity Get liquidity pool information for a token. Read profit_address_analysis Get profit/loss analysis of addresses holding a token (distribution of profitable vs losing addresses). Read rankings Get token rankings. Read rwa_config Get RWA trading config: supported stablecoins, slippage, amount limits, gas info. Read rwa_kline Get K-line data for an RWA stock. Read rwa_my_holdings Get user's RWA stock holdings. Read rwa_order_price rwa_order_price Read rwa_stock_info Get RWA stock info: market status, trading limits, chain assets, description. Read rwa_ticker_list Get available RWA stock tickers. Optionally include user balance. Read search_tokens search_tokens Read search_tokens_v2 Search tokens by keyword using v2 API (broader results including DEX tokens). Read simple_kline simple_kline Read smart_money_addresses smart_money_addresses Read swap_get_order_details Query swap order status and details. Read token_info token_info Read token_price Get the current price of a token. Read top_profit Get top profitable addresses for a token (who made the most money trading this token). Read trading_dynamics Get trading dynamics for a token (buy/sell pressure, whale activity, etc.). Read transaction_list transaction_list Read transfer_get_order Query transfer order status. Poll until terminal status (SUCCESS or FAILED). Read tx_info Get token transaction statistics (5m/1h/4h/24h volume, buyers, sellers).

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Bitget Wallet MCP Server

Can an AI agent move money through the Bitget Wallet MCP Server MCP server? +

Yes. The Bitget Wallet MCP Server server exposes 2 financial tools including transfer_make_order, transfer_submit. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How many tools does the Bitget Wallet MCP Server MCP server expose? +

39 tools across 4 categories: Execute, Financial, Read, Write. 33 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Bitget Wallet MCP Server? +

Register the Bitget Wallet MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Bitget Wallet MCP Server tool call.

Deterministic rules across all 39 Bitget Wallet MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

39 Bitget Wallet MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.