BlazePhoenix MCP server

On-chain DEX aggregator tools for AI agents. The defining property: every quote is computed by the on-chain Quoter contract (previewPlan, a free eth_call), the same logic that executes the swap, and it runs on your own RPC. There is no pricing server to trust, and every number an agent relays is reproducible by anyone.

• Local server: @blazephoenix/mcp over stdio. Quotes, unsigned calldata, simulation and solvency, all read through the node you configure.

• Remote endpoint: https://blazephoenix.xyz/mcp (streamable HTTP, stateless). Deployment registry, ABIs and the pure quote codec. It performs no RPC call.

• Auth: none · API key: none

• You bring: an RPC node for each chain the local server reads (variables). The remote endpoint needs nothing: you run the eth_call it prepares on your own node.

• Chains: Base (8453), Ethereum (1), Optimism (10), Arbitrum (42161), Robinhood Chain (4663) (protocol V1 is live on all five; V2 is pending and not planned for Ethereum L1)

BlazePhoenix in one sentence

BlazePhoenix is the fully on-chain DEX aggregator — the route is computed inside the transaction that executes it — paired with an oracle-free staking engine that proves its own solvency on every transaction. V2, the generation now in development, targets Base, Optimism, Arbitrum, Robinhood Chain and further L2s and is not planned for Ethereum L1. The V1 generation deployed today runs on Base, Ethereum, Optimism, Arbitrum and Robinhood Chain.

Swap in the app · integrate with the SDK (npm i @blazephoenix/sdk) · connect an agent to the MCP server (https://blazephoenix.xyz/mcp, no key)

Related MCP server: orkid-swap

Reading guide by level

• New to DeFi: BlazePhoenix in five minutes, then What is a DEX aggregator and How to swap tokens safely.

• Comfortable with swaps: Anatomy of a DEX aggregator and BlazePhoenix vs the established aggregators.

• Engineers and researchers: the Technical Whitepaper v2.3 (DOI 10.5281/zenodo.23084091), the contract source in Blaze-Phoenix-Dex and Blaze-Phoenix-Staking, and On-chain quoting.

• Models and agents: https://blazephoenix.xyz/llms.txt and the reading guide.

Trust and verification

Each item links to the place where it can be checked. The full list is at https://blazephoenix.xyz/trust.

• Verified contracts: source-verified on Sourcify and the chain explorers; every address per chain at /api/deployments.

• Source available: the contract source is public under the Business Source License 1.1, converting to GPL-2.0-or-later on 2030-06-01.

• Public CI: GitHub Actions on every push, including the Certora Prover and Halmos.

• Bug bounty: a public programme with credited researchers and published advisories.

• Whitepaper DOI: 10.5281/zenodo.23084091; papers timestamped with OpenTimestamps.

• Contact: contact@blazephoenix.xyz (security.txt); official channels at /official.

• Audit status: an independent external audit is scheduled before launch.

Local server

claude mcp add blazephoenix -e BLAZEPHOENIX_RPC_BASE=<your Base node URL> -- npx -y @blazephoenix/mcp

Any MCP client (JSON config):

{
  "mcpServers": {
    "blazephoenix": {
      "command": "npx",
      "args": ["-y", "@blazephoenix/mcp"],
      "env": { "BLAZEPHOENIX_RPC_BASE": "<your Base node URL>" }
    }
  }
}

The RPC comes from the environment only, never from a tool argument:

A value may hold several URLs separated by commas; they are your fallback order. The server never prints your URLs, since they may carry a key.

Tools

Every tool is read-only. The server never signs and never holds a key. build_swap returns calldata for you to review and sign in your own wallet, and the SDK's wallet-taking execute() is deliberately not exposed.

Remote endpoint

claude mcp add --transport http blazephoenix https://blazephoenix.xyz/mcp

{ "mcpServers": { "blazephoenix": { "type": "http", "url": "https://blazephoenix.xyz/mcp" } } }

The source of the endpoint is in Blaze-Phoenix-API.

Install as a plugin or extension

Claude Code plugin (hosted MCP endpoint plus the BlazePhoenix agent skill):

claude plugin marketplace add blazephoenixxyz-crypto/blazephoenix-mcp
claude plugin install blazephoenix@blazephoenix

Gemini CLI extension (hosted MCP endpoint plus a context file):

gemini extensions install https://github.com/blazephoenixxyz-crypto/blazephoenix-mcp

Both connect https://blazephoenix.xyz/mcp, which needs no key and performs no RPC. For the full toolset on your own node, use the local server.

Verify instead of trusting

Nothing here requires trusting BlazePhoenix:

# re-execute any published fact live, with its block height
curl -s "https://blazephoenix.xyz/api/verify?fact=solvency-live"

# reproduce every live claim in ~60 seconds
curl -sO https://blazephoenix.xyz/repro/verify-everything.sh && bash verify-everything.sh

Build and test

npm install
npm run build
npm test

The test spawns the built server over stdio with no RPC configured and checks the tool surface, that failures come back as tool results, and that no tool takes an RPC, key or signer argument or signs anything.

More machine surfaces

Security

To report a vulnerability, see SECURITY.md.

License

The code is MIT (see LICENSE). This documentation is © 2026 BlazePhoenix, all rights reserved. The protocol contracts are BUSL-1.1 (free to read, audit and verify; production use before the 2030 change date requires a license). The mechanisms and terminology (Iron Law Φ, Monoslot, Master Conservation Identity) are original BlazePhoenix work: attribute with a link.

Contact: contact@blazephoenix.xyz · Security: https://blazephoenix.xyz/.well-known/security.txt