Dexra Trader
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRY_RUN | No | Dry run mode. Only false/0/no/off turn it off. Trades are sent only when DRY_RUN=false, SOLANA_PRIVATE_KEY and JUPITER_API_KEY are all set. | true |
| SLIPPAGE_BPS | No | Jupiter slippage in basis points, 0 to 1000. | 100 |
| ALLOW_CAUTION | No | Let a caution verdict pass. | false |
| DEXRA_API_KEY | Yes | Dexra API key (dxr_…). Without it, paid checks answer 402 and every buy is blocked. | |
| MAX_TRADE_SOL | No | Hard cap per buy in SOL. Larger buys are refused. | 0.05 |
| DEXRA_BASE_URL | No | Dexra API base URL. Point it at a local API for testing. | https://api.dexra.dev |
| JUPITER_API_KEY | No | Jupiter API key. Needed for live trading; in a dry run it adds a Jupiter quote. | |
| SOLANA_PRIVATE_KEY | No | Base58 64-byte Solana secret key. Only for live trading. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_tokenA | Dexra token_deep_check: who really holds the token, linked wallets, authorities and Token-2022 extensions. Returns a verdict (ok, caution, avoid, unknown) with reasons. |
| preflightA | Dexra swap_preflight for this exact swap: price impact, sandwich risk, transfer fees, hooks, mint and freeze authority. Returns a verdict with reasons. |
| fresh_launchesA | Dexra new_launches: tokens launched on Solana in the last N minutes, each with its own verdict and reasons. Windows over 60 minutes cost more. |
| buyA | Buys the token with SOL through Jupiter, only if Dexra's token check and preflight both pass. Dry run unless the operator enabled live trading. status is blocked, dry_run, executed, failed or error; decision.reasons says why. |
| sellA | Sells the token for SOL through Jupiter. Never blocked by a verdict, so a position can always be exited; the preflight verdict is reported. Dry run unless live trading is on. |
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 5 tools
buy, sell, and fresh_launches are unmistakable, but check_token and preflight both return a 'verdict with reasons' and both cover mint/freeze authority, so an agent may hesitate over which to call first. The distinction (token-level vetting vs this-specific-swap risk) is stated but requires reading the descriptions rather than being obvious from names.
The set mixes snake_case verb_noun names (check_token, fresh_launches) with bare single-word actions (preflight, buy, sell). Every name is readable and conventional in trading parlance, but there is no single predictable pattern an agent can pattern-match on.
Five tools is tightly scoped for a swap-execution server: discover, vet, preflight, enter, exit. Every tool maps to a distinct stage of the trading workflow and none feels redundant.
The discover-vet-buy-sell lifecycle is covered, but there is no tool to view open positions, SOL balance, or transaction status, so after a buy the agent has no way to know what it holds — sell's note about 'exiting a position' implies state the surface cannot read. No quote-only or slippage/config operation either.