Sonar-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HELIUS_API_KEY | Yes | Your Helius API key | |
| SOLANA_NETWORK | No | The Solana network to use (devnet or mainnet) | devnet |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_slotA | Get the current slot the node has reached, at the given commitment level. |
| get_epoch_infoB | Get current epoch progress: absolute slot, block height, epoch, slot index/total. |
| get_healthA | Check whether the RPC node is healthy. |
| get_sol_balanceA | Get the SOL balance (in lamports and SOL) for a wallet address. |
| get_token_accounts_by_ownerA | List SPL token accounts owned by a wallet, optionally filtered to one mint. |
| get_transactionA | Get full details for a transaction by its signature. |
| get_signatures_for_addressB | Get recent transaction signatures involving an address. |
| get_token_supplyA | Get total supply and decimals for an SPL token mint. |
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 8 tools
Each tool targets a distinct resource or query, but get_slot and get_epoch_info overlap slightly since both report the current slot. The descriptions clarify their different scopes, so ambiguity is minimal.
All tool names follow a consistent verb_noun pattern with the 'get_' prefix. Variations like get_epoch_info or get_token_supply still adhere to the pattern, and there is no mixing of styles.
Eight tools is well within the ideal range and appropriate for a read-only Solana RPC server. Each tool provides a needed query without bloat or redundancy.
The set covers core Solana read operations: slot, epoch, health, balances, token accounts, transactions, signatures, and supply. Missing queries like get_block or get_program_accounts are minor gaps, and the server's scope is clearly read-only.