base-flash-arb-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 |
|---|---|
| detect_arb_opportunityB | Compare token prices across Uniswap V2, Uniswap V3, and Aerodrome on Base. Find profitable arbitrage routes. |
| get_pool_reservesC | Get reserves/liquidity for a token across all known DEX pools on Base. |
| estimate_flash_profitC | Given two pools with a price difference, estimate flash loan profit after gas. |
| scan_top_tokensC | Scan top traded tokens on Base for arb opportunities using DexScreener. |
| get_price_across_dexesB | Get current price of a token on all available DEXes on Base. |
| check_sandwich_riskC | Analyze a token's recent trades for sandwich attack patterns (bot activity). |
| get_mempool_pendingB | Check pending transactions for a token (front-run detection). Note: Base L2 has minimal public mempool exposure. |
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 7 tools
Each tool has a clearly distinct purpose with no overlap: check_sandwich_risk focuses on attack patterns, detect_arb_opportunity finds profitable routes, estimate_flash_profit calculates profit after gas, get_mempool_pending checks pending transactions, get_pool_reserves retrieves liquidity data, get_price_across_dexes provides price comparisons, and scan_top_tokens scans for opportunities. The descriptions clearly differentiate their functions, making misselection unlikely.
All tool names follow a consistent verb_noun pattern with snake_case, such as check_sandwich_risk, detect_arb_opportunity, and get_pool_reserves. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions across the seven tools.
With 7 tools, the count is well-scoped for the server's purpose of arbitrage and risk analysis on Base. Each tool serves a specific role in the workflow, from detection to estimation and monitoring, without being excessive or insufficient for the domain.
The tool set covers core aspects of arbitrage and risk analysis on Base, including opportunity detection, profit estimation, and monitoring tools. However, there is a minor gap in execution tools (e.g., executing trades or managing positions), which agents might need to work around, but the surface is largely complete for analysis and detection purposes.