mint_tokens, burn_tokens and pause_token each state the same condition: they work only if the token was deployed with mintable, burnable or pausable set. estimate_cost takes those flags too, so the price of that decision is visible before deploy_token runs. list_deployed_tokens reads a local registry rather than the chain, so it reports what this server deployed; get_token_info is the call that reads a contract's live state regardless of where it came from.
A Bitbond Token Tool client covering 11 tools, in front of token deployment and the deployer wallet on each supported chain.
- Deployment with the options set up front: deploy_token takes name, symbol, decimals, supply and max_supply, the mintable, burnable and pausable switches, blacklist, whitelist and force_transfer controls, a document_uri and a discount_code, and covers EVM chains as ERC20, Solana as SPL tokens and Stellar as assets.
- A cost check before committing: list_chains reports the networks available and estimate_cost prices a deployment on one of them with the burnable, mintable and pausable choices applied.
- Supply operations after launch: mint_tokens issues more to an address, burn_tokens destroys from your balance, and transfer_tokens moves an amount to another address.
- An emergency stop: pause_token halts all transfers on a contract and unpause_token resumes them.
- State you can read back: get_token_info returns name, symbol, supply, paused state and owner live from any contract address, list_deployed_tokens reads the local registry of tokens deployed through this server, and get_wallet_info returns the deployer address and its balance on a chain.
A deployer wallet whose key is held in BITBOND_PRIVATE_KEY, funded on the chain you deploy to — get_wallet_info reports that address and its balance.
One command plus a key — npx -y token-tool-mcp, then supply credentials