MantraChain MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MNEMONIC | Yes | The mnemonic seed phrase for the wallet to use | |
| CUSTOM_NETWORKS | No | JSON string containing additional network configurations |
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 |
|---|---|
| bank-sendC | Send tokens to another address. Supports sending multiple coins in one transaction. |
| get-balanceB | Get balance of an address (defaults to your own address if none provided) |
| delegateC | Delegate/Stake tokens to a validator |
| undelegateC | Undelegate/Unstake tokens from a validator |
| claim-rewardsC | Claim rewards for a specific validator |
| get-validatorsC | Get all validators |
| get-delegationsC | Get current staking information for an address |
| get-available-rewardsC | Get all available rewards for an address |
| get-account-infoC | Get current account information |
| get-block-infoC | Get block information |
| query-networkA | Execute a generic network gRPC Gateway query against chain APIs when you cannot find the required information from other tools. You MUST first check the available query/service by reading the openapi specification from the resource |
| ibc-transferC | Send tokens via IBC transfer. |
| contract-queryB | Query a smart contract by executing a read-only function |
| contract-executeC | Execute a function on a smart contract that changes state |
| dex-get-poolsB | Get all available liquidity pools from the DEX |
| dex-find-routesA | Find available swap routes between two tokens - must first check two tokens are available in the DEX pools by using |
| dex-simulate-swapA | Simulate a token swap to get expected outcome without executing it - must first check two tokens are available in the DEX pools by using |
| dex-swapA | Execute a token swap on the DEX - must first check two tokens are available in the DEX pools by using |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| networks - show available networks where the key is the network name and value is network configuration including rpcEndpoint, chainId, prefix, denom, gasPrice, isMainnet, defaultNetwork, displayDenom, displayDenomExponent, explorerUrl |
TDQS
Scored across 18 tools
Most tools have distinct purposes, but there is some overlap between get-account-info and get-balance, and between get-available-rewards and claim-rewards, which could cause minor confusion. The DEX tools are well-differentiated with clear dependencies, and other tools like delegate/undelegate and contract-execute/contract-query are clearly separate.
The naming follows a consistent verb-noun pattern with hyphens (e.g., bank-send, get-balance, dex-swap), making it predictable and readable. There are minor deviations like query-network being more verbose and ibc-transfer using an acronym, but overall the pattern is maintained across most tools.
With 18 tools, the count is slightly high but reasonable for a blockchain server covering banking, staking, DEX, contracts, and IBC. It provides comprehensive functionality without being overwhelming, though it borders on the upper limit of typical scoping.
The tool set offers complete coverage for the blockchain domain, including core operations like sending tokens, staking/delegating, querying contracts, DEX swaps, and IBC transfers. It includes both read and write operations, with no obvious gaps, and even provides a fallback query-network tool for extended functionality.