Binance MCP
by UpperMoon0
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BINANCE_API_KEY | No | Binance API key used for signed account requests. | |
| BINANCE_API_SECRET | No | Binance API secret for HMAC signing. Required if using HMAC as the signer. | |
| BINANCE_TRADING_ENABLED | No | Set to 'true' to enable trading operations. Defaults to 'false'. | false |
| BINANCE_PRIVATE_KEY_PATH | No | Path to the Ed25519/RSA private key file for signing. Required if using an asymmetric key. | |
| BINANCE_PRIVATE_KEY_PASSPHRASE | No | Optional passphrase for the private key. |
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 |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/UpperMoon0/Binance-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server