Recta Preflight
REMOTE · API.RECTA.BUILD
Free check before a cross-chain USDC/USDT transfer: total cost, arrival time, proven cheaper route
Available components
Last scanned (15 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability50
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1580 tokens (~316/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 4 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 2 additions. See how to fix → Fail
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 −3
- Stability: 0.07 → fail ▼ security
- A breaking change shipped without a version bump: still RECTA_COMMERCIAL_EVALUATION_CONTRACT_V23 ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “recta_preflight” rewrote its description, which is the text the model reads security
- Schema quality: 222 → 316 ▼ functional
- “recta_preflight” added a required parameter “amount”, so existing callers break ▼ functional
- “recta_preflight” added a required parameter “destination_asset”, so existing callers break ▼ functional
- “recta_preflight” added a required parameter “destination_network”, so existing callers break ▼ functional
- “recta_preflight” added a required parameter “source_asset”, so existing callers break ▼ functional
- “recta_preflight” added a required parameter “source_network”, so existing callers break ▼ functional
- “recta_preflight” changed the type of “body”: object|string → object ▼ functional
- Destructive annotations: pass → 100 functional
- New tool “recta_prepare_signed_request” functional
- New tool “recta_send_signed_request” functional
- “recta_preflight” added an optional parameter “baseline_provider” cosmetic
- “recta_preflight” added an optional parameter “recipient” cosmetic
- “recta_preflight” added an optional parameter “sender” cosmetic
- “recta_preflight” reworded the description of “body” cosmetic
- “recta_preflight” made “body” optional cosmetic
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “recta_preflight” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.recta.build/preflight/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=recta.build | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 3cf66954c1320e1b1358efc7c0fa2558 |
| SANs: recta.build, api.recta.build, *.api.recta.build | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.recta.build. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| build. | DS published | 30770, 38839 | 8, 8 | Verified |
| recta.build. | DS published | 2371 | 13 | Verified |
| api.recta.build. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.recta.build/preflight/mcp | Verified | 200 | |
| http (plaintext) | http://api.recta.build/preflight/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
recta_fit_check Is my transfer covered? (free, no signature) ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination_asset | string | yes | – |
| destination_network | string | yes | – |
| source_asset | string | yes | Uppercase asset, e.g. USDC. |
| source_network | string | yes | Lowercase network as in the service descriptor, e.g. base, ethereum, arbitrum. |
No output schema declared.
No examples provided.
recta_preflight Preflight before a cross-chain transfer: cost, arrival and saving (free, no signature) ~431
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | 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 | string | – | 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 appl… |
| body | object | – | Alternative to the fields above: the whole evaluation request body (from recta_request_template), as a JSON object. |
| destination_asset | string | yes | – |
| destination_network | string | yes | – |
| recipient | string | – | Optional: the receiving address. |
| sender | string | – | Optional: your own sending address, for the most exact figure. |
| source_asset | string | yes | Uppercase asset, e.g. USDC. |
| source_network | string | yes | Lowercase network as in the service descriptor, e.g. base, ethereum, arbitrum. |
No output schema declared.
No examples provided.
recta_prepare_signed_request Text to sign for a Recta request ~417
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | The exact JSON body text, byte for byte as it will be sent. Empty for GET. |
| idempotency_key | string | – | Required by POST /v1/golden-corridor/commercial-evaluations. |
| method | – | yes | – |
| path | string | yes | 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… |
No output schema declared.
No examples provided.
recta_request_template The whole evaluation request for my transfer (free, no signature) ~219
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | 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 | string | yes | The route you would use without Recta (see recta_fit_check's declarable_baselines). |
| destination_asset | string | yes | – |
| destination_network | string | yes | – |
| guarantee_class | string | – | – |
| latency_class | string | – | – |
| source_asset | string | yes | Uppercase asset, e.g. USDC. |
| source_network | string | yes | Lowercase network as in the service descriptor, e.g. base, ethereum, arbitrum. |
No output schema declared.
No examples provided.
recta_send_signed_request Send a signed request to Recta ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| idempotency_key | string | – | – |
| issued_at | integer | yes | – |
| method | – | yes | – |
| path | string | yes | – |
| signature | string | yes | – |
| signer | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Recta Preflight MCP server?
Recta Preflight is a hosted endpoint at https://api.recta.build/preflight/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.recta.build
claude mcp add --transport http rectabuild-preflight 'https://api.recta.build/preflight/mcp'
What is the Recta Preflight MCP server?
Recta Preflight is an MCP server listed in the public MCP registry as io.github.RectaBuild/preflight. Free check before a cross-chain USDC/USDT transfer: total cost, arrival time, proven cheaper route. This page covers its hosted endpoint (https://api.recta.build/preflight/mcp).
Is the Recta Preflight MCP server safe to use?
Recta Preflight scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Recta Preflight MCP server expose?
Recta Preflight exposes 5 tools: recta_preflight, recta_fit_check, recta_request_template, recta_prepare_signed_request, recta_send_signed_request. Their descriptions and schemas cost roughly 1,347 tokens of context every time the server is loaded.
Does the Recta Preflight MCP server require authentication?
No. We connected to Recta Preflight without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Recta Preflight MCP server still maintained?
Recta Preflight is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Recta Preflight MCP server?
VerifyMCP ran 12 checks on Recta Preflight, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Recta Preflight: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.