tokensift
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOKENSIFT_CACHE_TTL_S | No | Cache duration in seconds for successful responses. | 30 |
| TOKENSIFT_RAW_MAX_BYTES | No | Maximum bytes of raw response returned when verbose=true; above this raw_truncated is set. | 32768 |
| TOKENSIFT_LIMITER_WAIT_S | No | When a rate limit bucket is empty, the call waits up to this many seconds before returning rate_limited. | 5 |
| TOKENSIFT_NEG_CACHE_TTL_S | No | Cache duration in seconds for invalid_input and not_found errors. | 10 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| honeypot_checkA | simulate a buy and sell of an evm token via honeypot.is and report is_honeypot, buy/sell/transfer tax, gas, risk flags, pair liquidity, contract open-source/proxy status and holder count. chains: ethereum, bsc, base (chain id or alias; supported: ethereum (aliases: eth, 1); bsc (aliases: bnb, 56); base (aliases: 8453); solana (aliases: sol)); for solana use rugcheck_report. no result means the token has no simulated pair yet. verbose=true adds top holders with supply percentages and the raw payload. |
| rugcheck_reportA | fetch rugcheck.xyz's risk report for a solana mint: score and normalised score, named risks with levels, lp locked percentage, token program. verbose=true fetches the full report: mint/freeze authority, top holders with percentages and insider flags, metadata mutability, jupiter verification, and the raw payload. solana only; for evm tokens use honeypot_check. |
| dex_searchA | search dexscreener by ticker, name, token address or pair address and return candidate pairs in upstream relevance order with chain, dex, price, liquidity, fdv, 24h volume and txns, and pair age. tickers are ambiguous: confirm identity by contract address (dex_token_pairs / dex_pair) before any safety check. limit 1-30 (default 10). verbose=true adds the raw payload. |
| dex_token_pairsA | list dexscreener pools for one token contract on one chain, sorted by liquidity descending, with price, liquidity, fdv, volume, txns and pair age. chains: chain id or alias; supported: ethereum (aliases: eth, 1); bsc (aliases: bnb, 56); base (aliases: 8453); solana (aliases: sol). limit 1-30 (default 20). an empty list means dexscreener does not index the token on that chain. verbose=true adds the raw payload. |
| dex_pairA | live snapshot of one dexscreener pair: price, liquidity, fdv, market cap, 24h volume and txns, price change windows, project links and boosts. chains: chain id or alias; supported: ethereum (aliases: eth, 1); bsc (aliases: bnb, 56); base (aliases: 8453); solana (aliases: sol). not_found means no such pair on that chain. verbose=true adds the raw payload. |
| jupiter_pricesA | usd prices for up to 50 solana mints from jupiter price v3 (swap-derived), with liquidity, 24h change and decimals; unknown mints come back with found=false. use as a second price source next to dexscreener. verbose=true adds the raw payload. |
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 6 tools
Tools are mostly distinct: honeypot_check and rugcheck_report clearly separate EVM vs Solana safety checks; dex_search, dex_token_pairs, and dex_pair cover different granularities of pair data. Minor overlap exists between dex_search and dex_token_pairs, but descriptions clarify when each is appropriate.
All tool names use consistent snake_case and follow a predictable pattern: domain-specific prefix (dex_, jupiter_, honeypot_, rugcheck_) plus a clear noun or verb. The naming scheme makes the tool's function obvious and uniform across the set.
Six tools is a well-scoped size for a token research and safety-checking server. Each tool covers a distinct aspect of the workflow (search, pair lookup, pair snapshot, safety verification, pricing) without redundancy or bloat.
The core workflow (find token, verify pair, assess safety, get price) is covered. Minor gaps exist: no EVM-specific price source analogous to jupiter_prices, and dex_token_pairs only queries one chain at a time, requiring multiple calls for cross-chain analysis.