NFT Management
When to Use
- Minting ERC-721 or ERC-1155 tokens
- Buying/selling on OpenSea, Blur, Reservoir
- Resolving and validating NFT metadata
- Creating token-bound accounts (ERC-6551)
- Managing royalty enforcement (EIP-2981)
Prerequisites
- MCP:
nft-metadata-server,blockchain-rpc-server,ipfs-storage-server - Skills: skill-02, skill-08 (verify collection contracts)
Workflow
1. Collection Verification
- Verify contract on explorer; check for verified source
- Confirm standard: ERC-721 (
ownerOf), ERC-1155 (balanceOfwith id) - Check for honeypot patterns (non-transferable after mint, hidden fees)
- Validate royalty config via
royaltyInfo(tokenId, salePrice)
2. Minting
- Resolve metadata URI (IPFS CID or Arweave txid)
- Pin metadata via
ipfs-storage-serverbefore mint - Estimate mint cost including gas
- Execute mint; verify token received
3. Trading
- Use Reservoir API via
nft-metadata-serverfor aggregated listings - Set approval: prefer
setApprovalForAllonly for trusted marketplaces - For high-value sales: use private tx submission (skill-15)
- Verify listing price and currency (ETH, WETH, USDC)
4. Token-Bound Accounts (ERC-6551)
- Deploy TBA registry implementation
- Create account:
createAccount(implementation, chainId, tokenContract, tokenId, salt, initData) - TBA can hold ETH, ERC-20, and other NFTs
- Sign transactions from TBA via ERC-1271
5. Metadata Standards
| Field | Requirement |
|---|---|
name |
Human-readable token name |
description |
Token description |
image |
IPFS/Arweave URI (not HTTP unless pinned) |
attributes |
Array of trait_type/value pairs |
References
knowledge-base/standards/erc721/,erc1155/,erc6551/references/marketplace-apis.md