Which integrations are available for this server?

Provides advanced technical analysis capabilities for cryptocurrency trading on Binance, including moving averages, momentum indicators, volatility measures, volume analysis, market trend detection, support/resistance levels, and multi-symbol comparison.

How do I use binance-mcp-enhanced?

1. Click on "Deploy 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-mcp-enhanced Analyze BTCUSDT on 4h timeframe with support/resistance levels" 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-mcp-enhanced

by CarlosIrineuCosta

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Binance MCP Enhanced - Technical Analysis Edition

Enhanced fork of binance-mcp by @snjyor
Original work licensed under Apache 2.0 License

A powerful cryptocurrency analysis MCP server that adds advanced technical analysis capabilities to the original Binance MCP implementation.

What's New

Technical Indicators

Moving Averages: SMA, EMA with customizable periods
Momentum: RSI, MACD for trend strength analysis
Volatility: Bollinger Bands, ATR for risk assessment
Volume: VWAP for institutional trading levels

Market Analysis

Trend Detection: Automatic bullish/bearish/neutral classification
Support & Resistance: Dynamic level identification
Price Statistics: Returns, volatility, Sharpe ratio calculations
Market Conditions: Overbought/oversold detection

Multi-Symbol Tools

Performance Comparison: Compare up to 5 symbols
Correlation Analysis: Find related trading pairs
Volatility Ranking: Identify high/low volatility assets

Security Enhancements

Updated all dependencies to latest secure versions
Non-root Docker container execution
Comprehensive input validation
Sanitized error messages

Related MCP server: Binance MCP Server

Installation

Docker (Recommended)

# Build the enhanced image
docker build -t binance-mcp-enhanced .

# Run the container
docker run -i --rm binance-mcp-enhanced

Local Installation

# Install dependencies
npm install

# Build
npm run build

# Run
npm start

Configuration

Claude Desktop

Add to your claude_desktop_config.json:

{
  "binance-enhanced": {
    "command": "docker",
    "args": ["run", "-i", "--rm", "binance-mcp-enhanced"]
  }
}

Testnet Mode

For paper trading and testing:

{
  "binance-testnet": {
    "command": "docker",
    "args": [
      "run", "-i", "--rm",
      "-e", "BINANCE_TESTNET=true",
      "binance-mcp-enhanced"
    ]
  }
}

Enhanced Tools Usage

Calculate Technical Indicators

Calculate indicators for BTCUSDT on 1h timeframe:
- Indicators: ["sma", "ema", "rsi", "macd"]
- Period: 20

Response includes current values and signals (overbought/oversold, bullish/bearish).

Analyze Market

Analyze BTCUSDT market on 4h timeframe with support/resistance levels

Provides comprehensive market analysis including trend, statistics, and key levels.

Compare Symbols

Compare performance of ["BTCUSDT", "ETHUSDT", "BNBUSDT"] on daily timeframe

Returns comparative metrics and rankings.

Original Features

All original features from @snjyor's binance-mcp remain available:

Real-time price data
Order book information
Historical trades
K-line/candlestick data
24hr statistics
Exchange information
Symbol price ticker
And more...

Attribution & License

Original Work: binance-mcp by @snjyor
License: Apache 2.0 License (maintained)
Enhancements: Technical analysis capabilities and security improvements

This enhanced version maintains full compatibility with the original API while adding powerful analysis tools for cryptocurrency trading.

See LICENSE and NOTICE files for complete attribution details.

Contributing

This is a personal enhancement fork. For the original project, please contribute to @snjyor's repository.

Available Tools

15 tools

analyze_marketD

ParametersJSON Schema

Name	Required	Description
`symbol`	Yes	Trading pair symbol, e.g. BTCUSDT
`interval`	Yes	Analysis timeframe
`includeSupport`	No	Include support/resistance levels

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.

calculate_indicatorsD

ParametersJSON Schema

Name	Required	Description
`limit`	No	Number of candles to analyze (default 100)
`period`	No	Period for moving averages (default 20)
`symbol`	Yes	Trading pair symbol, e.g. BTCUSDT
`interval`	Yes	K-line interval
`indicators`	Yes	Technical indicators to calculate

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.

compare_symbolsD

ParametersJSON Schema

Name	Required	Description
`metric`	Yes	Comparison metric
`symbols`	Yes	Symbols to compare (2-5)
`interval`	Yes	Comparison timeframe

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_24hr_tickerD

ParametersJSON Schema

Name	Required	Description
`type`	No	Ticker type, default FULL
`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
`limit`	No	Number of aggregate trades to return, default 500, max 1000
`fromId`	No	Aggregate trade ID to start from
`symbol`	Yes	Trading pair symbol, e.g. BTCUSDT
`endTime`	No	End timestamp (milliseconds)
`startTime`	No	Start timestamp (milliseconds)

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
`limit`	No	Number of trades to return, default 500, max 1000
`fromId`	No	Trade ID to start from
`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_klinesD

ParametersJSON Schema

