Solscan MCP Server
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_transactionA | Get details of a Solana transaction from Solscan |
| get_accountC | Get details of a Solana account from Solscan |
| get_account_transactionsB | Get recent transactions of a Solana account from Solscan |
| get_account_transfersB | Get SPL transfers of a Solana account from Solscan |
| get_account_defi_activitiesB | Get DeFi activities (dextrading) of a Solana account from Solscan |
| get_account_nft_activitiesC | Get NFT activities of a Solana account from Solscan |
| get_account_tokensB | Get tokens held by a Solana account from Solscan |
| get_account_nftsB | Get NFTs held by a Solana account from Solscan |
| get_account_stake_accountsB | Get stake accounts held by a Solana account from Solscan |
| get_token_metaC | Get metadata of a token from Solscan |
| get_token_holdersC | Get holders of a token from Solscan |
| get_token_listC | Get list of top tokens from Solscan |
| get_token_trendingC | Get trending tokens from Solscan |
| get_token_priceB | Get current price of a token from Solscan (via metadata) |
| get_token_transfersB | Get transfers of a token from Solscan |
| get_chain_infoA | Get current chain info (latest block/slot) from Solscan |
| get_block_detailC | Get details of a specific block |
| get_block_transactionsC | Get transactions in a specific block |
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 18 tools
Each tool targets a distinct resource and action: transaction, account sub-types (transactions, transfers, defi, nft, tokens, nfts, stake), token sub-types (meta, holders, list, trending, price, transfers), chain info, and block detail/transactions. No two tools appear to serve the same purpose.
All tool names follow the consistent get_<resource>_<subtype> pattern, with get_ prefix used throughout. Even get_transaction and get_chain_info fit the pattern as resource-only names. No camelCase or mixed conventions.
18 tools is a reasonable number for a blockchain explorer server covering transactions, accounts, tokens, chain, and blocks. Each tool has a clear place, and the count does not feel bloated or sparse.
The server covers the main read-only operations for Solana exploration: transactions, account details and activities, token information, block data, and chain info. Minor gaps like missing token price history or validator info, but the core surface is solid.