Este proyecto proporciona una herramienta de Protocolo de Contexto de Modelo (MCP) para obtener datos de precios de Bitcoin de Binance. Permite que los modelos de lenguaje de gran tamaño accedan a datos históricos y en tiempo real del mercado de Bitcoin mediante una interfaz estandarizada.
Obtenga datos actuales del ticker de Bitcoin (precio, cambio de 24 horas, volumen, etc.)
Obtenga los mejores precios de oferta y demanda del libro de órdenes
Obtener transacciones recientes
Obtenga datos históricos de precios con intervalos personalizables
Transmita actualizaciones de precios de Bitcoin en tiempo real durante períodos cortos
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 buildPara utilizar esta herramienta con un cliente LLM compatible con MCP:
# Start the MCP server
pnpm startLuego, conecta tu cliente LLM compatible con MCP para interactuar con los datos de Binance.
get_bitcoin_ticker - Obtener datos actuales del ticker de Bitcoin
Parámetros:
symbol (opcional, predeterminado: "BTCUSDT") - Símbolo del par comercial
get_bitcoin_order_book : obtenga los mejores precios de oferta y demanda actuales
Parámetros:
symbol (opcional, predeterminado: "BTCUSDT") - Símbolo del par comercial
get_bitcoin_recent_trades - Obtener transacciones recientes
Parámetros:
symbol (opcional, predeterminado: "BTCUSDT") - Símbolo del par comercial
limit (opcional, predeterminado: 10): número de transacciones a obtener
get_bitcoin_price_history - Obtener datos históricos de líneas k/velas
Parámetros:
symbol (opcional, predeterminado: "BTCUSDT") - Símbolo del par comercial
interval (opcional, predeterminado: "1h") - Intervalo de Kline (1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 1s, 1M)
limit (opcional, predeterminado: 24): número de velas a obtener
get_realtime_bitcoin_price - Obtén actualizaciones de precios en tiempo real
Parámetros:
symbol (opcional, predeterminado: "btcusdt"): símbolo del par comercial en minúsculas
duration (opcional, predeterminado: 5, máximo: 30): duración en segundos para recopilar datos en tiempo real
Una vez conectado a un LLM compatible con MCP, puede utilizar indicaciones como:
"¿Cuál es el precio actual de Bitcoin y el cambio en 24 horas?"
"Muéstrame el diferencial actual entre los precios de oferta y demanda de Bitcoin".
"Analice las últimas 10 transacciones de Bitcoin e identifique cualquier patrón".
"Obtenga el historial de precios de Bitcoin de las últimas 24 horas y explique la tendencia".
"Observa las transacciones de Bitcoin en tiempo real durante 5 segundos y dime si hay más presión de compra o venta".
Para realizar cambios en el proyecto:
Modificar el código fuente en el directorio src
Ejecute pnpm build para compilar el código TypeScript
Pruebe sus cambios con pnpm start
Esta herramienta se proporciona únicamente con fines educativos e informativos. No constituye asesoramiento financiero.
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