BNB Chain과 다른 EVM 호환 네트워크와 상호 작용하는 강력한 툴킷은 자연 언어 처리 및 AI 지원을 통해.

묘사

BNBChain MCP는 AI 전원 인터페이스를 통해 블록체인 네트워크와 원활한 상호 작용을 가능하게 하는 모델 Context Protocol 구현입니다. 블록 체인 개발, 스마트 계약 상호 작용 및 네트워크 관리를위한 포괄적 인 도구 및 리소스를 제공합니다.

핵심 단위

프로젝트는 몇몇 핵심 단위로 편성됩니다:

• **블록 **: Query 및 블록체인 블록 관리 -Contracts: 스마트 컨트랙트와 상호작용
• Network: 네트워크 정보 및 관리
• ** NFT **: NFT (ERC721/ERC1155) 가동
• **토큰 **: 토큰 (ERC20) 운영
• 번역: 거래 관리
• Wallet: 지갑 운영 및 관리 -Common: 공유 유틸리티 및 유형
• **그린 필드 **: Greenfield Network의 지원 파일 관리 운영, 업로드, 다운로드 및 파일 관리 및 버킷
• 곧 추가 기능 (Greenfield, Swap, Bridge 등)

BNBChain MCP (Model Context Protocol)

A powerful toolkit for interacting with BNB Chain and other EVM-compatible networks through natural language processing and AI assistance.

Description

BNBChain MCP is a Model Context Protocol implementation that enables seamless interaction with blockchain networks through AI-powered interfaces. It provides a comprehensive set of tools and resources for blockchain development, smart contract interaction, and network management.

Core Modules

The project is organized into several core modules:

• Blocks: Query and manage blockchain blocks
• Contracts: Interact with smart contracts
• Network: Network information and management
• NFT: NFT (ERC721/ERC1155) operations
• Tokens: Token (ERC20) operations
• Transactions: Transaction management
• Wallet: Wallet operations and management
• Common: Shared utilities and types
• Greenfield: Support file management operations on Greenfield network including, uploading, downloading, and managing files and buckets
• Additional features coming soon (Greenfield, Swap, Bridge, etc.)
• Agents (ERC-8004): Register and resolve on-chain AI agent identities (ERC-8004 Trustless Agents) on BSC and BSC Testnet
• DappBay: Read-only access to DappBay, the official BNB Chain dApp registry: check whether a website belongs to a listed dApp, look up official profiles, search and rank dApps

Important Notes

We do not recommend deploying this MCP Server on the public internet. (1) The SSE endpoint has no authentication—anyone who can reach it can use the server. (2) There is no centralized service that custodies private keys or funds; keys and signing are the responsibility of the client. If you still need to deploy it publicly, add an authentication layer in front (e.g. API keys, JWT, or a reverse proxy with auth), or deploy a keyless version that only exposes read-only or non-sensitive tools.

Credentials: Prefer setting PRIVATE_KEY in the MCP server environment. Do not pass the private key in tool parameters when avoidable, as it may be stored in conversation history, client logs, or request logs and lead to exposure.

Transfer and payment confirmation

Transfer and payment tools (e.g. transfer_native_token, transfer_erc20, approve_token_spending, transfer_nft, transfer_erc1155, gnfd_deposit_to_payment, gnfd_withdraw_from_payment, gnfd_create_payment_account) use a preview-then-confirm flow by default so that no funds move until the user explicitly confirms.