Recta Preflight

● Active

io.github.RectaBuild/preflight

Free check before a cross-chain USDC/USDT transfer: total cost, arrival time, proven cheaper route

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "preflight": {
      "url": "https://api.recta.build/preflight/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http preflight https://api.recta.build/preflight/mcp
VS Code
code --add-mcp '{"name":"preflight","type":"http","url":"https://api.recta.build/preflight/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Crypto & Web3
Version
1.0.0
Registry
active
Published
11/17/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Mostly fine: Recta Preflight is maintained, hosted endpoint answering without a key.

Maintained
Active
Last commit 3 days ago (Nov 18, 2026), 0 open issues.
Official registry
Active
Published as io.github.RectaBuild/preflight in the official MCP registry, version 1.0.0.
Source
No licence found
Public repository, but GitHub reports no recognised licence (0 stars). Check the README before shipping it in a product.
Runs
Hosted by the publisher
Your client talks to api.recta.build: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 00:07 UTCStatus history & uptime →
● Working170 msprotocol 2025-06-18vRECTA_COMMERCIAL_EVALUATION_CONTRACT_V23tools

The endpoint answered the MCP handshake as "Recta Preflight" and listed 5 tools. Answering since Nov 18, 2026.

Context cost ≈ 1.9k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 5 tools.

Tools (5)

  • recta_preflight9 params

    Call before any cross-chain USDC/USDT transfer. Give the corridor and the amount (and, optionally, baseline_provider: the route you would use; without it Recta compares against lifi, LI.FI's own quote, or across where LI.FI does not apply). Returns, for your route, its estimated total cost in USDC and when it arrives; and, when Recta proves a cheaper route, the saving (a proven lower bound), Recta's 5 % fee, that route's total cost and arrival (the route itself is not named) and execute_via_recta: sign the same request to get the route. No wallet and no address needed (sender, recipient, constraints and gas ceilings are filled when absent and listed in `assumed`; your own sender gives the most exact figure). Stores nothing, charges nothing; 3 a day per IP address.

    Show parameters
    • source_networkstringrequiredLowercase network as in the service descriptor, e.g. base, ethereum, arbitrum.
    • source_assetstringrequiredUppercase asset, e.g. USDC.
    • destination_networkstringrequired
    • destination_assetstringrequired
    • amountstringrequiredHow much of source_asset to send, in whole tokens (not cents, not wei): "100" with USDC means 100 USDC. Minimum 3.5 for stablecoins (about 3.5 USD). No maximum.
    • baseline_providerstringOptional: the route you would use without Recta, e.g. lifi, across, stargate_v2, cctp_v2_standard (recta_fit_check lists the ones a corridor admits). Absent: li
    • senderstringOptional: your own sending address, for the most exact figure.
    • recipientstringOptional: the receiving address.
    • bodyobjectAlternative to the fields above: the whole evaluation request body (from recta_request_template), as a JSON object.
  • recta_fit_check4 params

    Call first, before a cross-chain stablecoin 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.

    Show parameters
    • source_networkstringrequiredLowercase network as in the service descriptor, e.g. base, ethereum, arbitrum.
    • source_assetstringrequiredUppercase asset, e.g. USDC.
    • destination_networkstringrequired
    • destination_assetstringrequired
  • recta_request_template8 params

    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.

    Show parameters
    • source_networkstringrequiredLowercase network as in the service descriptor, e.g. base, ethereum, arbitrum.
    • source_assetstringrequiredUppercase asset, e.g. USDC.
    • destination_networkstringrequired
    • destination_assetstringrequired
    • amountstringrequiredHow much of source_asset to send, in whole tokens (not cents, not wei): "100" with USDC means 100 USDC. Minimum 3.5 for stablecoins (about 3.5 USD). No maximum.
    • baseline_providerstringrequiredThe route you would use without Recta (see recta_fit_check's declarable_baselines).
    • guarantee_classstring
    • latency_classstring
  • recta_prepare_signed_request4 params

    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`) is a local MCP server that does it as tools: without a key it offers only the free fit check and trial; with RECTA_PRIVATE_KEY of a dedicated wallet (kept on your machine) it signs too. Evaluations are free and need no funds. Paying a fee needs the fee in USDC on Base and a USDC allowance to Permit2 (an ERC-20 approve of USDC to Permit2). If the transfer itself starts from USDC on Base, the wallet needs the transfer amount plus the fee.

    Show parameters
    • methodenumrequired
    • pathstringrequiredA signed route: /v1/golden-corridor/commercial-evaluations[/{result_id}[/execution-artifact|/fee-authorization|/execution]], /v1/golden-corridor/commercial-accr
    • idempotency_keystringRequired by POST /v1/golden-corridor/commercial-evaluations.
    • bodystringThe exact JSON body text, byte for byte as it will be sent. Empty for GET.
  • recta_send_signed_request7 params

    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, a decision (whether a cheaper route than the one the agent would use anyway is proven, and the saving) or an abstention; GET /v1/golden-corridor/commercial-evaluations/{result_id}/execution-artifact then asks for the fee ceiling's signature and, once it is signed, returns the route's transactions. 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.

    Show parameters
    • methodenumrequired
    • pathstringrequired
    • idempotency_keystring
    • bodystring
    • signerstringrequired
    • issued_atintegerrequired
    • signaturestringrequired

Checked by Serverdex with a plain initialize + tools/list call to api.recta.build/preflight/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 18, 2026
Stars
0
Forks
0
Last push
Nov 18, 2026
License
—

TypeScript

From the README

Recta Preflight for AI agents that move stablecoins between blockchains: before a bridge transfer, ask Recta whether a cheaper route exists at the same chain state. Free when there is none; otherwise exactly 5 % of the saving verified on chain. The agent keeps at least 95 % of every verified saving. • Docs for agents: https://api.recta.build/llms.txt • MCP server (Streamable HTTP, no API key): https://api.recta.build/mcp • OpenAPI: https://api.recta.build/openapi.json • Wallet allowlist for agent wallets: https://api.recta.build/v1/golden-corridor/wallet-policy • Coverage check (unsigned, free): https://api.recta.build/v1/golden-corridor/fit?sourcenetwork=ethereum&sourceasset=USDC&destinationnetwork=arbitrum&destinationasset=USDC Recta never holds keys or funds: your agent signs and sends every transaction itself. Client package packages/client is @recta/client: evaluate, authorize the fee, execute and report from your agent's own wallet, with local checks before every signature. Published to npm from this repository with provenance. Local MCP server packages/mcp is @recta/mcp: a local MCP server over the client, so Claude, Cursor or any MCP agent runs the same flow with its own key, which stays on the machine. Execution is off until the operator turns it on; then each transfer is capped (RECTAMAXAMOUNT, default 1000 tokens) and goes only to the wallet itself or an address the operator lists (RECTAALLOWEDRECIPIENTS), checked before anything is signed.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://api.recta.build/preflight/mcp

The most-starred Crypto & Web3 servers in the index, with their live-check result.

ServerStarsLast pushLive check
Oh My Posh Validator23,772Nov 2026Working
Solana MCP by Vybe2,728Oct 2026Working
Solana MCP by Vybe2,728Oct 2026Working
Oracle3 prediction-market agent tools569Nov 2026Local / not checked
Flyto Core483Nov 2026Local / not checked

Recta Preflight: questions people ask

Is Recta Preflight a remote or a local MCP server?
According to its entry in the official MCP registry, Recta Preflight ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Recta Preflight need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is Recta Preflight safe to use?
Mostly fine: Recta Preflight is maintained, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: No licence found; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Recta Preflight still maintained?
Active: the repository's last commit 3 days ago. Last push Nov 18, 2026, 0 GitHub stars. Read from GitHub on Nov 18, 2026.
What tools does Recta Preflight expose?
5 tools as listed by the server itself during the live check, including recta_preflight, recta_fit_check, recta_request_template, recta_prepare_signed_request, recta_send_signed_request. The full list with parameters is in the Live check section above.
How do I add Recta Preflight to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. RectaProven cheaper USDC bridge route for AI agents (Across, CCTP, Stargate); fee 5% of verified saving
Browse all Crypto & Web3 →

Add the badge to your site

Show visitors that Recta Preflight is listed here — it’s also the link we check for a free listing.

Recta Preflight — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-rectabuild-preflight?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Recta Preflight — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Recta Preflight — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-rectabuild-preflight?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-rectabuild-preflight) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-rectabuild-preflight) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-rectabuild-preflight)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-rectabuild-preflight"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-rectabuild-preflight"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-rectabuild-preflight"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).