Recta Preflight
Free check before a cross-chain USDC/USDT transfer: total cost, arrival time, proven cheaper route
¿Debería usar esto?
Calidad y seguridad
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"preflight": {
"url": "https://api.recta.build/preflight/mcp"
}
}
}Puntos de conexión remotos
https://api.recta.build/preflight/mcpstreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (5)
🟢recta_preflight(source_network, source_asset, destination_network, destination_asset, amount, ...)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"source_network": {
"type": "string",
"description": "Lowercase network as in the service descriptor, e.g. base, ethereum, arbitrum."
},
"source_asset": {
"type": "string",
"description": "Uppercase asset, e.g. USDC."
},
"destination_network": {
"type": "string"
},
"destination_asset": {
"type": "string"
},
"amount": {
"type": "string",
"description": "How 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_provider": {
"type": "string",
"description": "Optional: 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: lifi, or across where LI.FI does not apply."
},
"sender": {
"type": "string",
"description": "Optional: your own sending address, for the most exact figure."
},
"recipient": {
"type": "string",
"description": "Optional: the receiving address."
},
"body": {
"type": "object",
"description": "Alternative to the fields above: the whole evaluation request body (from recta_request_template), as a JSON object."
}
},
"required": [
"source_network",
"source_asset",
"destination_network",
"destination_asset",
"amount"
]
}🟢recta_fit_check(source_network, source_asset, destination_network, destination_asset)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"source_network": {
"type": "string",
"description": "Lowercase network as in the service descriptor, e.g. base, ethereum, arbitrum."
},
"source_asset": {
"type": "string",
"description": "Uppercase asset, e.g. USDC."
},
"destination_network": {
"type": "string"
},
"destination_asset": {
"type": "string"
}
},
"required": [
"source_network",
"source_asset",
"destination_network",
"destination_asset"
],
"additionalProperties": false
}🟢recta_request_template(source_network, source_asset, destination_network, destination_asset, amount, ...)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"source_network": {
"type": "string",
"description": "Lowercase network as in the service descriptor, e.g. base, ethereum, arbitrum."
},
"source_asset": {
"type": "string",
"description": "Uppercase asset, e.g. USDC."
},
"destination_network": {
"type": "string"
},
"destination_asset": {
"type": "string"
},
"amount": {
"type": "string",
"description": "How 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_provider": {
"type": "string",
"description": "The route you would use without Recta (see recta_fit_check's declarable_baselines)."
},
"guarantee_class": {
"type": "string"
},
"latency_class": {
"type": "string"
}
},
"required": [
"source_network",
"source_asset",
"destination_network",
"destination_asset",
"amount",
"baseline_provider"
],
"additionalProperties": false
}🟢recta_prepare_signed_request(method, path, idempotency_key, body)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"method": {
"enum": [
"GET",
"POST"
]
},
"path": {
"type": "string",
"description": "A signed route: /v1/golden-corridor/commercial-evaluations[/{result_id}[/execution-artifact|/fee-authorization|/execution]], /v1/golden-corridor/commercial-accruals/{payer} or /v1/golden-corridor/fee-debts."
},
"idempotency_key": {
"type": "string",
"description": "Required by POST /v1/golden-corridor/commercial-evaluations."
},
"body": {
"type": "string",
"description": "The exact JSON body text, byte for byte as it will be sent. Empty for GET."
}
},
"required": [
"method",
"path"
],
"additionalProperties": false
}🟡recta_send_signed_request(method, path, idempotency_key, body, signer, ...)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"method": {
"enum": [
"GET",
"POST"
]
},
"path": {
"type": "string"
},
"idempotency_key": {
"type": "string"
},
"body": {
"type": "string"
},
"signer": {
"type": "string",
"pattern": "^0x[0-9a-fA-F]{40}$"
},
"issued_at": {
"type": "integer"
},
"signature": {
"type": "string",
"pattern": "^0x[0-9a-fA-F]+$"
}
},
"required": [
"method",
"path",
"signer",
"issued_at",
"signature"
],
"additionalProperties": false
}Comunidad
Evidencia