io.github.bitbond/token-tool
NPM · TOKEN-TOOL-MCP · SCANNED SEP 20
Deploy compliant ERC-20 tokens from any AI agent. 17 tools, 10 networks, CertiK-audited.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects toml 3.0.0, reached via @stellar/stellar-sdk > toml. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 211 of 215 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 192 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 792 tokens (~72/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy_token" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.bitbond/token-tool MCP server?
io.github.bitbond/token-tool runs locally as an npm package, launched with npx -y token-tool-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · token-tool-mcp
claude mcp add bitbond-token-tool -- npx -y token-tool-mcp
{
"mcpServers": {
"bitbond-token-tool": {
"command": "npx",
"args": [
"-y",
"token-tool-mcp"
]
}
}
} {
"servers": {
"bitbond-token-tool": {
"command": "npx",
"args": [
"-y",
"token-tool-mcp"
]
}
}
} codex mcp add bitbond-token-tool -- npx -y token-tool-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bitbond-token-tool": {
"type": "local",
"command": [
"npx",
"-y",
"token-tool-mcp"
],
"enabled": true
}
}
} openclaw mcp add bitbond-token-tool --command npx --arg -y --arg token-tool-mcp
mcp_servers:
bitbond-token-tool:
command: "npx"
args: ["-y", "token-tool-mcp"] {
"McpServers": {
"bitbond-token-tool": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"token-tool-mcp"
]
}
}
} assistant mcp add bitbond-token-tool -t stdio -c npx -a -y token-tool-mcp
{
"mcpServers": {
"bitbond-token-tool": {
"command": "npx",
"args": [
"-y",
"token-tool-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/token-tool-mcp@1.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 5 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-3gc7-fjrx-p6mg | CVE-2025-3194 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| GHSA-528h-pc64-c93x | CVE-2026-71429 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-82x6-q7mm-w9cf | CVE-2026-77465 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-v5mp-jgw5-2x6j | CVE-2026-63376 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L | yes |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 211 packages
| Packages resolved | 211 |
|---|---|
| Deprecated | 3 |
| Stale | 65 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
burn_tokens ~63
Burn/destroy tokens from your balance (only works if token was deployed with burnable=true)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to burn (human-readable) |
| chain | string | yes | Chain the token is on |
| contract_address | string | yes | Token contract address |
No output schema declared.
No examples provided.
deploy_token ~277
Deploy a new token using Bitbond Token Tool. Supports EVM chains (ERC20, CertiK-audited), Solana (SPL tokens), and Stellar (assets).
| Name | Type | Req | Description |
|---|---|---|---|
| blacklist | boolean | – | Enable blacklist — block specific addresses |
| burnable | boolean | – | Allow burning/destroying tokens |
| chain | string | yes | Chain to deploy on (e.g. "ethereum", "polygon", "base", "sepolia") |
| decimals | string | – | Token decimals (default: 18) |
| discount_code | string | – | Bitbond discount code if you have one |
| document_uri | string | – | URI to legal document or prospectus |
| force_transfer | boolean | – | Allow owner to force-transfer tokens (compliance) |
| max_supply | string | – | Maximum total supply cap |
| mintable | boolean | – | Allow minting more tokens after deployment |
| name | string | yes | Token name (e.g. "My Token") |
| pausable | boolean | – | Allow pausing all transfers (emergency stop) |
| supply | string | yes | Initial token supply as a number (e.g. "1000000") |
| symbol | string | yes | Token symbol/ticker (e.g. "MTK") |
| whitelist | boolean | – | Enable whitelist — only approved addresses can hold tokens |
No output schema declared.
No examples provided.
estimate_cost ~84
Get the cost to deploy a token on a given chain before committing
| Name | Type | Req | Description |
|---|---|---|---|
| burnable | boolean | – | Include burnable feature |
| chain | string | yes | Chain name (e.g. "ethereum", "polygon", "base", "sepolia") |
| mintable | boolean | – | Include mintable feature |
| pausable | boolean | – | Include pausable feature |
No output schema declared.
No examples provided.
get_token_info ~56
Get live on-chain info for any token contract (name, symbol, supply, paused state, owner)
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain the token is on |
| contract_address | string | yes | Token contract address (0x...) |
No output schema declared.
No examples provided.
get_wallet_info ~34
Get the deployer wallet address and balance on a given chain
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain to check balance on |
No output schema declared.
No examples provided.
list_chains ~18
List all supported blockchain networks for token deployment
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_deployed_tokens ~34
List all tokens deployed via this MCP server (local registry)
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Filter by chain (optional) |
No output schema declared.
No examples provided.
mint_tokens ~71
Mint additional tokens (only works if token was deployed with mintable=true)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to mint (human-readable) |
| chain | string | yes | Chain the token is on |
| contract_address | string | yes | Token contract address |
| to | string | yes | Address to receive minted tokens |
No output schema declared.
No examples provided.
pause_token ~46
Pause all token transfers — emergency stop (only works if pausable=true)
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain the token is on |
| contract_address | string | yes | Token contract address |
No output schema declared.
No examples provided.
transfer_tokens ~70
Transfer tokens from your wallet to another address
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to transfer (human-readable, e.g. "1000") |
| chain | string | yes | Chain the token is on |
| contract_address | string | yes | Token contract address |
| to | string | yes | Recipient wallet address |
No output schema declared.
No examples provided.
unpause_token ~39
Resume token transfers after a pause
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain the token is on |
| contract_address | string | yes | Token contract address |
No output schema declared.
No examples provided.
What is the io.github.bitbond/token-tool MCP server?
io.github.bitbond/token-tool is an MCP server listed in the public MCP registry as io.github.bitbond/token-tool. Deploy compliant ERC-20 tokens from any AI agent. 17 tools, 10 networks, CertiK-audited. This page covers its npm package (token-tool-mcp).
Is the io.github.bitbond/token-tool MCP server safe to use?
io.github.bitbond/token-tool scores 77 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.bitbond/token-tool MCP server expose?
io.github.bitbond/token-tool exposes 11 tools: list_chains, estimate_cost, deploy_token, get_token_info, list_deployed_tokens, and 6 more. Their descriptions and schemas cost roughly 792 tokens of context every time the server is loaded.
Is the io.github.bitbond/token-tool MCP server still maintained?
io.github.bitbond/token-tool is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.bitbond/token-tool MCP server under?
io.github.bitbond/token-tool declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.