Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
Recta is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
97/100
trust score
12
tools declared
local
or remote
—
downloads a day
What it does
Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user recta-mcp '--' npx -y @recta/mcp
# 2 — ask your agent for something these tools do
# recta_fit, recta_evaluate, recta_preview and 9 more
Recta costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
REAll 1 server
rectabuild1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user recta-mcp '--' npx -y @recta/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://api.recta.build/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http recta-mcp https://api.recta.build/mcpFree on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Free and unsigned: does Recta cover this corridor, and which contracts would a route call? Call it before recta_evaluate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source_network | string | yes | Source network key, e.g. base, arbitrum, ethereum, optimism, polygon. |
| source_asset | string | yes | Asset moved, e.g. USDC or USDT. |
| destination_network | string | yes | — |
| destination_asset | string | no | Defaults to source_asset. |
Before a cross-chain stablecoin transfer: ask Recta, signed with the local key, whether a cheaper route than the one you would use (baseline_provider) can be proven at the same chain state. Free; returns a result_id. If there is no saving, keep your own route: nothing is owed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount | string | yes | Whole units, e.g. "100". Recta accepts 10 to 100000. |
| baseline_provider | string | yes | The route you would use without Recta: across, stargate_v2, cctp_v2_standard, cctp_v2_fast, relay, usdt0, usdg_oft or debridge_dln. The saving is measured against it. |
| recipient | string | no | Destination address; defaults to the local wallet. |
| guarantee_class | string | no | Default ANY. |
| latency_class | string | no | Default ANY. |
For a result_id with a saving: shows the fee ceiling Recta asks you to authorize and, when no permit is needed, the transactions after this server's local checks. Signs nothing, sends nothing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| result_id | string | yes | — |
For a result_id with a saving: signs the fee permit (never above the operator's cap), sends the committed transactions from the local wallet after the local checks, and reports them to Recta. Recta charges exactly 5 % of the saving it verifies on chain. Only available when the operator enabled…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| result_id | string | yes | — |
Reports an executed route again (for example after a PENDING answer). Returns ACCRUED, PENDING or REFUSED.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| result_id | string | yes | — |
| origin_tx_hash | string | yes | — |
| approval_tx_hash | string | no | — |
When recta_evaluate answered DEBT: signs the debt permit Recta offered (after the same checks as a fee permit, never above the operator's cap) so evaluations can continue. Only available when the operator enabled execution.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| debt_offer | object | yes | The debt_offer object exactly as recta_evaluate returned it. |
The local wallet's Recta fees and whether each was collected.
No parameter schema on file.
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
No parameter schema on file.
Whether Recta is ready to evaluate, and its contract version.
No parameter schema on file.
Supported corridors (networks and assets), providers, amount ranges, limits and the JSON Schema of every request and response.
No parameter schema on file.
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 b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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- |
| idempotency_key | string | no | Required by POST /v1/golden-corridor/commercial-evaluations. |
| body | string | no | The exact JSON body text, byte for byte as it will be sent. Empty for GET. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| method | yes | — | |
| path | string | yes | — |
| idempotency_key | string | no | — |
| body | string | no | — |
| signer | string | yes | — |
| issued_at | integer | yes | — |
| signature | string | yes | — |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Recta or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 97 / 100
Scanned: 0.1.1 · 6 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digestfd675b6abc5851db4e1f681b5bc1c6f4248fe10eb934c7566f15ca73f5030f1a
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| recta_fit | no tags | |
| recta_evaluate | external-sink | external-sink: parameter "recipient" |
| recta_preview | no tags | |
| recta_execute | no tags | |
| recta_report | no tags | |
| recta_pay_debt | no tags | |
| recta_ledger | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestfd675b6abc5851db
Scanned2026-11-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.0. Pin a release below and the command asks for exactly that one.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Recta can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.