该项目提供了一个模型上下文协议 (MCP) 工具，用于从币安获取比特币价格数据。它允许大型语言模型通过标准化接口访问实时和历史比特币市场数据。
获取当前比特币行情数据（价格、24 小时变化、交易量等）
从订单簿中获取最佳买入价和卖出价
获取近期交易
获取可自定义间隔的历史价格数据
短时间内实时获取比特币价格更新
Related MCP server: Binance Cryptocurrency MCP
# Clone the repository
git clone https://github.com/yourusername/binance-mcp.git
cd binance-mcp
# Install dependencies
pnpm install
# Build the project
pnpm build要将此工具与 MCP 兼容的 LLM 客户端一起使用：
# Start the MCP server
pnpm start然后连接与 MCP 兼容的 LLM 客户端以与 Binance 数据进行交互。
get_bitcoin_ticker - 获取当前比特币行情数据
参数：
symbol （可选，默认：“BTCUSDT”）- 交易对符号
get_bitcoin_order_book - 获取当前最佳买入价和卖出价
参数：
symbol （可选，默认：“BTCUSDT”）- 交易对符号
get_bitcoin_recent_trades - 获取最近的交易
参数：
symbol （可选，默认：“BTCUSDT”）- 交易对符号
limit （可选，默认值：10） - 要获取的交易数量
get_bitcoin_price_history - 获取历史 K 线/K 线数据
参数：
symbol （可选，默认：“BTCUSDT”）- 交易对符号
interval (可选，默认: "1h") - K线间隔 (1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 1w, 1M)
limit （可选，默认值：24） - 要获取的蜡烛数量
get_realtime_bitcoin_price - 获取实时价格更新
参数：
symbol （可选，默认值：“btcusdt”）- 小写交易对符号
duration （可选，默认值：5，最大值：30）- 收集实时数据的持续时间（秒）
一旦连接到与 MCP 兼容的 LLM，您可以使用如下提示：
“比特币现在的价格和24小时变化是多少？”
“向我显示比特币当前买入价和卖出价之间的差价。”
“分析最近 10 笔比特币交易并找出任何模式。”
“获取过去 24 小时的比特币价格历史并解释趋势。”
“观察比特币实时交易 5 秒钟，然后告诉我买入压力还是卖出压力更大。”
要对项目进行更改：
修改src目录下的源代码
运行pnpm build来编译 TypeScript 代码
使用pnpm start测试您的更改
此工具仅供教育和信息之用。并非财务建议。
Get the current price of a cryptocurrency
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Get' implies a read-only operation, the description doesn't address important behavioral aspects like rate limits, data freshness (how current is 'current'), error conditions, or authentication requirements. For a tool with zero annotation coverage, this represents a significant gap in transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is perfectly concise - a single sentence that states exactly what the tool does without any wasted words. It's front-loaded with the core functionality and contains no redundant information. Every word earns its place in this minimal but complete statement of purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. While concise, it doesn't provide enough information about behavior, parameter usage, or return values. The agent would need to guess about important aspects like response format, error handling, and parameter constraints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage, with one undocumented parameter 'symbol'. The description mentions 'cryptocurrency' which provides some context for what 'symbol' might represent, but doesn't specify format (e.g., 'BTC', 'bitcoin', ticker symbols), valid values, or examples. This minimal compensation for the complete lack of schema documentation is insufficient.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get') and resource ('current price of a cryptocurrency'), making the purpose immediately understandable. It's specific enough to distinguish this tool from potential alternatives like historical price tools or exchange rate calculators. However, it doesn't explicitly differentiate from non-existent siblings, so it doesn't reach the highest score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or limitations. It simply states what the tool does without context about appropriate use cases or constraints. Since there are no sibling tools mentioned, this omission is less critical but still leaves the agent without usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0crypto-priceScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or deviations.
One tool is too few for a server named 'Binance Bitcoin MCP Tool', which suggests broader cryptocurrency functionality. This minimal set severely limits the server's scope and utility.
The tool surface is severely incomplete for the implied domain of Binance Bitcoin operations. It only provides price checking, lacking essential functions like trading, account management, or market data analysis.
MCP server exposing the Backtest360 engine API as tools for AI agents.
Unlock the power of real-time cryptocurrency data with our Crypto Price Insights MCP server.
Trading MCP server for AI agents, with live market data, account reads and controlled execution.
MCP server for OpenMM — exposes market data, account, trading, and strategy tools to AI agents