MIST.cash MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_LOG_LEVEL | No | Log level for the MCP server | info |
| STARKNET_NETWORK | Yes | The Starknet network to use (mainnet or sepolia) | mainnet |
| STARKNET_RPC_URL | Yes | URL of the Starknet RPC provider (e.g., https://ztarknet-madara.d.karnot.xyz) | |
| CHAMBER_CONTRACT_ADDRESS | No | Address of the Chamber contract (Required for Madara if not using Mainnet) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generar_secreto_transaccionC | Generate a transaction secret for private payments. Creates a cryptographic secret using a claiming key and recipient address. |
| obtener_assets_transaccionA | Fetch assets from a transaction. WARNING: This shows assets even if already spent. Use verificar_existencia_transaccion for accurate verification. |
| verificar_existencia_transaccionB | Verify if a transaction exists with specific assets. For fully private transactions where assets are not publicly visible. |
| calcular_hash_transaccionC | Calculate the unique hash of a transaction using transaction parameters. |
| obtener_configuracion_chamberB | Get Chamber contract configuration including contract address, network, and supported tokens. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Chamber Contract Information | Static information about the MIST.cash Chamber contract |
| Transaction Details | Details for a specific transaction by hash |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: calcular_hash_transaccion computes a transaction hash, generar_secreto_transaccion creates a cryptographic secret, obtener_assets_transaccion fetches assets, obtener_configuracion_chamber retrieves contract configuration, and verificar_existencia_transaccion verifies transaction existence. The descriptions explicitly differentiate their functions, preventing agent misselection.
All tool names follow a consistent Spanish verb_noun pattern (e.g., calcular_hash_transaccion, generar_secreto_transaccion) using snake_case throughout. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 5 tools, this server is well-scoped for its apparent domain of transaction and contract operations in MIST.cash. Each tool serves a specific, non-trivial function, and the count is neither too sparse nor bloated, fitting typical expectations for a focused MCP server.
The tool set covers core transaction operations (hash calculation, secret generation, asset fetching, existence verification) and contract configuration retrieval, providing a solid foundation. A minor gap exists in lacking tools for creating or modifying transactions, but agents can likely work around this for basic query and verification tasks.