minter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WOC_BASE | No | WhatsOnChain base URL | mainnet WOC |
| MINTER_WIF | No | Use an existing minter key instead of the generated file | |
| WALLET_URL | No | BSV Desktop apps API URL | http://127.0.0.1:3321 |
| MINTER_HOME | No | Where the minter's key lives | ~/.stas-minter |
| WALLET_ORIGIN | No | Origin sent to the wallet. Must be non-admin so the spending prompt appears. | http://localhost:8080 |
| ALLOW_UNCONFIRMED | No | Let a mint spend the funding tx's change without waiting a confirmation | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| minter_statusA | Check whether the minter can mint: its funding address and spendable balance, and whether BSV Desktop is running, signed in, and on which network. Read-only, spends nothing. Call this first. |
| minter_fundA | Top up the minter from the user's own BSV Desktop wallet. The wallet will show a spending-authorization prompt that the user must approve by hand. Waits for the funding to become spendable. |
| mint_tokenA | Mint one token into the wallet and register it so it appears in Assets within seconds (no Refresh needed). Requires the minter to be funded — check minter_status first. |
| mint_activate_bsv21A | Activate a BSV-21 token id with GorillaPool so WOC and overlay indexers surface it. Only needed for external discovery — the wallet already shows the token without this. Polls for the fee address, then pays it 2000 sats. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clear, distinct purpose: status checks readiness, fund supplies the minter, mint_token creates a token, and mint_activate_bsv21 handles external discovery. No overlapping responsibilities.
All tools share the 'minter_' prefix, but the suffixes mix nouns (status), verbs (fund), and verb+object patterns (mint_token, mint_activate_bsv21). The consistent prefix helps, but the style is not uniform.
Four tools perfectly cover the minter's lifecycle: check, fund, mint, and activate. Neither sparse nor bloated for the stated purpose.
The expected workflow is fully covered: verify status, fund if needed, mint a token, and activate for external visibility. There are no obvious dead ends or missing operations for the domain.