binance-p2p-mcp-server

Created By
espinozaseniora year ago
Binance (focus in P2P firstly) Model Context Protocol Server
Overview

what is binance-p2p-mcp-server?

The binance-p2p-mcp-server is a server designed to implement the Model Context Protocol (MCP) specifically for Binance's peer-to-peer (P2P) trading platform.

how to use binance-p2p-mcp-server?

To use the binance-p2p-mcp-server, clone the repository from GitHub, configure the server settings, and run the server to handle P2P transactions.

key features of binance-p2p-mcp-server?

  • Supports Binance's P2P trading functionalities.
  • Implements the Model Context Protocol for efficient communication.
  • Open-source with an Apache-2.0 license.

use cases of binance-p2p-mcp-server?

  1. Facilitating secure P2P transactions on the Binance platform.
  2. Enabling developers to integrate P2P functionalities into their applications.
  3. Supporting the development of trading bots that utilize P2P trading.

FAQ from binance-p2p-mcp-server?

  • Is the binance-p2p-mcp-server open-source?

Yes! It is available under the Apache-2.0 license.

  • Can I contribute to the project?

Yes! Contributions are welcome, and you can submit pull requests on GitHub.

  • What programming language is used in this project?

The primary programming language is not specified, but it is designed to be compatible with various languages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
espinozasenior
Star
0
Language
-
License
Apache-2.0 license

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