transfer_nft
Transfer ERC721 NFTs between wallets using the EVM MCP Server. Requires the owner’s private key, NFT contract address, token ID, and recipient address to securely sign and execute the transaction.
Instructions
Transfer an NFT (ERC721 token) from one address to another. Requires the private key of the current owner for signing the transaction.
Input Schema
Name | Required | Description | Default |
---|---|---|---|
network | No | Network name (e.g., 'ethereum', 'optimism', 'arbitrum', 'base', 'polygon') or chain ID. Most NFTs are on Ethereum mainnet, which is the default. | |
privateKey | Yes | Private key of the NFT owner account in hex format (with or without 0x prefix). SECURITY: This is used only for transaction signing and is not stored. | |
toAddress | Yes | The recipient wallet address that will receive the NFT | |
tokenAddress | Yes | The contract address of the NFT collection (e.g., '0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D' for Bored Ape Yacht Club) | |
tokenId | Yes | The ID of the specific NFT to transfer (e.g., '1234') |
Input Schema (JSON Schema)
You must be authenticated.
Other Tools from EVM MCP Server
- approve_token_spending
- check_nft_ownership
- estimate_gas
- get_address_from_private_key
- get_balance
- get_block_by_number
- get_chain_info
- get_erc1155_balance
- get_erc1155_token_uri
- get_erc20_balance
- get_latest_block
- get_nft_balance
- get_nft_info
- get_supported_networks
- get_token_balance
- get_token_balance_erc20
- get_token_info
- get_transaction
- get_transaction_receipt
- is_contract
- read_contract
- resolve_ens
- transfer_erc1155
- transfer_erc20
- transfer_eth
- transfer_nft
- transfer_token
- write_contract
Related Tools
- @mcpdotdirect/evm-mcp-server
- @mcpdotdirect/evm-mcp-server
- @SailFish-Finance/educhain-ai-agent-kit
- @NaniDAO/agentek
- @mcpdotdirect/evm-mcp-server