gate-dex-market

Gate Wallet Market Skill

Market / Token domain — K-line, transaction stats, liquidity, token details, rankings, security audit, new token discovery. 7 MCP tools, all require no authentication.

Trigger scenarios: User mentions "market", "K-line", "kline", "price", "token info", "ranking", "security", "audit", "risk", "chart", "new token", "liquidity", or when market data / security audit assistance is needed.

Step 0: MCP Server Connection Check (Mandatory)

Before executing any operation, the Gate Wallet MCP Server must be confirmed available. This step cannot be skipped.

Connectivity probe:

CallMcpTool(server="gate-dex-mcp", toolName="chain.config", arguments={chain: "eth"})

| Result | Action | |--------|--------| | Success | MCP Server is available, proceed to next steps | | server not found / unknown server | Cursor not configured → show config guide (see below) | | connection refused / timeout | Unreachable → prompt to check URL and network |

When Cursor Is Not Configured

❌ Gate Wallet MCP Server Not Configured

No MCP Server named "gate-dex-mcp" found in Cursor. Follow these steps to configure:

Option 1: Via Cursor Settings (recommended)
  1. Open Cursor → Settings → MCP
  2. Click "Add new MCP server"
  3. Fill in:
     - Name: gate-dex-mcp
     - Type: HTTP
     - URL: https://api.gatemcp.ai/mcp
  4. Save and retry

Option 2: Manually edit config file
  Edit ~/.cursor/mcp.json, add:
  {
    "mcpServers": {
      "gate-dex-mcp": {
        "url": "https://api.gatemcp.ai/mcp"
      }
    }
  }

If you don't have an MCP Server URL yet, contact your administrator.

When Remote Service Is Unreachable

⚠️  Gate Wallet MCP Server Connection Failed

MCP Server configuration found, but unable to connect to the remote service. Please check:
1. Verify the service URL is correct (is the configured URL accessible?)
2. Check network connection (VPN / firewall interference?)
3. Confirm the remote service is running

When API Key Authentication Fails

🔑 Gate Wallet MCP Server Authentication Failed

MCP Server connected but API Key validation failed. The service has AK/SK authentication enabled (x-api-key header).
Contact your administrator to obtain a valid API Key and verify the server-side configuration.

Authentication

All tools in this Skill require no authentication — they are all public market data queries with no mcp_token needed.

MCP Tool Specifications

1. market_get_kline — Get K-Line Data

Retrieve candlestick (K-line) data for a specified token over a given time interval.

| Field | Description | |-------|-------------| | Tool name | market_get_kline | | Parameters | { chain: string, token_address: string, interval?: string, limit?: number } | | Returns | Array of K-line data, each containing timestamp, open, high, low, close, volume |

Parameters:

| Parameter | Required | Description | |-----------|----------|-------------| | chain | Yes | Chain identifier (e.g. "eth", "bsc") | | token_address | Yes | Token contract address. Use "native" for native tokens | | interval | No | K-line interval (e.g. "1m", "5m", "1h", "4h", "1d"). Default "1h" | | limit | No | Number of records to return. Default 100 |

Call example:

CallMcpTool(
  server="gate-dex-mcp",
  toolName="market_get_kline",
  arguments={
    chain: "eth",
    token_address: "0xdAC17F958D2ee523a2206206994597C13D831ec7",
    interval: "1h",
    limit: 24
  }
)

Response example:

[
  {
    "timestamp": 1700000000,
    "open": "1.0001",
    "high": "1.0005",
    "low": "0.9998",
    "close": "1.0002",
    "volume": "15000000"
  }
]

Agent behavior: Present K-line trends as text tables or summaries (high/low prices, price change, volume changes, etc.).

2. market_get_tx_stats — Get Transaction Statistics

Retrieve on-chain transaction statistics for a specified token (buy/sell counts, volumes, etc.).

