burn_tokens
Burn/destroy tokens from your balance (only works if token was deployed with burnable=true)
LABSCO SUMMARY
What you can do to a token six months from now is decided by the flags you pass at deploy time.
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.
What it is
A Bitbond Token Tool client covering 11 tools, in front of token deployment and the deployer wallet on each supported chain.
What you get
- 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.
Requirements
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.
Setup effort
One command plus credentials — npx -y token-tool-mcp, then supply credentials
USE CASES
01
Costing a launch before committing funds to it
Check which chains are available, price the deployment with the options you actually want, and confirm the deployer wallet can cover it.
02
Getting a token live with the switches you will need later
Deployment is where mintable, burnable and pausable are decided, along with supply, decimals and the transfer controls. Read the contract back to confirm what shipped.
03
Stopping every transfer while you work out what went wrong
A pausable token can be frozen in one call and released in another, without touching balances.
04
Adjusting supply after the token is already out
Issue more to an address, destroy some of your own balance, or move an amount to another wallet.
11 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
deploy_token
Deploy a new token using Bitbond Token Tool. Supports EVM chains (ERC20, CertiK-audited), Solana (SPL tokens), and Stellar (assets).
estimate_cost
Get the cost to deploy a token on a given chain before committing
get_token_info
Get live on-chain info for any token contract (name, symbol, supply, paused state, owner)
get_wallet_info
Get the deployer wallet address and balance on a given chain
list_chains
List all supported blockchain networks for token deployment
list_deployed_tokens
List all tokens deployed via this MCP server (local registry)
mint_tokens
Mint additional tokens (only works if token was deployed with mintable=true)
pause_token
Pause all token transfers — emergency stop (only works if pausable=true)
transfer_tokens
Transfer tokens from your wallet to another address
unpause_token
Resume token transfers after a pause
BEFORE YOU INSTALL
What to know first
Tools you get
11 tools when we connected; the project documents 17. The six missing are the compliance tools: add_to_whitelist, remove_from_whitelist, get_whitelist, add_to_blacklist, remove_from_blacklist and get_compliance_status. No flag gates them; the npm build likely predates the documented version.
Requires
- npx on PATH
- BITBOND_PRIVATE_KEY in your environment
Where it runs
All 4 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y token-tool-mcpMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"token-tool": {
"command": "npx",
"args": [
"-y",
"token-tool-mcp"
],
"env": {
"BITBOND_PRIVATE_KEY": "<YOUR_BITBOND_PRIVATE_KEY>"
}
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"token-tool": {
"command": "npx",
"args": [
"-y",
"token-tool-mcp"
],
"env": {
"BITBOND_PRIVATE_KEY": "<YOUR_BITBOND_PRIVATE_KEY>"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add token-tool -- npx -y token-tool-mcp
