transfer_native_token
Transfer native tokens (BNB, ETH, MATIC, etc.) to a specified address using a private key for signing transactions. Supports multiple networks, including BSC and Ethereum.
Instructions
Transfer native tokens (BNB, ETH, MATIC, etc.) to an address
Input Schema
Name | Required | Description | Default |
---|---|---|---|
amount | Yes | Amount to send in BNB (or the native token of the network), as a string (e.g., '0.1') | |
network | No | Network name (e.g. 'bsc', 'opbnb', 'ethereum', 'base', etc.) or chain ID. Supports others main popular networks. Defaults to BSC mainnet. | bsc |
privateKey | No | Private key of the sender account in hex format (with or without 0x prefix). SECURITY: This is used only for transaction signing and is not stored. | 0x5a2b7e4d9c8f1a3e6b0d2c5f4e3d2a1b0c9f8e7d6a5b4c3d2e1f0a9b8c7d6e5f4 |
to | Yes | The recipient address or ENS name (e.g., '0x1234...' or 'vitalik.eth') |
Input Schema (JSON Schema)
You must be authenticated.
Other Tools from bnbchain-mcp
- approve_token_spending
- check_nft_ownership
- estimate_gas
- get_address_from_private_key
- get_block_by_hash
- get_block_by_number
- get_chain_info
- get_erc1155_balance
- get_erc1155_token_uri
- get_erc20_balance
- get_erc20_token_info
- get_latest_block
- get_native_balance
- get_nft_balance
- get_nft_info
- get_supported_networks
- get_transaction
- get_transaction_receipt
- is_contract
- read_contract
- resolve_ens
- transfer_erc1155
- transfer_erc20
- transfer_native_token
- transfer_nft
- write_contract
Related Tools
- @bnb-chain/bnbchain-mcp
- @TermiX-official/bsc-mcp
- @bnb-chain/bnbchain-mcp
- @bnb-chain/bnbchain-mcp
- @mcpdotdirect/evm-mcp-server