mcp-server-cex-bn

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is mcp-server-cex-bn?

The mcp-server-cex-bn is a robust server interface designed for executing Binance spot trading operations, allowing users to manage their trading activities efficiently.

how to use mcp-server-cex-bn?

To use the mcp-server-cex-bn, clone the repository, configure your Binance API credentials in a .env file, install the necessary dependencies, and start the server to begin trading.

key features of mcp-server-cex-bn?

  • Securely configure and store Binance API credentials.
  • Execute spot trading operations including LIMIT and MARKET orders.
  • Monitor account balances and manage open orders.
  • Cancel existing orders and track trading activities.

use cases of mcp-server-cex-bn?

  1. Automating cryptocurrency trading on Binance.
  2. Monitoring and managing trading accounts in real-time.
  3. Developing trading bots that interact with Binance's API.

FAQ from mcp-server-cex-bn?

  • Is this server secure for trading?

Yes! It is designed with security best practices, including secure storage of API keys and error handling for common issues.

  • What programming language is used?

The server is built using TypeScript, ensuring type safety and better development experience.

  • Can I use this server for other exchanges?

This server is specifically designed for Binance, but similar implementations can be created for other exchanges.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-
Category
finance

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago