Skip to content

Recta MCP server

io.github.RectaBuild/rectaRectaBuildstreamable-httpv1.3.5Scanned

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

10 tools: 1 do something that can't be undone and 9 change things.

Tools: 0 delete, 1 irreversible, 9 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 1
  • 6 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Recta MCP server can do

The Recta MCP server is published by the GitHub account RectaBuild. It has 10 tools. It can do things that cannot be undone, such as sending, paying or publishing (recta_send_signed_request) and create or change data (9 tools: recta_about, recta_status, recta_service_descriptor, recta_fit_check and 5 more), but cannot delete data. None of its tools only reads.

3 tools bring in text other people can write (recta_trial_evaluation, recta_preflight and recta_send_signed_request); 1 tool can send data out of your system (recta_send_signed_request).

The fixed checks matched 6 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 1.3.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Can't be undone 1Claude Code: ask
  • recta_send_signed_requestStep 2: sends the request signed by the agent's own wallet to a Recta route and returns its HTTP status and JSON body.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "recta_send_signed_request" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "recta_send_signed_request" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Changes things 9Claude Code: ask
  • recta_aboutStart here.1 finding

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "recta_about" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • recta_fit_checkCall 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 w…1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "recta_fit_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • recta_preflightFree check to make before any cross-chain USDC/USDT transfer.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Free check to make before any cross-chain USDC/USDT transfer. Send the evaluation request body (from recta_request_template; no wallet and no address needed: only the corridor, amount and baseline_provider are required; sender, recipient, constraints and gas ceilings are filled when absent and listed in `assumed`; your own sender gives the most exact figure) and get, for the route you would use, 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 body to get the route. Stores nothing, charges nothing; shares the trial's 3 a day per IP address.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • recta_prepare_signed_requestStep 1 of a free quote for a cross-chain transfer.1 finding

    Why it is in this group

    • The name "recta_prepare_signed_request" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "recta_prepare_signed_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "recta_prepare_signed_request" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • recta_request_templateReturns 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 ceili…1 finding

    Why it is in this group

    • The name "recta_request_template" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "recta_request_template" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "recta_request_template" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • recta_saving_oddsHow many recorded decisions on this corridor found a saving, by amount range (counts and dates only, never per route).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • recta_service_descriptorCall 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,…1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "recta_service_descriptor" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • recta_statusCall before relying on Recta in a run: whether it is ready to evaluate now, and its contract version.1 finding

    Why it is in this group

    • The name "recta_status" says "status": a word for reading.
    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "recta_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "recta_status" says "status": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Call before relying on Recta in a run: whether it is ready to evaluate now, and its contract version.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • recta_trial_evaluationUnsigned 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 …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:23 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
10
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 10 tools that change things (1 irreversible, 9 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.recta.build/mcp: tools/list returned 10 tools to an anonymous client, including recta_send_signed_request (irreversible), recta_about (write), recta_status (write), recta_service_descriptor (write), recta_fit_check (write) and 5 more

    What this check looks for

Posture changes

  1. Nov 19, 2026
    • Tools that change things, listed without credentials: 9 to 10
  2. Nov 12, 2026
    • Tools that change things, listed without credentials: 4 to 9

Findings

Matches of fixed checks, with the text they matched.

6 warn
  • The server marks "recta_about" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.

    What this check looks for
  • The server marks "recta_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "recta_status" says "status": a word for reading.

    What this check looks for
  • The server marks "recta_service_descriptor" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The server marks "recta_fit_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The server marks "recta_request_template" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "recta_request_template" says "request": a word for a change.

    What this check looks for
  • The server marks "recta_prepare_signed_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "recta_prepare_signed_request" says "request": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 10.View diff
    • Tools that change things, listed without credentials: 9 to 10
  2. Tools1 added, 1 changed.+1 added~1 changedView diff
  3. Tools1 changed.~1 changedView diff
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 9.View diff
    • Tools that change things, listed without credentials: 4 to 9
  5. Tools5 changed.~5 changedView diff
  6. Tools4 added, 1 changed.+4 added~1 changedView diff
  7. Tools5 changed.~5 changedView diff

Install

Pinned to version 1.3.5. Values in angle brackets are yours to fill in.

claude mcp add --transport http recta https://api.recta.build/mcp
claude mcp add --transport http recta https://api.recta.build/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__recta__recta_about",
      "mcp__recta__recta_status",
      "mcp__recta__recta_service_descriptor",
      "mcp__recta__recta_fit_check",
      "mcp__recta__recta_saving_odds",
      "mcp__recta__recta_request_template",
      "mcp__recta__recta_trial_evaluation",
      "mcp__recta__recta_preflight",
      "mcp__recta__recta_prepare_signed_request",
      "mcp__recta__recta_send_signed_request"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as recta. Review it before you use it.

Capability tags behind 3 rules
  • mcp__recta__recta_trial_evaluation untrusted-input
  • mcp__recta__recta_preflight untrusted-input
  • mcp__recta__recta_send_signed_request untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.RectaBuild/recta/verify?hash=55697f58e66ac327ce8427e613ed87e58445ff75fa7be9c06fdbe1fb89b977fe" | jq -e '.changed == false'

Pinned hash 55697f58e66a, from Nov 19, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.RectaBuild/recta/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.RectaBuild/recta
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.RectaBuild/recta.svg)](https://radar.anlyon.com/servers/io.github.RectaBuild/recta)

Source: MCP Registry · repository. Synced Nov 19, 2026, 16:17 UTC.

Recta MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Recta MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 10 of which can change, send or delete something, and 6 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Recta MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Recta MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: recta_send_signed_request.

What tools does the Recta MCP server have?

10 tools: 1 irreversible, 9 write. recta_send_signed_request, recta_about, recta_status, recta_service_descriptor, recta_fit_check, recta_saving_odds, recta_request_template, recta_trial_evaluation and 2 more.

Does the Recta MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Recta MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): recta_send_signed_request.

Has the Recta MCP server changed its tools?

Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.