Concordia MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOLANA_RPC_URL | No | Solana RPC endpoint URL. This is a live, rate-limited RPC URL provided for convenience. For production use, it's highly recommended to obtain your own dedicated RPC endpoint. | https://mainnet.helius-rpc.com/?api-key=ad83f75e-b1c4-4fbd-b405-866fe3b9c558 |
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 |
|---|---|
| fetchWalletActivityC | Fetches the transaction activity history for a Solana wallet address |
| analyzeWalletC | Analyzes a Solana wallet's DeFi activity and creates a profile with recommendations |
| getTransactionDetailsC | Gets detailed information about a specific Solana transaction by signature |
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 3 tools
The tools have distinct primary purposes: analyzeWallet focuses on DeFi profiling and recommendations, fetchWalletActivity retrieves transaction history, and getTransactionDetails provides specific transaction data. However, there is some overlap as analyzeWallet likely uses transaction data, but the descriptions clarify their different intents well.
The naming is mixed: analyzeWallet and fetchWalletActivity use camelCase, while getTransactionDetails uses a different verb style and structure. This inconsistency makes the set less predictable, though the names remain readable and descriptive of their functions.
With only 3 tools, the server feels thin for a DeFi/Solana wallet analysis domain. While the tools cover key operations, more comprehensive coverage (e.g., for token balances or portfolio tracking) might be expected, making the count borderline for the apparent scope.
The tools provide good coverage for wallet analysis and transaction details, but there are notable gaps. For example, there are no tools for fetching token balances, interacting with DeFi protocols, or updating wallet data, which could limit agent workflows in this domain.