Recta MCP Server

Start here. Call Recta before your agent moves stablecoins or BTC from one blockchain to another (a bridge or cross-chain transfer): give it the route you would use anyway, and it answers, for free, whether a cheaper route exists at the same chain state and proves the saving. If there is none, nothing is charged. Networks: arbitrum, arc, avalanche, base, bitcoin_l1, bnb_chain, ethereum, hyperevm, ink, linea, monad, optimism, polygon, robinhood_chain, solana_mainnet, tron_mainnet, unichain. Assets: BTC, USDC, USDC_BINANCE_PEG, USDG, USDT, USDT_BINANCE_PEG, USDT_OP_BRIDGED. The exact corridors are in the service descriptor. Returns the full guide (llms.txt): what Recta is, the fee (5 % of the verified saving, nothing if none) and the call flow.

Call first, before a cross-chain stablecoin or BTC transfer: whether Recta covers the corridor, which routes it compares, which route you can declare as yours, and the contracts a route would touch. Unsigned, free, never reveals a route or a saving.

Step 1 of a free quote for a cross-chain transfer. Computes the exact message the agent's EVM wallet must sign (EIP-191 personal_sign) for one Recta request, and the headers to send. Holds no key and calls nothing. Then call recta_send_signed_request with the same method, path, idempotency_key, body and issued_at, plus the signature. Start with POST /v1/golden-corridor/commercial-evaluations (body: recta_request_template; its "sender" must be the signing address). If you have no wallet tool that can personal_sign, this server cannot sign for you: No signing code needed: the npm package @recta/client builds, checks and signs the request for you, and @recta/mcp (`npx -y @recta/mcp`, key in RECTA_PRIVATE_KEY of a dedicated wallet, kept on your machine) is a local MCP server that does it as tools. Evaluations are free and need no funds.

Returns the full body of the evaluation request for a corridor, an amount and the route you would use anyway (baseline_provider): you fill only your sender, recipient and gas ceilings, then sign it with recta_prepare_signed_request and recta_send_signed_request.

How many recorded decisions on this corridor found a saving against each route you could declare (counts and dates only). Unsigned and free; use it to decide whether a signed evaluation is worth it.

Step 2: sends the request signed by the agent's own wallet to a Recta route and returns its HTTP status and JSON body. POST /v1/golden-corridor/commercial-evaluations returns, free, the cheapest provable route against the route the agent would use anyway, or an abstention. Executing a decision's route creates a fee of 5 % of the verified saving, capped by the permit the agent signs; no saving, no fee.

Call to check whether a planned cross-chain transfer is covered: the supported corridors (source and destination networks and assets), the bridges compared (Across, CCTP, Stargate, USDT0 and others), amount ranges, limits and the JSON Schema of every request and response.

Call before relying on Recta in a run: whether it is ready to evaluate now, and its contract version.

Unsigned trial of an evaluation: send the evaluation request body (from recta_request_template, with your sender and recipient filled) and get whether a cheaper provable route exists for this exact transfer, the saving (lower bound, USDC) and Recta's 5 % of it. Names no route, stores nothing, charges nothing; 3 a day per address. To get the route, sign the same body with recta_prepare_signed_request and recta_send_signed_request.