Name	Required	Description
`limit`	No	Number of K-lines to return, default 500, max 1000
`symbol`	Yes	Trading pair symbol, e.g. BTCUSDT
`endTime`	No	End timestamp (milliseconds)
`interval`	Yes	K-line interval
`timeZone`	No	Time zone, default UTC
`startTime`	No	Start timestamp (milliseconds)

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
`limit`	No	Order book depth, default 100, max 5000
`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_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
`limit`	No	Number of trades to return, default 500, max 1000
`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_rolling_window_tickerD

ParametersJSON Schema

Name	Required	Description
`type`	No	Ticker type, default FULL
`symbol`	No	Trading pair symbol, e.g. BTCUSDT
`symbols`	No	Array of multiple trading pair symbols
`windowSize`	No	Window size, default 1d

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
`type`	No	Ticker type, default FULL
`symbol`	No	Trading pair symbol, e.g. BTCUSDT
`symbols`	No	Array of multiple trading pair symbols
`timeZone`	No	Time zone, default UTC

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
`limit`	No	Number of K-lines to return, default 500, max 1000
`symbol`	Yes	Trading pair symbol, e.g. BTCUSDT
`endTime`	No	End timestamp (milliseconds)
`interval`	Yes	K-line interval
`timeZone`	No	Time zone, default UTC
`startTime`	No	Start timestamp (milliseconds)

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.

15 tool updatesv1.0.2-enhancedAug 9, 2026
- First observedanalyze_market
- First observedcalculate_indicators
- First observedcompare_symbols
- 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

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.7/5.0

Scored 2026-08-09 21:35 across 15 tools

Disambiguation2/5

Several tools have overlapping or confusingly similar purposes, such as the three trade-related tools (get_recent_trades, get_historical_trades, get_aggregate_trades) and the three ticker tools (get_24hr_ticker, get_trading_day_ticker, get_rolling_window_ticker). Without descriptions, agents could easily select the wrong one. get_avg_price and get_price also create ambiguity.

Naming Consistency3/5

Most tools follow a get_ prefix, but then calculate_indicators, analyze_market, and compare_symbols break the pattern with bare verb forms. The convention is mostly consistent within the get_ group but mixed overall.

Tool Count4/5

15 tools is at the upper boundary of well-scoped. The server covers a broad market data API with many similar endpoints, but each endpoint is distinct enough that the count is justifiable. Slightly heavy but not unreasonable.

Completeness4/5

The tool set covers a wide range of market data operations: order book, trades, klines, tickers, price, and even analysis. Missing common endpoints like exchangeInfo or server time, but the core market data surface is largely covered. The analysis tools add extra value.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

James's MCP Server A
io.github.JGPAS
MCP server with quote and live cryptocurrency price tools, local and cloud-deployed transports.
Cryptocurrency Finance
21
Crypto Prices Mcp
io.github.varvararatta
Unlock the power of real-time cryptocurrency data with our Crypto Price Insights MCP server.
Cryptocurrency Finance
2
gainium-mcpOAuth
io.gainium
MCP server for Gainium — manage trading bots, deals, and balances via AI assistants
Cryptocurrency Finance
22
tachyo A
ai.tachyo
Crypto market intelligence, token rug-checks, and wallet verification in one MCP server.
Cryptocurrency Blockchain Finance
242

Related MCP Servers

crypto-indicators-mcp
Cryptocurrency Finance Agent Orchestration
kukapay
A
license
Not graded
quality
F
maintenance
An MCP server providing a range of cryptocurrency technical analysis indicators and strategies.
Updated 9 months ago (2025-12-06 01:07 UTC)
12 npm
130
MIT
Binance MCP Server
Cryptocurrency Finance Autonomous Agents
mixuechu
F
license
B
quality
D
maintenance
A Model Control Protocol (MCP) server that provides cryptocurrency trading interfaces for Binance exchange, enabling functions like real-time price fetching, account balance queries, order placement/cancellation, and automated arbitrage strategies.
Updated a year ago (2025-04-05 02:46 UTC)
9
14
-
crypto-powerdata-mcp
Cryptocurrency Finance Research & Data
veithly
A
license
Not graded
quality
D
maintenance
A comprehensive MCP service for cryptocurrency data acquisition with advanced technical analysis capabilities, supporting 100+ exchanges, 158 TA-Lib indicators, and dual transport protocols (stdio and HTTP/SSE).
Updated a year ago (2025-07-16 08:40 UTC)
5
MIT
bitbank-lab-mcpofficial
Cryptocurrency Finance
bitbankinc
A
license
A
quality
B
maintenance
MCP server for analyzing cryptocurrency markets from bitbank API, enabling technical analysis, charting, and trading via AI clients.
Updated 3 days ago (2026-09-12 06:34 UTC)
33
17 npm
4
MIT

Binance MCP Enhanced - Technical Analysis Edition

What's New

Technical Indicators

Market Analysis

Multi-Symbol Tools

Security Enhancements

Installation

Docker (Recommended)

Local Installation

Configuration

Claude Desktop

Testnet Mode

Enhanced Tools Usage

Calculate Technical Indicators

Analyze Market

Compare Symbols

Original Features

Attribution & License

Contributing

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

bitbank-lab-mcpofficial