Recta
REMOTE · API.RECTA.BUILD
Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.
Available components
Last scanned (12 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 4 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 Security63
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 822 tokens (~164/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 not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 27% 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 61
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 4 Nov 2026 · Probed https://api.recta.build/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 insecure
Validation of api.recta.build. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| build. | present | 30770, 38839 | 8, 8 | Verified |
| recta.build. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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/mcp | Verified | 200 | |
| http (plaintext) | http://api.recta.build/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_about What Recta is and how it charges ~196
Recta is a preflight for AI agents that move stablecoins (and BTC) between blockchains. Before a transfer, the agent asks Recta; Recta reads every route it knows at the same chain state (Across, CCTP, Stargate, USDT0 and others) and returns the cheapest one it can prove, against the route the agent would have used anyway. Recta charges exactly 5 % of the saving it verifies on chain after the agent executes its route. No saving, no charge. No prepayment and no credit: the agent signs, with each decision, a Permit2 authorization capped at `max_fee_authorization`, and Recta's collection pulls only the verified 5 % (never more than the cap) in USDC on Base; the payer's ledger shows whether each fee has been collected yet (`charged`). The evaluation itself is free. Returns the full guide (llms.txt).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recta_prepare_signed_request Text to sign for a Recta request ~242
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: see recta_service_descriptor; its "sender" must be the signing address).
| 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_send_signed_request Send a signed request to Recta ~116
Sends a request signed by the agent's own wallet to a Recta route and returns its HTTP status and JSON body. An evaluation is free; executing a decision's route creates a fee of 5 % of the verified saving, capped by the permit the agent signs.
| 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.
recta_service_descriptor Commercial contract ~34
Supported corridors (networks and assets), providers, amount ranges, limits and the JSON Schema of every request and response.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recta_status Service readiness ~22
Whether Recta is ready to evaluate, and its contract version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Recta MCP server?
Recta is a hosted endpoint at https://api.recta.build/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-recta 'https://api.recta.build/mcp'
What is the Recta MCP server?
Recta is an MCP server listed in the public MCP registry as io.github.RectaBuild/recta. Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none. This page covers its hosted endpoint (https://api.recta.build/mcp).
Is the Recta MCP server safe to use?
Recta scores 61 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 MCP server expose?
Recta exposes 5 tools: recta_about, recta_status, recta_service_descriptor, recta_prepare_signed_request, recta_send_signed_request. Their descriptions and schemas cost roughly 610 tokens of context every time the server is loaded.
Does the Recta MCP server require authentication?
No. We connected to Recta without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Recta MCP server still maintained?
Recta is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.