BlazePhoenix MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLAZEPHOENIX_RPC_ETH | No | A node for Ethereum (1). A value may hold several URLs separated by commas, which are used as the fallback order. | |
| BLAZEPHOENIX_RPC_URL | No | One node, used for every chain it serves. Use either this or the per-chain variables, not both. A value may hold several URLs separated by commas, which are used as the fallback order. | |
| BLAZEPHOENIX_RPC_BASE | No | A node for Base (8453). A value may hold several URLs separated by commas, which are used as the fallback order. | |
| BLAZEPHOENIX_RPC_ARBITRUM | No | A node for Arbitrum (42161). A value may hold several URLs separated by commas, which are used as the fallback order. | |
| BLAZEPHOENIX_RPC_OPTIMISM | No | A node for Optimism (10). A value may hold several URLs separated by commas, which are used as the fallback order. | |
| BLAZEPHOENIX_RPC_ROBINHOOD | No | A node for Robinhood Chain (4663). A value may hold several URLs separated by commas, which are used as the fallback order. |
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 |
|---|---|
| get_quoteA | Quote a swap on-chain through YOUR RPC: net output after the fee, the minimum the Router enforces, price impact and the Phoenix Check verdict (ok / caution / danger / blocked; it fails closed). Set exact=true for an execution-grade dry-run of every leg. |
| build_swapA | Quote a swap and return verified UNSIGNED calldata for the Router, with the minimum output and deadline baked in. Nothing is signed or sent: review it, then sign in your own wallet. |
| simulate_swapA | Build the swap, then dry-run it from the given account with an eth_call on your node. Returns the plan and the simulation. Nothing is signed or sent. |
| check_solvencyB | Live staking solvency read from the chain: isSolvent() and the decoded solvency() struct. Defaults to Base. |
| get_token_infoB | Symbol, decimals and name of a token, read from the chain through your RPC. |
| get_deploymentsB | The versioned deployment registry: Core, Hub, Solver, Quoter and Router addresses per chain and protocol version. |
| verify_deploymentB | Check that the registry addresses for a chain and version match what is deployed on-chain, through your RPC. |
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
The three swap tools overlap: build_swap builds calldata, simulate_swap builds and dry-runs, and get_quote with exact=true also performs an execution-grade dry-run. Descriptions help distinguish intended use, but an agent could still reasonably confuse which tool to call for a quote versus a simulation.
All tool names follow a consistent snake_case verb_noun pattern: build_swap, get_quote, simulate_swap, check_solvency, get_token_info, get_deployments, verify_deployment. There are no mixed conventions or vague standalone verbs.
Seven tools is well-scoped for a focused DeFi swap and deployment-verification server. Each tool covers a distinct part of the quote/build/simulate/verify lifecycle without excessive surface area.
The server covers swap quoting, calldata building, simulation, token metadata, solvency checking, and deployment registry verification. Minor gaps remain around token approvals, balances, or gas estimation, but core workflows can be completed through the exposed tools.