kaspa-script-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| disassemble_scriptA | Disassemble a Kaspa (rusty-kaspa v2.1.0 / Toccata) script from hex into opcodes and data pushes, exactly as the engine's parser walks it. Flags disabled/reserved opcodes and truncated pushes. |
| estimate_script_costA | Estimate a Kaspa script's compute cost: script units, compute-mass grams, share of the 500,000-gram block compute limit, and the minimum per-input compute budget to commit. Approximate; use it to size a compute budget before signing and to avoid ExceededCommittedScriptUnits. |
| explain_script_errorA | Explain a rusty-kaspa txscript error message (e.g. 'script units exceeded...', 'stack contains N unexpected items', 'ZK Integrity: ...', disabled-opcode, push-encoding errors) in plain terms with a concrete fix. |
| lookup_opcodeA | Look up a Kaspa opcode by hex code (e.g. '0xa8') or by name (e.g. 'OpSHA256'). Returns code, name, disabled/illegal status. |
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 clearly distinct purpose: disassembling scripts, estimating cost, explaining errors, and looking up opcodes. There is no meaningful overlap between any of the four tools.
All tool names follow a consistent verb_noun snake_case pattern: disassemble_script, estimate_script_cost, explain_script_error, lookup_opcode. This makes the toolset predictable and easy for an agent to navigate.
Four tools is an appropriately scoped size for a focused diagnostic utility server. Each tool handles a distinct part of the script analysis workflow without bloat or redundancy.
The toolset covers the full diagnostic lifecycle for Kaspa scripts: disassembly, cost estimation, error explanation, and opcode reference. There are no obvious dead ends for the server's apparent purpose.