Transfers, approvals, contract writes and Greenfield payments all return a preview plus a token that a second call has to present, and that token dies after 5 minutes, so an unattended agent cannot drift from reading a balance into spending it. The same behaviour is switched off account-wide by one environment variable, which is worth knowing before you set it.
An EVM client for BNB Chain that also reaches Greenfield object storage and the ERC-8004 identity registry: 45 tools over blocks, balances, transfers, contracts, buckets and agent identities.
- Chain reads: block metadata by number, hash or latest, transaction lookup by hash, gas estimation, chain info and the list of supported networks
- Contract work in both directions — call a view or pure function with a maxResponseSize cap, call a state-changing function, check whether an address is a contract or an EOA, and deploy a new ERC20
- Transfers of native tokens, ERC20, ERC721 and ERC1155, plus spender approvals for a named amount
- A two-step path for anything that moves value: the call returns a preview and a confirmToken, confirm_transfer executes it, and the token expires after 5 minutes
- Greenfield storage: buckets and folders, file upload and download, object listing that returns totalCount and hasMore for paging, and bucket quota usage
- Greenfield payment accounts created, funded, withdrawn from and inspected
- ERC-8004 agent identity: mint an agent NFT against an agentURI, update that URI as the owner, and read back the owner, tokenURI and verified payment wallet
A private key for anything that signs; block, balance and contract-read calls take a network and an address instead. npx on your PATH. BNBCHAIN_MCP_SKIP_TRANSFER_CONFIRMATION set to true removes the preview step.
One command plus a key — npx -y @bnb-chain/mcp@latest, then supply credentials