base-token-sniper-mcp
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 |
|---|---|
| watch_launchesA | Get recent token launches from the OBSD LaunchPad on Base. Returns newest first with token address, pool, creator, name, symbol, supply, and launch timestamp. Use this to discover newly deployed tokens to trade. |
| snipe_buyA | Buy a token on the OBSD LaunchPad with ETH via PlatformRouter. 0.5% ETH fee goes to platform treasury. Requires DEPLOYER_PRIVATE_KEY env var. Returns tx hash and tokens received. |
| multi_quoteA | Get buy quotes for multiple tokens at once. Shows how many tokens you'd receive for a given ETH amount across multiple LaunchPad tokens. Useful for comparing opportunities. |
| get_token_safetyA | Check safety metrics for a LaunchPad token. Returns liquidity depth, burn stats, fee rates, age, and a simple safety score. Use before trading to assess risk. |
| get_launch_feedA | Get a feed of token launches since a given timestamp. Useful for polling new launches periodically. Returns only launches newer than the specified time. |
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
The two launch retrieval tools (watch_launches and get_launch_feed) have overlapping purposes; agents might struggle to pick between them. The other tools are distinct and well-separated.
Naming styles are mixed: 'multi_quote' and 'snipe_buy' do not follow the verb_noun pattern seen in 'get_token_safety' and 'get_launch_feed'. This inconsistency makes the toolset feel less predictable.
With exactly 5 tools, the server is well-scoped for a token sniper: discovery, quoting, safety checks, and buying are all covered without unnecessary bloat.
The core workflow of discovering and buying tokens is fully covered. However, there is no sell mechanism or direct token lookup by address, which are minor gaps for a complete sniper tool.