Connects to the Binance API to provide real-time pricing information for cryptocurrency symbols.
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 TypeScript MCP What is the current price of BTC?"
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 implements a Model Context Protocol server using TypeScript.
Build:
npm installAdd to .vscode/mcp.json:
{
"servers": {
"binance-ts-mcp": {
"command": "npx",
"args": [
"-y",
"/FULL_PATH_GOES_HERE/typescript_mcp"
]
}
},
"inputs": []
}Type "what's the BTC price now" into Copilot, and you'll see it use this mcp to answer
Debug with npx @modelcontextprotocol/inspector node src/binance_mcp.ts
Optionally, publish it to npmjs.com
npm login
npm publish
the mcp will still run locally when using npmjs, but it will be downloaded
remotely running MCPs would mean going along the lines of https://github.com/cloudflare/ai/tree/main/demos/remote-mcp-auth0
Related MCP server: Binance Cryptocurrency MCP
This project has a tool that connects to the Binance API to give the price of a given crypto symbol.
MCP resources provide easy access to files, database tables, API results, e.g. this project writes MCP activity log to a file resource.
@modelcontextprotocol/sdk: Core MCP functionality
zod: Runtime type checking
typescript: Development dependency for TypeScript compilation
@types/node: Type definitions for Node.js
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Unlock the power of real-time cryptocurrency data with our Crypto Price Insights MCP server.
Official CoinMarketCap MCP server: real-time crypto prices, market cap, rankings and exchange data.
Real-time market events, sentiment, and technical analysis as MCP tools, backed by real data.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ber4444/typescript-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
