
BlazePhoenix
Actively maintained
≈ 25visits/mo
Little sign of use · estimate, read Oct 15, 2026
- For
- Traders and integrators swapping tokens on-chain across Base, Ethereum, Optimism and Arbitrum, self-custodially
- Activity
- Actively maintainedrelease 9 days ago · site updated 2 days ago
- Company
- since 2026per their site
- Used for
- get a swap quote that can be reproduced at a given block
- swap tokens without registration or handing over custody
- verify a quote independently through your own node
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsblazephoenix.xyz ↗
- Founded2026per their site ↗
- Domain since2025domain registered
- Privacy policy updated2026-08-30privacy policy ↗
- Security contactsecurity.txt
These are BlazePhoenix's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP serverxyz.blazephoenix/mcpverified in the MCP registry
- Stateanswers, 4 toolschecked 2026-10-15
- Address to connectblazephoenix.xyz/mcp
- OpenAPI spec12 pathsthe spec ↗
- API docsblazephoenix.xyz/apithe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use BlazePhoenix for?
Sign in to leave a noteWhat is BlazePhoenix?
Routes token swaps on-chain via contract-resident discovery, quoting, splitting and multi-hop assembly, reproducible at any block.
Who is BlazePhoenix for?
Traders and integrators swapping tokens on-chain across Base, Ethereum, Optimism and Arbitrum, self-custodially
Do people use BlazePhoenix?
Little sign of use: ≈ 25 visits/mo · estimate, 2026-10.
Is BlazePhoenix still maintained?
Actively maintained: release 9 days ago · site updated 2 days ago.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.