About Recta
Recta helps AI agents moving stablecoins or BTC between chains check for a cheaper route before bridging. It charges 5% of on-chain verified savings, nothing when there are none, and leaves signing and sending transactions to the agent.
Key features
- 01Evaluate cross-chain routes before transfers
- 02Verify savings on-chain
- 03Charge 5% of verified savings
- 04Let agents sign and send transactions
- 05Keep keys and funds with the agent
Use cases
- 01Compare bridge routes before moving stablecoins
- 02Check alternatives for cross-chain BTC transfers
- 03Execute an authorized route from an agent wallet
MCP support
The hosted service provides a Streamable HTTP MCP endpoint with no API key. The repository also contains a local MCP server based on the client; execution is off by default and keys stay on the machine.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.recta.build/mcpclaude mcp add --transport http rectabuild-recta https://api.recta.build/mcp{"mcpServers":{"rectabuild-recta":{"type":"http","url":"https://api.recta.build/mcp"}}}Open in Cursor{"servers":{"rectabuild-recta":{"type":"http","url":"https://api.recta.build/mcp"}}}Open in VS Code{"mcpServers":{"rectabuild-recta":{"type":"http","url":"https://api.recta.build/mcp"}}}{"mcpServers":{"rectabuild-recta":{"serverUrl":"https://api.recta.build/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMERecta
Preflight for AI agents that move stablecoins or BTC between blockchains: before a bridge transfer, ask Recta whether a cheaper route exists at the same chain state. Free when there is none; otherwise exactly 5 % of the saving verified on chain. The agent keeps at least 95 % of every verified saving.
- Docs for agents: https://api.recta.build/llms.txt
- MCP server (Streamable HTTP, no API key): https://api.recta.build/mcp
- OpenAPI: https://api.recta.build/openapi.json
- Wallet allowlist for agent wallets: https://api.recta.build/v1/golden-corridor/wallet-policy
- Coverage check (unsigned, free): https://api.recta.build/v1/golden-corridor/fit?source_network=ethereum&source_asset=USDC&destination_network=arbitrum&destination_asset=USDC
Recta never holds keys or funds: your agent signs and sends every transaction itself.
Client package
packages/client is @recta/client: evaluate, authorize the fee, execute and report from your
agent's own wallet, with local checks before every signature. Published to npm from this repository with provenance.
Local MCP server
packages/mcp is @recta/mcp: a local MCP server over the client, so Claude, Cursor or any MCP agent
runs the same flow with its own key, which stays on the machine. Execution is off until the operator turns it on.
What is in this repository
The tools an agent uses to call Recta: the Agent Skill, the AGENTS.md snippet and, as they are published, the client
and local MCP packages. The server behind api.recta.build is not published here; its MCP endpoint above is the one
listed in the official MCP Registry as io.github.RectaBuild/recta.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.