NestDaddy

Recta Preflight

io.github.RectaBuild/preflight · v1.0.0

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

MCP Score How we grade

B
78 / 100

From what our daily checks can see without credentials, last checked 22 Nov 2026.

Reliability
Answered 6 of 6 daily checks.
30 / 30
Speed
Typical response 206 ms.
16 / 20
Tool docs
5 of 5 tools have a full description; 16 of 32 inputs have a description.
18 / 25
Stability
3 tool rewrites in 30 days (description or inputs changed, or removed).
5 / 15
Listing
Missing an icon.
9 / 10

How to raise the grade

  • Answer initialize faster: under 150 ms earns full Speed points (yours: 206 ms).
  • Describe every tool input in its inputSchema (16 of 32 have no description).
  • Change tool descriptions and inputs rarely, and with a new version: agents trust stable tools.
  • Add an icon to your server.json in the official MCP registry.
Fixed something? Run the same check now. The grade updates at once.

Connect Remote server

Terminal
claude mcp add --transport http preflight https://api.recta.build/preflight/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "preflight": {
      "url": "https://api.recta.build/preflight/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "preflight": {
      "type": "http",
      "url": "https://api.recta.build/preflight/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://api.recta.build/preflight/mcp

Tools 5 found in our last check

  • recta_preflight

    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…

  • recta_fit_check

    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.

  • recta_request_template

    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.

  • recta_prepare_signed_request

    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,…

  • recta_send_signed_request

    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 sa…

Tool changes seen by our daily check

  • 21 Nov 2026

    Description changed: recta_send_signed_request.

  • 20 Nov 2026

    Added: recta_prepare_signed_request, recta_send_signed_request.

  • 19 Nov 2026

    Inputs changed: recta_preflight. Description changed: recta_preflight.

Renames and new inputs are usually routine. A changed description changes what your agent is told the tool does, and can carry new instructions: review it before you rely on the tool again.

Details

Endpointhttps://api.recta.build/preflight/mcp (Streamable HTTP)
First published17 Nov 2026
Last updated17 Nov 2026
Registry nameio.github.RectaBuild/preflight

More other servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.