Kaspa MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KASPA_NETWORK | No | Network: mainnet, testnet-10, testnet-11. Defaults to mainnet | mainnet |
| KASPA_MNEMONIC | No | BIP39 mnemonic phrase (24 words) | |
| KASPA_PRIVATE_KEY | No | Hex-encoded private key (alternative to mnemonic) | |
| KASPA_ACCOUNT_INDEX | No | BIP44 account index when using mnemonic. Defaults to 0 | 0 |
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 |
|---|---|
| get_my_addressB | Get the Kaspa address derived from the configured private key |
| get_balanceB | Get balance for a Kaspa address (defaults to your wallet address) |
| get_fee_estimateB | Get current fee estimates from the Kaspa network |
| send_kaspaC | Send KAS tokens to a recipient address |
| get_transactionC | Get transaction status and details |
| generate_mnemonicA | Generate a new BIP39 mnemonic phrase and derive the corresponding Kaspa wallet address. Use this to create a new wallet. |
| health_checkB | Check server health: wallet config, address derivation, and API connectivity |
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 7 tools
Each tool has a distinct and clearly defined purpose with no overlap. For example, generate_mnemonic creates a new wallet, get_balance checks funds, send_kaspa transfers tokens, and health_check monitors server status. The descriptions make it easy for an agent to select the correct tool for any task.
All tool names follow a consistent verb_noun pattern using snake_case, such as generate_mnemonic, get_balance, and send_kaspa. This uniformity makes the toolset predictable and easy to navigate, with no deviations in naming conventions.
With 7 tools, the server is well-scoped for wallet and transaction management in the Kaspa domain. Each tool serves a specific function, from wallet creation to transaction handling, without being overly sparse or bloated, making it efficient for typical use cases.
The toolset covers core wallet operations like creation, balance checking, and sending tokens, along with network and health checks. A minor gap is the lack of tools for advanced features such as transaction history or multi-signature support, but agents can perform essential workflows without significant hindrance.