Recta

Proven cheaper USDC bridge route for AI agents (Across, CCTP, Stargate); fee 5% of verified saving

¿Debería usar esto?

Calidad y seguridad

B
Calidad de la descripción
96%
Integridad del esquema
70%
Calidad de los nombres
80%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~2,027Tokens (definiciones de herramientas)
~1.1 KBTamaño de respuesta típico
Impacto moderado en la atención (1.58% del contexto de 128k)

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": {
    "recta": {
      "command": "npx",
      "args": [
        "@recta/mcp"
      ]
    }
  }
}

Paquetes ejecutables

npm@recta/mcp0.1.14stdio

Puntos de conexión remotos

https://api.recta.build/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (9)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢recta_about

Start here. Call Recta before your agent moves stablecoins 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. Transfers start on: arbitrum, arc, avalanche, base, bnb_chain, ethereum, hyperevm, ink, linea, monad, optimism, polygon, unichain. They can arrive on: arbitrum, arc, avalanche, base, bnb_chain, ethereum, hyperevm, ink, linea, monad, optimism, polygon, robinhood_chain, solana_mainnet, tron_mainnet, unichain. Assets: USDC, USDC_BINANCE_PEG, USDG, USDT, USDT_BINANCE_PEG, USDT_OP_BRIDGED. Amounts: at least 3.5 tokens of a stablecoin (about 3.5 USD), no maximum. 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.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢recta_status

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

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢recta_service_descriptor

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.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢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_saving_odds(source_network, source_asset, destination_network, destination_asset, baseline_provider)

How many recorded decisions on this corridor found a saving, by amount range (counts and dates only, never per route). Unsigned and free; use it to decide whether a signed evaluation is worth it.

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"
    },
    "baseline_provider": {
      "type": "string",
      "description": "Accepted and ignored: the odds are for the whole corridor."
    }
  },
  "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_trial_evaluation(body)

Unsigned trial of an evaluation: send the evaluation request body (from recta_request_template, with a sender and recipient filled: no wallet needed: any sender address other than the zero address, and any recipient of the destination network's kind) 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 IP address. To get the route, sign the same body with recta_prepare_signed_request and recta_send_signed_request.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "body": {
      "description": "The evaluation request body, as a JSON object or its JSON text.",
      "type": [
        "object",
        "string"
      ]
    }
  },
  "required": [
    "body"
  ],
  "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

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada9 herramientas