NestDaddy

Recta

io.github.RectaBuild/recta · v1.3.2

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

Connect Remote server

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

Tools 9 found in our last check

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

  • recta_status

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

  • 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.

  • 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_saving_odds

    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.

  • 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_trial_evaluation

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

  • 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, the cheapest provable route against the route the agent would use anyway, or an abstention. Execu…

Details

Endpointhttps://api.recta.build/mcp (Streamable HTTP)
Package@recta/[email protected] (NPM, stdio)
First published11 Nov 2026
Last updated11 Nov 2026
Registry nameio.github.RectaBuild/recta

More ai and media servers See all

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