Which integrations are available for this server?

Provides real-time access to Binance cryptocurrency market data, including current prices, order books, candlestick charts, trading history, 24-hour price changes, and various ticker statistics for cryptocurrencies.

How do I use Binance Cryptocurrency MCP?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Binance Cryptocurrency MCP what's the current price of Bitcoin in USDT?" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Binance Cryptocurrency MCP

by jianchundev

Overview Schema Related Servers Score Discussions

JavaScript

Remote

Binance Cryptocurrency MCP

Model Context Protocol service for accessing Binance cryptocurrency market data.

📄 License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.

Related MCP server: Binance MCP Server

🔄 Fork Notice

This is a fork of the original binance-mcp project by snjyor.

Major enhancements in this fork:

✅ Added SOCKS5 proxy support
✅ Enhanced proxy configuration options
✅ Improved documentation with copy-paste examples
✅ Better MCP configuration compatibility

🤝 Contributing

This fork maintains the same Apache 2.0 license as the original project. All contributions are welcome!

Overview

This MCP service allows AI agents (such as Claude, Cursor, Windsurf, etc.) to execute Binance API calls and obtain real-time data from the cryptocurrency market, including prices, candlestick charts, order books, and more.

Purpose You can directly ask AI about the latest cryptocurrency prices, trading volume, price trends, and other information, without having to check the Binance website or use other tools.

Available Information

Through this MCP service, you can obtain the following information:

Current price information - Get real-time prices for specified cryptocurrencies
Order book data - View buy and sell order depth
Candlestick chart data - Obtain candlestick data for different time periods
24-hour price changes - View price changes within 24 hours
Trading history - View recent trading records
Price statistics - Get price statistics for various time windows

Available Tools

Tool	Description
`get_price`	Get current price for specified cryptocurrency
`get_order_book`	Get order book data
`get_recent_trades`	Get list of recent trades
`get_historical_trades`	Get historical trade data
`get_aggregate_trades`	Get list of aggregate trades
`get_klines`	Get K-line/candlestick data
`get_ui_klines`	Get UI-optimized K-line data
`get_avg_price`	Get current average price
`get_24hr_ticker`	Get 24-hour price change statistics
`get_trading_day_ticker`	Get trading day market information
`get_book_ticker`	Get order book ticker
`get_rolling_window_ticker`	Get rolling window price change statistics

Using in Cursor

Global Installation

Use npx to run the MCP service directly from GitHub:

# Method 1: Direct from GitHub (recommended)
npx -y git+https://github.com/jianchundev/binance-mcp.git

# Method 2: Alternative for Windows compatibility
npx -y https://github.com/jianchundev/binance-mcp.git

# Method 3: Clone and run locally (most reliable)
git clone https://github.com/jianchundev/binance-mcp.git
cd binance-mcp
npm install
npm run build
npm start

In Cursor IDE:

Go to Cursor Settings > MCP
Click + Add New MCP Service
Fill in the form:
- Name: binance
- Type: command
- Command: npx -y git+https://github.com/jianchundev/binance-mcp.git
If the above doesn't work on Windows, use:
- Command: npx -y https://github.com/jianchundev/binance-mcp.git

Project Installation

Add a .cursor/mcp.json file to your project:

{
  "mcpServers": {
    "binance": {
      "command": "npx",
      "args": [
        "-y",
        "git+https://github.com/jianchundev/binance-mcp.git"
      ]
    }
  }
}

Windows Alternative:

{
  "mcpServers": {
    "binance": {
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/jianchundev/binance-mcp.git"
      ]
    }
  }
}

Alternative MCP Configuration

Some MCP clients use a different configuration format:

{
  "key": "binance",
  "command": "npx",
  "args": [
    "-y",
    "@snjyor/binance-mcp@latest"
  ],
  "approvalPolicy": "always"
}

Configuration Options

key: Unique identifier for the MCP service
command: Command to run the service
args: Arguments passed to the command
approvalPolicy:
- "always" - Auto-approve all tool calls
- "prompt" - Ask for approval before each tool call
- "never" - Never auto-approve
env: Environment variables (for proxy configuration)

