Dritan MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRITAN_API_KEY | Yes | Dritan API key |
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 |
|---|---|
| system_check_prereqsA | Check whether required local binaries are installed (currently solana-keygen) and return install commands. |
| auth_statusA | Show current API key status for this MCP session (active source, preview, and onboarding options). |
| auth_set_api_keyA | Set the active Dritan API key for this running MCP process and persist it locally for restart recovery. |
| auth_clear_api_keyA | Clear the active in-memory API key and delete the persisted auth file. Optionally clear DRITAN_API_KEY in this process env. |
| wallet_create_localB | Create a local Solana wallet using solana-keygen and return path + public address. |
| wallet_get_addressA | Get the public address for a local Solana wallet file. |
| wallet_get_balanceA | Get SOL balance for a local wallet address from a Solana RPC endpoint. |
| wallet_transfer_solB | Send SOL from a local wallet to a destination wallet (used in x402 paid key flow). |
| x402_get_pricingB | Get x402 pricing and receiver wallet for paid time-limited API keys. |
| x402_create_api_key_quoteA | Create an x402 payment quote for a time-limited API key (returns quoteId, receiverWallet, and exact SOL amount). |
| x402_create_api_keyC | Claim a paid x402 API key using quoteId and payment transaction signature. |
| dritan_healthB | Check data plane health endpoint via Dritan SDK. |
| market_get_snapshotC | Fetch token market snapshot via Dritan SDK (price/metadata/risk/first-buyers/aggregated). |
| token_searchA | Search tokens by ticker/name and resolve mint addresses (first step for ticker-based chart requests). |
| token_get_priceC | Fetch token price via Dritan (same as market_get_snapshot mode=price). |
| token_get_metadataC | Fetch token metadata via Dritan. |
| token_get_riskA | Fetch token risk via Dritan (same as market_get_snapshot mode=risk). |
| token_get_first_buyersC | Fetch first buyers via Dritan. |
| token_get_aggregatedC | Fetch aggregated token data via Dritan (same as market_get_snapshot mode=aggregated). |
| token_get_deployer_statsC | Fetch token deployer stats via Dritan. |
| token_get_ohlcvC | Fetch OHLCV candles for a token and timeframe. |
| token_get_ohlcv_chartA | Build embeddable chart markdown from token OHLCV candles so agents can render the actual chart inline in chat (resolve ticker with token_search first). Supports line-volume or candlestick charts. |
| wallet_get_performanceD | Fetch wallet performance via Dritan. |
| wallet_get_token_performanceC | Fetch wallet performance for a specific token mint via Dritan. |
| wallet_get_portfolio_chartC | Fetch wallet portfolio chart series via Dritan. |
| wallet_get_portfolio_chart_visualB | Build embeddable line-chart markdown for wallet portfolio history so agents can render a graphical portfolio view inline. |
| wallet_get_summaryC | Fetch basic wallet summary via Dritan. |
| wallet_get_trade_historyC | Fetch wallet trade history via Dritan. |
| wallet_get_holdingsD | Fetch wallet holdings via Dritan. |
| wallet_get_holdings_chartC | Build embeddable holdings allocation chart markdown from wallet holdings so agents can render token balance distribution inline. |
| wallet_get_holdings_pageC | Fetch paginated wallet holdings via Dritan. |
| wallet_get_performance_chartB | Build embeddable wallet PnL chart markdown (history when available, otherwise summary/token PnL bars) for graphical performance views. |
| market_stream_sampleB | Open a DEX websocket stream and collect events for a short duration. |
| wallet_stream_sampleC | Open the wallet websocket stream and collect events for selected wallets. |
| ths_healthB | Check Meteora THS service health. |
| ths_get_scoreC | Fetch THS score for a wallet. |
| ths_get_score_tokens_getC | Fetch THS score for selected token mints using GET. |
| ths_get_score_tokens_postC | Fetch THS score for selected token mints using POST. |
| ths_get_top_walletsB | Fetch paginated top wallets ranked by THS score. |
| swap_buildC | Build an unsigned swap transaction with Dritan. |
| swap_sign_and_broadcastA | Sign a base64 swap transaction with a local wallet and broadcast through Dritan. |
| swap_build_sign_and_broadcastC | Convenience tool: build swap, sign locally with wallet, and broadcast in one call. |
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 42 tools
Several tools have overlapping purposes (e.g., market_get_snapshot vs token_get_aggregated, price, risk; ths_get_score_tokens_get vs post; wallet_get_holdings vs wallet_get_holdings_page). Multiple chart tools could be consolidated. This creates ambiguity for an agent.
Tools mostly follow a domain_verb_noun pattern (e.g., auth_set_api_key, token_get_metadata). However, there are minor inconsistencies like ths_get_score_tokens_get vs ths_get_score_tokens_post where the verb order differs. Overall predictable.
42 tools is on the high side, but they cover a broad domain (auth, market, swaps, tokens, wallets, x402). However, several near-duplicates inflate the count (e.g., chart tools, HTTP method variants). Could be streamlined to ~30 tools.
The tool surface covers key operations for the Dritan ecosystem: authentication, market data, token metadata, swaps, wallet management, THS scoring, and x402 payments. Minor gaps exist, such as no tool to list all tokens or manage swap orders beyond building, but core workflows are supported.