Binance MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crypto-priceC | Get the current price of a cryptocurrency |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as fetching cryptocurrency prices, making it impossible for an agent to confuse it with another tool.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'crypto-price' follows a clear noun-noun pattern that is straightforward and descriptive for its single function.
A single tool is too few for a server named 'Binance MCP Server', which implies broader cryptocurrency exchange functionality. This minimal set feels thin and inadequate for the expected scope, such as trading, account management, or market data beyond just price.
The tool surface is severely incomplete for a Binance server, covering only price retrieval. Obvious gaps include trading operations, balance checks, order management, and other exchange features, which will likely cause agent failures in typical cryptocurrency tasks.