Hosted MCP server/Finance

BlazePhoenix MCP server

Hosted at blazephoenix.xyz·Streamable HTTP

BlazePhoenix is a keyless remote MCP server for an on-chain DEX aggregator. The hosted endpoint prepares a swap quote to run on your own RPC, decodes it with a safety verdict, and reads deployments and ABIs. Quote and trade execution require the local @blazephoenix/mcp server with BLAZEPHOENIX_RPC_BASE set to your RPC, so the hosted and local paths do different jobs.

blazephoenix.xyz Streamable HTTP No authentication Server not checked yet Reviewed 2026-11-16
About

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.

Install

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.

  1. Set your RPC base

    Export BLAZEPHOENIX_RPC_BASE with the RPC endpoint the transactions should run against.

  2. Run the local server

    Start npx -y @blazephoenix/mcp and register that command as a local stdio MCP server.

  3. 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.

Connection

Endpoint and configuration

Endpoint
https://blazephoenix.xyz/mcp
Host
blazephoenix.xyz · /mcp
Transport
Streamable HTTP
Authentication
No authentication
Server name
blazephoenix
Listing type
Community or directory listing

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.

Verification

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.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that blazephoenix appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Prepare a swap quote through the hosted codec. Check the result before you give the server more access.

  3. 3
    Check 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.

Server not checked yet

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.

Troubleshooting

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.
Safety

Before you connect

Remote means provider access
  • 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.
Review path

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.

Reference

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/