Fetches Bitcoin price data from Binance, allowing access to current ticker data, order book information, recent trades, historical price data, and real-time price updates.
Provides Bitcoin market data including current prices, 24-hour changes, trading volumes, order book information, and historical price trends across different time intervals.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Binance Bitcoin MCP Tool what's the current Bitcoin price and 24-hour change?"
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.
This project provides a Model Context Protocol (MCP) tool for fetching Bitcoin price data from Binance. It allows large language models to access real-time and historical Bitcoin market data through a standardized interface.
Get current Bitcoin ticker data (price, 24h change, volume, etc.)
Get best bid and ask prices from the order book
Fetch recent trades
Get historical price data with customizable intervals
Stream real-time Bitcoin price updates for short durations
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 buildTo use this tool with an MCP-compatible LLM client:
# Start the MCP server
pnpm startThen connect your MCP-compatible LLM client to interact with the Binance data.
get_bitcoin_ticker - Get current Bitcoin ticker data
Parameters:
symbol (optional, default: "BTCUSDT") - Trading pair symbol
get_bitcoin_order_book - Get current best bid and ask prices
Parameters:
symbol (optional, default: "BTCUSDT") - Trading pair symbol
get_bitcoin_recent_trades - Get recent trades
Parameters:
symbol (optional, default: "BTCUSDT") - Trading pair symbol
limit (optional, default: 10) - Number of trades to fetch
get_bitcoin_price_history - Get historical kline/candlestick data
Parameters:
symbol (optional, default: "BTCUSDT") - Trading pair symbol
interval (optional, default: "1h") - Kline interval (1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 1w, 1M)
limit (optional, default: 24) - Number of candles to fetch
get_realtime_bitcoin_price - Get real-time price updates
Parameters:
symbol (optional, default: "btcusdt") - Trading pair symbol in lowercase
duration (optional, default: 5, max: 30) - Duration in seconds to collect real-time data
Once connected to an MCP-compatible LLM, you can use prompts like:
"What is the current Bitcoin price and 24-hour change?"
"Show me the current spread between bid and ask prices for Bitcoin."
"Analyze the last 10 Bitcoin trades and identify any patterns."
"Get Bitcoin price history for the last 24 hours and explain the trend."
"Watch real-time Bitcoin trades for 5 seconds and tell me if there's more buying or selling pressure."
To make changes to the project:
Modify the source code in the src directory
Run pnpm build to compile the TypeScript code
Test your changes with pnpm start
This tool is provided for educational and informational purposes only. It is not financial advice.
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.
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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
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.
MCP server for OpenMM — exposes market data, account, trading, and strategy tools to AI agents
Hosted MCP server for live public-data APIs and Skills for AI agents.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/MilesCool/binance-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server