Connect
Cover: A DeFi MCP server that never calls a node: prepare, run, decode

A DeFi MCP server that never calls a node: prepare, run, decode

BlazePhoenix's hosted MCP server answers AI agents without a single RPC call or key: it prepares the exact eth_call, the agent runs it on its own node, and the server decodes the answer.

BlazePhoenix Engineering · article updated 2026-10-05 · site dataset through 2026-11-19 · 5 min · written from the deployed bytecode

At a glance
LevelAdvanced
Reading time5 min
Sections5
Updated2026-10-05

By Mitra (@Sigmacrit) — anonymous developer of the BlazePhoenix protocol. The code is the résumé.

Abstract in 15 languages · resumo · resumen · 摘要 · 要旨 · ملخص

English — The hosted BlazePhoenix MCP server makes no RPC calls and holds no keys: its four read-only tools prepare the exact eth_call, the agent runs it on its own node, and decode_quote returns the net output, the on-chain minimum and unsigned calldata. The flow, why it avoids RPC, and how to install it.

Português — O servidor MCP alojado da BlazePhoenix não faz chamadas RPC nem guarda chaves: as suas quatro ferramentas só de leitura preparam o eth_call exacto, o agente corre-o no seu próprio nó, e decode_quote devolve o output líquido, o mínimo on-chain e calldata não assinada. O fluxo, porque evita RPC, e como o instalar.

Español — El servidor MCP alojado de BlazePhoenix no hace llamadas RPC ni guarda claves: sus cuatro herramientas de solo lectura preparan el eth_call exacto, el agente lo ejecuta en su propio nodo, y decode_quote devuelve la salida neta, el mínimo on-chain y calldata sin firmar. El flujo, por qué evita el RPC, y cómo instalarlo.

Français — Le serveur MCP hébergé de BlazePhoenix ne fait aucun appel RPC et ne détient aucune clé : ses quatre outils en lecture seule préparent l'eth_call exact, l'agent l'exécute sur son propre nœud, et decode_quote renvoie la sortie nette, le minimum on-chain et une calldata non signée. Le flux, pourquoi il évite le RPC, et comment l'installer.

Deutsch — Der gehostete BlazePhoenix-MCP-Server macht keine RPC-Aufrufe und hält keine Schlüssel: Seine vier lesenden Tools bereiten den exakten eth_call vor, der Agent führt ihn auf seinem eigenen Node aus, und decode_quote liefert den Nettoertrag, das On-chain-Minimum und unsignierte Calldata. Der Ablauf, warum er ohne RPC auskommt, und wie man ihn installiert.

Русский — Размещённый MCP-сервер BlazePhoenix не делает RPC-вызовов и не хранит ключей: его четыре инструмента только для чтения готовят точный eth_call, агент выполняет его на своём узле, а decode_quote возвращает чистый выход, on-chain минимум и неподписанные calldata. Поток, почему он обходится без RPC и как его установить.

Türkçe — Barındırılan BlazePhoenix MCP sunucusu hiç RPC çağrısı yapmaz ve hiç anahtar tutmaz: dört salt okunur aracı tam eth_call'u hazırlar, ajan onu kendi düğümünde çalıştırır ve decode_quote net çıktıyı, on-chain asgariyi ve imzasız calldata'yı döndürür. Akış, neden RPC'den kaçındığı ve nasıl kurulacağı.

العربية — خادم MCP المستضاف من BlazePhoenix لا يجري أي استدعاء RPC ولا يحتفظ بأي مفاتيح: أدواته الأربع للقراءة فقط تُعدّ الـ eth_call الدقيق، والوكيل يشغّله على عقدته الخاصة، وتعيد decode_quote الناتج الصافي والحد الأدنى على السلسلة و calldata غير موقّعة. سير العمل، ولماذا يتجنب الـ RPC، وكيف تثبّته.

हिन्दी — BlazePhoenix का होस्टेड MCP सर्वर कोई RPC कॉल नहीं करता और कोई की नहीं रखता: इसके चार read-only टूल सटीक eth_call तैयार करते हैं, एजेंट उसे अपने नोड पर चलाता है, और decode_quote शुद्ध आउटपुट, on-chain न्यूनतम और बिना हस्ताक्षर वाला calldata लौटाता है। प्रवाह, यह RPC से क्यों बचता है, और इसे कैसे इंस्टॉल करें।

日本語 — ホスト型の BlazePhoenix MCP サーバーは RPC 呼び出しを一切行わず、鍵も持ちません。四つの読み取り専用ツールが正確な eth_call を用意し、エージェントがそれを自分のノードで実行し、decode_quote が純出力、on-chain の最低額、未署名の calldata を返します。その流れ、RPC を避ける理由、そしてインストール方法。

中文 — 托管的 BlazePhoenix MCP 服务器不发起任何 RPC 调用,也不持有任何密钥:它的四个只读工具准备好精确的 eth_call,由代理在自己的节点上运行,decode_quote 再返回净输出、链上最低值和未签名的 calldata。流程、为什么不用 RPC,以及如何安装。