Usage

After configuration, the Binance market data tools will be automatically available to Cursor AI agents:

The tool will be listed under Available Tools in the MCP settings
Agents will automatically use it when relevant
You can explicitly ask agents to use these tools

Using in Other MCP-Compatible Environments

Standard MCP Configuration

{
  "mcpServers": {
    "binance": {
      "command": "npx",
      "args": [
        "-y",
        "@snjyor/binance-mcp@latest"
      ]
    }
  }
}

Alternative Configuration Format

{
  "key": "binance",
  "command": "npx",
  "args": [
    "-y",
    "git+https://github.com/jianchundev/binance-mcp.git"
  ],
  "approvalPolicy": "always"
}

With Proxy Configuration

{
  "key": "binance",
  "command": "npx",
  "args": [
    "-y",
    "@snjyor/binance-mcp@latest"
  ],
  "approvalPolicy": "always",
  "env": {
    "SOCKS_PROXY": "socks5://127.0.0.1:1080"
  }
}

🚀 Quick Start with SOCKS5 Proxy (Copy & Paste)

For users who need proxy support, use this ready-to-use configuration:

{
  "key": "binance",
  "command": "npx",
  "args": [
    "-y",
    "git+https://github.com/jianchundev/binance-mcp.git"
  ],
  "approvalPolicy": "always",
  "env": {
    "SOCKS_PROXY": "socks5://127.0.0.1:1080"
  }
}

Common SOCKS5 Proxy Ports:

1080 - Default SOCKS5 port
7890 - Common alternative (Clash, V2Ray)
1081 - Alternative port
10808 - Some proxy tools

To use a different port, simply change the port number:

"env": {
  "SOCKS_PROXY": "socks5://127.0.0.1:7890"
}

📦 Installation from GitHub

This package is distributed directly from GitHub for simplicity and to avoid npm publishing overhead:

# Direct run from GitHub
npx -y git+https://github.com/jianchundev/binance-mcp.git

# Or clone and run locally
git clone https://github.com/jianchundev/binance-mcp.git
cd binance-mcp
npm install
npm run build
npm start

Benefits of GitHub distribution:

🚀 No npm account required
🔄 Always get the latest version
📝 Full source code transparency
⚡ Faster updates and fixes

🔧 Troubleshooting

Windows npx Issues

If you encounter 'binance-mcp' is not recognized error on Windows:

Try alternative URL format:

npx -y https://github.com/jianchundev/binance-mcp.git

Use local installation:

git clone https://github.com/jianchundev/binance-mcp.git
cd binance-mcp
npm install
npm run build

Update MCP configuration to use local path:

{
  "mcpServers": {
    "binance": {
      "command": "node",
      "args": ["C:\\path\\to\\binance-mcp\\dist\\index.js"]
    }
  }
}

Proxy Connection Issues

Verify your SOCKS5 proxy is running on the specified port
Check firewall settings
Try different proxy ports (7890, 1081, 10808)

Proxy Configuration

This MCP service supports both SOCKS5 and HTTP/HTTPS proxies to help users access Binance API from restricted networks.

SOCKS5 Proxy (Recommended)

Set environment variable:

# Linux/macOS
export SOCKS_PROXY="socks5://127.0.0.1:1080"

# Windows
set SOCKS_PROXY=socks5://127.0.0.1:1080

HTTP/HTTPS Proxy

Set environment variable:

# Linux/macOS
export HTTP_PROXY="http://127.0.0.1:8080"

# Windows
set HTTP_PROXY=http://127.0.0.1:8080

MCP Configuration with Proxy

{
  "mcpServers": {
    "binance": {
      "command": "npx",
      "args": [
        "-y",
        "@snjyor/binance-mcp@latest"
      ],
      "env": {
        "SOCKS_PROXY": "socks5://127.0.0.1:1080"
      }
    }
  }
}

For detailed proxy configuration instructions, see PROXY_CONFIG.md.

Usage Examples

Here are some usage examples:

Query Bitcoin Price

Please tell me the current price of Bitcoin

