# Recta (remote · api.recta.build)

Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `api.recta.build`: 61/100 (this document), [markdown](https://verifymcp.io/servers/rectabuild-recta/api.md), [page](https://verifymcp.io/servers/rectabuild-recta/api)

## Channel facts

- Endpoint: `https://api.recta.build/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 27% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

## Install

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

### Claude

```bash
claude mcp add --transport http rectabuild-recta 'https://api.recta.build/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "rectabuild-recta": {
      "url": "https://api.recta.build/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "rectabuild-recta": {
      "type": "http",
      "url": "https://api.recta.build/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.rectabuild-recta]
url = "https://api.recta.build/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rectabuild-recta": {
      "type": "remote",
      "url": "https://api.recta.build/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rectabuild-recta --url 'https://api.recta.build/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  rectabuild-recta:
    url: "https://api.recta.build/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "rectabuild-recta": {
      "Transport": "http",
      "Url": "https://api.recta.build/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add rectabuild-recta -t streamable-http -u 'https://api.recta.build/mcp'
```

### Other

```json
{
  "mcpServers": {
    "rectabuild-recta": {
      "type": "http",
      "url": "https://api.recta.build/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 61)

First indexed and scored.

## MCP tools (5)

### `recta_about` (~196 tokens)

What Recta is and how it charges

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

### `recta_status` (~22 tokens)

Service readiness

Whether Recta is ready to evaluate, and its contract version.

### `recta_service_descriptor` (~34 tokens)

Commercial contract

Supported corridors (networks and assets), providers, amount ranges, limits and the JSON Schema of every request and response.

### `recta_prepare_signed_request` (~242 tokens)

Text to sign for a Recta request

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

Input parameters:

- `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` (required)
- `path` (string, required): 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…

### `recta_send_signed_request` (~116 tokens)

Send a signed request to Recta

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.

Input parameters:

- `body` (string)
- `idempotency_key` (string)
- `issued_at` (integer, required)
- `method` (required)
- `path` (string, required)
- `signature` (string, required)
- `signer` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/rectabuild-recta/api#diagnostics

## Score history

- 2026-11-04: 61

## Common questions

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

## Links

- Remote endpoint: https://api.recta.build/mcp
- Repository: https://github.com/RectaBuild/route-hint
- Website: https://api.recta.build/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/rectabuild-recta/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/rectabuild-recta/api.json
- HTML version of this page: https://verifymcp.io/servers/rectabuild-recta/api