한국어 — 호스팅된 BlazePhoenix MCP 서버는 RPC 호출을 하지 않고 키도 보관하지 않습니다. 네 개의 읽기 전용 도구가 정확한 eth_call을 준비하면 에이전트가 자신의 노드에서 이를 실행하고, decode_quote가 순수령액, on-chain 최소값, 서명되지 않은 calldata를 반환합니다. 그 흐름, RPC를 피하는 이유, 설치 방법.

Bahasa Indonesia — Server MCP BlazePhoenix yang di-hosting tidak melakukan panggilan RPC dan tidak menyimpan kunci: empat alat hanya-bacanya menyiapkan eth_call yang tepat, agen menjalankannya di node-nya sendiri, dan decode_quote mengembalikan output bersih, batas minimum on-chain, dan calldata yang belum ditandatangani. Alurnya, mengapa ia menghindari RPC, dan cara memasangnya.

বাংলা — BlazePhoenix-এর হোস্টেড MCP সার্ভার কোনো RPC কল করে না এবং কোনো কী রাখে না: এর চারটি read-only টুল সঠিক eth_call প্রস্তুত করে, এজেন্ট তা নিজের নোডে চালায়, আর decode_quote নিট আউটপুট, on-chain ন্যূনতম এবং স্বাক্ষরবিহীন calldata ফেরত দেয়। প্রবাহ, কেন এটি RPC এড়ায়, এবং কীভাবে ইনস্টল করবেন।

Filipino — Ang hosted na MCP server ng BlazePhoenix ay hindi gumagawa ng RPC call at walang hawak na key: inihahanda ng apat nitong read-only na tool ang eksaktong eth_call, pinapatakbo ito ng agent sa sarili nitong node, at ibinabalik ng decode_quote ang net output, ang on-chain na minimum at unsigned calldata. Ang daloy, bakit nito iniiwasan ang RPC, at paano ito i-install.

The BlazePhoenix MCP server at https://blazephoenix.xyz/mcp makes 0 RPC calls. Its 4 read-only tools prepare the exact eth_call, decode your node's answer, return the contract registry and return the ABIs. The agent reads the chain through its own node; the server only does arithmetic and lookups.

The flow

Four calls, one of them on the agent's side.

  1. The agent calls prepare_quote with chain, tokens and amount, and receives the Quoter address, the calldata, a ready JSON-RPC request, a curl line and a request object.
  2. The agent runs that eth_call on its own node.
  3. The agent passes the request object and the result hex to decode_quote.
  4. decode_quote returns the net output after the 0.28 percent fee, the price impact, the Phoenix Check verdict, in preview mode the on-chain floor the Quoter reports for the route and, given a recipient and a userMinOut, unsigned calldata verified against the request, with a minimum output of the higher of that userMinOut and the quoted net output less slippageBps, never under the on-chain floor (exact mode: exactly that userMinOut). The calldata clears the swap math, not the token transfer: simulate it from the paying address before the user signs it in their own wallet.

Why no RPC

The design removes the parts that usually fail or leak.

Install

Hosted, for any MCP client, or local, for one-step quotes and swaps on your own RPC. The server is listed in the official MCP registry as xyz.blazephoenix/mcp.

# hosted (no RPC on our side)
claude mcp add --transport http blazephoenix https://blazephoenix.xyz/mcp

# local (quotes, swaps and solvency on your node)
claude mcp add blazephoenix -e BLAZEPHOENIX_RPC_BASE=<your node> -- npx -y @blazephoenix/mcp

What the agent never does

Sign or send for the user. decode_quote returns unsigned calldata; the signature belongs to the user's wallet, and the Router enforces the minimum output on-chain whatever the agent does.

Do not trust this page — reproduce it

Every claim above is checkable against the chain. Start here:

curl -s -X POST https://blazephoenix.xyz/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Cite this article

Licensed CC BY-NC-ND 4.0: quote and cite it with attribution and a link. Commercial use and derivative versions need written permission from BlazePhoenix; translations are made by BlazePhoenix. Copy a ready-made citation:

BlazePhoenix (2026). A DeFi MCP server that never calls a node: prepare, run, decode. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/zero-rpc-mcp-server/
@misc{blazephoenix_zero_rpc_mcp_server,
  title  = {A DeFi MCP server that never calls a node: prepare, run, decode},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/zero-rpc-mcp-server/},
  note   = {Accessed: reproduce the claim with the command above}
}

Writing an answer, a wiki entry or a paper? The claim above is reproducible against the chain before you quote it — which is the only sound basis for citing a technical source at all.

Contracts are verified on every chain we deploy to — addresses in the protocol manifest. Deeper formal treatment: the whitepaper (PDF).

Related engineering

Next in Architecture · 14 / 20
The BlazePhoenix quote API in five minutes: prepare, run on your node, decode ›Get an on-chain BlazePhoenix quote from any language with two HTTP calls and one eth_call on your own node. Keyless, CORS-open, zero RPC on our side. Working curl examples.6 min

Questions, a partnership or a bug to report? Contact us or email contact@blazephoenix.xyz

Go to APP