Binance TypeScript MCP
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_priceD | – |
| get_price_price_changeD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| activity_log |
TDQS
Scored across 2 tools
The two tools appear to serve nearly identical purposes related to price data, with 'get_price' and 'get_price_price_change' likely overlapping significantly in functionality. Without descriptions, it's impossible to distinguish their intended use cases, leading to high ambiguity and potential misselection.
Both tools use snake_case naming, which is consistent, but the naming pattern is unclear—'get_price' suggests a simple price fetch, while 'get_price_price_change' is redundant and poorly structured. The inconsistency in verb-object clarity makes the naming only moderately readable.
With only 2 tools, this server feels severely under-scoped for a Binance integration, which typically involves trading, account management, and market data beyond just price. The count is too low to cover the expected domain, making it inappropriate for comprehensive use.
The tool surface is extremely incomplete for a Binance server, lacking essential operations like placing orders, checking balances, or accessing other market data. With only price-related tools, there are significant gaps that will cause agent failures in typical cryptocurrency trading or analysis workflows.