| Field | Description | |-------|-------------| | Tool name | market_get_tx_stats | | Parameters | { chain: string, token_address: string, period?: string } | | Returns | { buy_count: number, sell_count: number, buy_volume: string, sell_volume: string, unique_buyers: number, unique_sellers: number } |

Parameters:

| Parameter | Required | Description | |-----------|----------|-------------| | chain | Yes | Chain identifier | | token_address | Yes | Token contract address | | period | No | Statistics period (e.g. "24h", "7d", "30d"). Default "24h" |

Call example:

CallMcpTool(
  server="gate-dex-mcp",
  toolName="market_get_tx_stats",
  arguments={
    chain: "eth",
    token_address: "0xdAC17F958D2ee523a2206206994597C13D831ec7",
    period: "24h"
  }
)

Response example:

{
  "buy_count": 12500,
  "sell_count": 11800,
  "buy_volume": "45000000",
  "sell_volume": "42000000",
  "unique_buyers": 3200,
  "unique_sellers": 2900
}

3. market_get_pair_liquidity — Get Trading Pair Liquidity

Retrieve liquidity pool information for a specified token's trading pairs.

| Field | Description | |-------|-------------| | Tool name | market_get_pair_liquidity | | Parameters | { chain: string, token_address: string } | | Returns | { total_liquidity_usd: string, pairs: [{ dex: string, pair: string, liquidity_usd: string, volume_24h: string }] } |

Parameters:

| Parameter | Required | Description | |-----------|----------|-------------| | chain | Yes | Chain identifier | | token_address | Yes | Token contract address |

Call example:

CallMcpTool(
  server="gate-dex-mcp",
  toolName="market_get_pair_liquidity",
  arguments={
    chain: "eth",
    token_address: "0xdAC17F958D2ee523a2206206994597C13D831ec7"
  }
)

Response example:

{
  "total_liquidity_usd": "250000000",
  "pairs": [
    {
      "dex": "Uniswap V3",
      "pair": "USDT/ETH",
      "liquidity_usd": "120000000",
      "volume_24h": "35000000"
    },
    {
      "dex": "Uniswap V3",
      "pair": "USDT/USDC",
      "liquidity_usd": "80000000",
      "volume_24h": "22000000"
    }
  ]
}

4. token_get_coin_info — Get Token Details

Retrieve detailed information for a specified token (name, symbol, market cap, holders, etc.).

| Field | Description | |-------|-------------| | Tool name | token_get_coin_info | | Parameters | { chain: string, token_address: string } | | Returns | { name: string, symbol: string, decimals: number, total_supply: string, market_cap: string, holders: number, price: string, price_change_24h: string, website: string, socials: object } |

Parameters:

| Parameter | Required | Description | |-----------|----------|-------------| | chain | Yes | Chain identifier | | token_address | Yes | Token contract address |

Call example:

CallMcpTool(
  server="gate-dex-mcp",
  toolName="token_get_coin_info",
  arguments={
    chain: "eth",
    token_address: "0xdAC17F958D2ee523a2206206994597C13D831ec7"
  }
)

Response example:

{
  "name": "Tether USD",
  "symbol": "USDT",
  "decimals": 6,
  "total_supply": "40000000000",
  "market_cap": "40000000000",
  "holders": 5200000,
  "price": "1.0001",
  "price_change_24h": "0.01",
  "website": "https://tether.to",
  "socials": { "twitter": "@Tether_to" }
}

5. token_ranking — Token Rankings

Retrieve on-chain token rankings (by market cap, price change, volume, etc.).

| Field | Description | |-------|-------------| | Tool name | token_ranking | | Parameters | { chain: string, sort_by?: string, order?: string, limit?: number } | | Returns | Array of ranked tokens, each containing rank, name, symbol, price, market_cap, change_24h, volume_24h |

Parameters:

| Parameter | Required | Description | |-----------|----------|-------------| | chain | Yes | Chain identifier | | sort_by | No | Sort dimension: "market_cap", `