Where it fits
DeFi users and developers who prepare swap quotes, check safety verdicts, and inspect deployments and ABIs without an API key.
- Prepare a swap quote through the hosted codec.
- Decode a quote and review its safety verdict.
- Run swaps locally with @blazephoenix/mcp and your own RPC.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with BlazePhoenix
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Investigates a question against high-trust primary sources and records the findings in a Markdown file inside the repo. Use it when a topic needs research, docs or API facts need gathering, or reading legwork should go to a background agent.
Show recorded token use, cache reads, and mode attribution for the current Claude Code session.
Improves application speed across the frontend, backend, database, and query layers. Reach for it when a performance target exists, a regression is suspected, Core Web Vitals or load times need work, N+1 queries need fixing, or profiling has exposed a bottleneck.
No skills found
Try a different search term or clear the filters.
Local quote and swap server
Quote and trade execution run through the local npx server with your own RPC via BLAZEPHOENIX_RPC_BASE. The hosted endpoint covers prepare and decode only.
- Set your RPC base
Export BLAZEPHOENIX_RPC_BASE with the RPC endpoint the transactions should run against.
- Run the local server
Start npx -y @blazephoenix/mcp and register that command as a local stdio MCP server.
- Use hosted for codec work only
The hosted https://blazephoenix.xyz/mcp endpoint prepares and decodes quotes; it does not execute swaps.
Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name blazephoenix. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
blazephoenixappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Prepare a swap quote through the hosted codec. Check the result before you give the server more access.
- 3Check permissions.
The provider documents no credential for this endpoint, so there is no scope or token to review. Remove the server when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- The server connects but no tools appear. Confirm the URL and transport, then restart the client.
- The first tool call times out. Try a smaller request and check the provider's status or rate limits.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
BlazePhoenix documentationhttps://blazephoenix.xyz/agents/