View Ethereum's 24-hour Price Movement

How has Ethereum's price changed in the past 24 hours?

Get BNB's K-line Data

Show me the daily K-line data for BNB over the last 5 days

Development

# Install dependencies
npm install

# Build
npm run build

# Local testing
npm run start

Debugging Server

To debug your server, you can use MCP Inspector.

First build the server

npm run build

Run the following command in terminal:

# Start MCP Inspector and server
npx @modelcontextprotocol/inspector node dist/index.js

License

Apache 2.0

Available Tools

12 tools

get_24hr_tickerD

ParametersJSON Schema

Name	Required	Description	Default
`symbol`	No	Trading pair symbol, e.g. BTCUSDT
`symbols`	No	Array of multiple trading pair symbols

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_aggregate_tradesD

ParametersJSON Schema

Name	Required	Description
`symbol`	Yes	Trading pair symbol, e.g. BTCUSDT
`fromId`	No	Aggregate trade ID to start from
`startTime`	No	Start timestamp (milliseconds)
`endTime`	No	End timestamp (milliseconds)
`limit`	No	Number of trades to return, default 500, max 1000

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_avg_priceD

ParametersJSON Schema

Name	Required	Description	Default
`symbol`	Yes	Trading pair symbol, e.g. BTCUSDT

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_book_tickerD

ParametersJSON Schema

Name	Required	Description	Default
`symbol`	No	Trading pair symbol, e.g. BTCUSDT
`symbols`	No	Array of multiple trading pair symbols

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_historical_tradesD

ParametersJSON Schema

Name	Required	Description
`symbol`	Yes	Trading pair symbol, e.g. BTCUSDT
`limit`	No	Number of trades to return, default 500, max 1000
`fromId`	No	Trade ID to start from, default returns the most recent trades

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_klinesD

ParametersJSON Schema

Name	Required	Description
`symbol`	Yes	Trading pair symbol, e.g. BTCUSDT
`interval`	Yes	K-line interval, e.g. 1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 1w, 1M
`startTime`	No	Start timestamp (milliseconds)
`endTime`	No	End timestamp (milliseconds)
`timeZone`	No	Time zone, default UTC
`limit`	No	Number of K-lines to return, default 500, max 1000

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_order_bookD

ParametersJSON Schema

Name	Required	Description	Default
`symbol`	Yes	Trading pair symbol, e.g. BTCUSDT
`limit`	No	Order book depth, default 100, max 5000

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_priceD

ParametersJSON Schema

Name	Required	Description	Default
`symbol`	No	Trading pair symbol, e.g. BTCUSDT
`symbols`	No	Array of multiple trading pair symbols

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_recent_tradesD

ParametersJSON Schema

Name	Required	Description	Default
`symbol`	Yes	Trading pair symbol, e.g. BTCUSDT
`limit`	No	Number of trades to return, default 500, max 1000

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_rolling_window_tickerD

ParametersJSON Schema

Name	Required	Description
`symbol`	No	Trading pair symbol, e.g. BTCUSDT
`symbols`	No	Array of multiple trading pair symbols
`windowSize`	No	Window size, e.g. 1m, 4h, 1d
`type`	No	Return data type, FULL or MINI

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_trading_day_tickerD

ParametersJSON Schema

Name	Required	Description
`symbol`	No	Trading pair symbol, e.g. BTCUSDT
`symbols`	No	Array of multiple trading pair symbols
`timeZone`	No	Time zone, default 0
`type`	No	Return data type, FULL or MINI

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_ui_klinesD

ParametersJSON Schema

Name	Required	Description
`symbol`	Yes	Trading pair symbol, e.g. BTCUSDT
`interval`	Yes	K-line interval, e.g. 1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 1w, 1M
`startTime`	No	Start timestamp (milliseconds)
`endTime`	No	End timestamp (milliseconds)
`timeZone`	No	Time zone, default UTC
`limit`	No	Number of K-lines to return, default 500, max 1000

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

