Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Recta

NPM · @RECTA/MCP · 2 COMPONENTS

Proven cheaper USDC bridge route for AI agents (Across, CCTP, Stargate); fee 5% of verified saving

+3 this week 82 Trust /100

Last scanned (12 hours ago)

Scores higher than 71% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 19 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to RectaBuild/recta). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 663 tokens (~331/item across 2 items; 2 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 86% 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
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 0
    • Stability: 0.30 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.1.14 → 0.1.16 functional
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +27
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 1.00 ▲ functional
  • 13 Nov 26 −26
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: 1.00 → unverified ▼ functional
    • Package version: 0.1.11 → 0.1.14 functional
    • Package version: 0.1.11 → 0.1.13 functional
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.07 ▲ functional
    • Package version: 0.1.7 → 0.1.11 functional
    • Package version: 0.1.1 → 0.1.7 functional
Diagnostics

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 · Analysed npm/@recta/mcp@0.1.16

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo RectaBuild/recta
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/RectaBuild/recta/.github/workflows/mcp-publish.yml@refs/tags/mcp-v0.1.16
Rekor log index 4000003091
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:877ed5f89ad60f6e08029293eca7c0222d0fdd8471c9a93fa49418c29534fdf0f5358c6aa7ccc458b57db8e319ef5e0d7e1303d044010b8b97e40cd21

Background: How many MCP packages publish verified provenance →

Dependencies 19 packages
Packages resolved 19
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~600 tokens

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 →

Tool Tokens
recta_fit ~100

Free and unsigned: does Recta cover this corridor, and which contracts would a route call? Call it before recta_evaluate.

NameTypeReqDescription
destination_assetstring–Defaults to source_asset.
destination_networkstringyes–
source_assetstringyesAsset moved, e.g. USDC or USDT.
source_networkstringyesSource network key, e.g. base, arbitrum, ethereum, optimism, polygon.

No output schema declared.

No examples provided.

recta_trial_evaluation ~500

Free, unsigned and stored nowhere: the same question as recta_evaluate with the same arguments, answered only with whether a cheaper provable route exists, the saving (lower bound, USDC) and Recta's 5 % of it. Names no route and returns no result_id; 3 a day per IP address. Use it to see whether Recta is worth a signature. Works without a key (give sender, or set RECTA_ADDRESS).

NameTypeReqDescription
amountstringyesHow 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). Recta sets no maximum; this server refuses more th…
baseline_providerstringyesThe route you would use without Recta, one of the corridor's declarable_baselines in recta_fit (GET /v1/golden-corridor/fit): across, stargate_v2, usdt0, usdg_oft, debridge_dln or lifi (LI.FI: declar…
destination_assetstring–Defaults to source_asset.
destination_networkstringyes–
guarantee_classstring–Default ANY.
latency_classstring–Default ANY.
recipientstring–Destination address; defaults to the local wallet. Any other address must be on the operator's list (RECTA_ALLOWED_RECIPIENTS), or the evaluation is refused before anything is signed.
senderstring–Only when the server runs without a key: the EVM address the transfer would leave from (0x + 40 hex), else RECTA_ADDRESS. With a key it is ignored: the sender is the local wallet.
source_assetstringyesAsset moved, e.g. USDC or USDT.
source_networkstringyesSource network key, e.g. base, arbitrum, ethereum, optimism, polygon.

No output schema declared.

No examples provided.

Install

How do I install the Recta MCP server?

Recta runs locally as an npm package, launched with npx -y @recta/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @recta/mcp

# add to Claude Code
claude mcp add rectabuild-recta -- npx -y @recta/mcp
Common questions

What is the Recta MCP server?

Recta is an MCP server listed in the public MCP registry as io.github.RectaBuild/recta. Proven cheaper USDC bridge route for AI agents (Across, CCTP, Stargate); fee 5% of verified saving. This page covers its npm package (@recta/mcp).

Is the Recta MCP server safe to use?

Recta scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 2 tools: recta_fit, recta_trial_evaluation. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.

Is the Recta MCP server still maintained?

Recta 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 licence is the Recta MCP server under?

Recta declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Recta MCP server?

VerifyMCP ran 16 checks on Recta, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.