Binance TypeScript MCP
Related Servers
Alternatives to Binance TypeScript MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides cryptocurrency data tools and resources via an HTTP endpoint. It enables users to fetch real-time market data from Binance, track activity logs, and generate cryptocurrency executive summaries.-
- AlicenseDqualityDmaintenanceMCP service that provides real-time access to Binance cryptocurrency market data, allowing AI agents to fetch current prices, order books, candlestick charts, and trading statistics through natural language queries.1293 npm44Apache 2.0
- AlicenseCqualityDmaintenanceProvides an MCP server that allows large language models to access real-time and historical Bitcoin market data from Binance, including current prices, order book data, recent trades, and price history through a standardized interface.18 npm3MIT
- AlicenseNot gradedqualityDmaintenanceAn HTTP-based Model Context Protocol server that provides tools and resources for accessing real-time cryptocurrency data from the Binance API. It enables users to fetch prices, analyze market changes, and track activity via a streamable endpoint.183 npmMIT
- FlicenseNot gradedqualityDmaintenanceHosted MCP server that provides agent-ready access to Binance APIs, with tools mapped 1:1 to real endpoints, no auth required, supporting crypto trading and market data operations via natural language.-
- FlicenseNot gradedqualityCmaintenanceA local stdio MCP server for Binance Spot, enabling users to query prices, manage orders, and check account info via natural language through the Hermes agent.-
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.