12 tool updatesv1.0.1Mar 8, 2026
- First observedget_24hr_ticker
- First observedget_aggregate_trades
- First observedget_avg_price
- First observedget_book_ticker
- First observedget_historical_trades
- First observedget_klines
- First observedget_order_book
- First observedget_price
- First observedget_recent_trades
- First observedget_rolling_window_ticker
- First observedget_trading_day_ticker
- First observedget_ui_klines

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.8/5.0

Disambiguation3/5

The tools have clear naming that distinguishes different types of market data (e.g., ticker vs. trades vs. order book), but there is some overlap in purpose. For example, 'get_24hr_ticker', 'get_rolling_window_ticker', and 'get_trading_day_ticker' all provide ticker data with different timeframes, which could cause confusion without descriptions to clarify the differences. Similarly, 'get_recent_trades' and 'get_historical_trades' are closely related, and 'get_klines' and 'get_ui_klines' might overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent 'get_*' verb_noun pattern with snake_case, making them predictable and easy to parse. The naming is uniform across all 12 tools, with no deviations in style or convention, which enhances readability and reduces cognitive load for agents.

Tool Count4/5

With 12 tools focused on cryptocurrency market data retrieval, the count is reasonable for the server's purpose. It covers various aspects like prices, trades, order books, and tickers, but it might be slightly heavy if some tools are redundant (e.g., multiple ticker variants). Overall, it aligns well with the scope of providing comprehensive Binance API access.

Completeness2/5

The tool set is severely incomplete for a cryptocurrency trading server, as it only includes data retrieval tools (all 'get_*') and lacks any trading or account management operations. There are no tools for creating orders, managing portfolios, or executing trades, which are essential for a full Binance integration. This creates significant gaps that will limit agent functionality to read-only tasks.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

GitHub Repository

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

binance-mcp C
io.github.junct-bot
Binance - 340 tools for market data, order books, and trading pairs
Finance Cryptocurrency Blockchain
2
GroundAPI
io.github.qingkongzhiqian
Real-time data API for AI Agents: stocks, weather, forex, logistics, search, scrape, news, IP.
Search Web Scraping Finance
2
mcp-crypto-toolkit A
io.github.nad33mahm3d
Live crypto prices, conversion, gas tracker, portfolio tools, and calculators for AI agents.
Cryptocurrency Blockchain
101
aTars MCP A
ai.aarna
Crypto market signals, technical indicators, and sentiment analysis for AI agents.
Cryptocurrency Finance Search
182

Related MCP Servers

Binance Cryptocurrency MCP
Cryptocurrency Blockchain Finance
snjyor
A
license
D
quality
D
maintenance
MCP service that provides real-time access to Binance cryptocurrency market data, allowing AI agents to fetch current prices, order books, candlestick charts, and trading statistics through natural language queries.
Updated a year ago (2025-07-05 04:56 UTC)
12
42
45
Apache 2.0
Binance MCP Server
Cryptocurrency Agent Orchestration Blockchain
shanrichard
A
license
Not graded
quality
D
maintenance
Enables AI agents to perform cryptocurrency trading operations on Binance exchange through 30 comprehensive tools supporting spot trading, futures contracts, options, account management, market data analysis, and risk control features. Provides enterprise-grade security with local encrypted API key storage and supports multiple account types with sandbox environment testing.
Updated a year ago (2025-08-15 06:24 UTC)
9
MIT
Binance Cryptocurrency MCP
Cryptocurrency Finance Search
BACH-AI-Tools
A
license
Not graded
quality
D
maintenance
Enables AI agents to access real-time Binance cryptocurrency market data including prices, order books, candlestick charts, trading history, and 24-hour statistics through natural language queries.
Updated 9 months ago (2025-12-04 05:37 UTC)
21
Apache 2.0
Crypto MCP Server
Cryptocurrency Finance Search
WilliamNing316
A
license
Not graded
quality
D
maintenance
Provides real-time cryptocurrency market data from Binance API, including price queries, 24h statistics, K-line data, market trend analysis, and order book depth information for trading analysis.
Updated 9 months ago (2025-12-19 07:25 UTC)
16
1
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jianchundev/binance-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server