MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

Recta

Claim this listing

io.github.RectaBuild/recta

RectaBuildVerified

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

AI models & agents

Developer ToolsIs Recta down?Alternatives

14 of 22 checks passed

  • Handshake
  • Tools listed
  • Updated recently

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Connect to server
Median latency
75 ms
Uptime, 30 days
Not measured
Last checked

Measurement details

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 78 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name recta.

  • Pass
    Lists tools

    tools/list returned 9 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 75 ms over 2 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 78 ms over 2 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    2 of 2 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Pass
    Stable tool list

    No tool was removed and no required parameter was added in the last 30 days.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Fail
    Parameters documented

    13 of 29 parameters have a description (45%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Not measured
    Website matches publisher

    This namespace is not a reverse domain, so the website comparison does not apply.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Pass
    Repo owner matches

    The GitHub repository owner matches the namespace login.

  • Pass
    Recently updated

    Updated 2026-11-09T20:53:18.489463Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Tools

  • recta_about

    Start here. Call Recta before your agent moves stablecoins or BTC from one blockchain to another (a bridge or cross-chain transfer): give it the route you would use anyway, and it answers, for free, whether a cheaper route exists at the same chain state and proves the saving. If there is none, nothing is charged. Networks: arbitrum, arc, avalanche, base, bitcoin_l1, bnb_chain, ethereum, hyperevm, ink, linea, monad, optimism, polygon, robinhood_chain, solana_mainnet, tron_mainnet, unichain. Assets: BTC, USDC, USDC_BINANCE_PEG, USDG, USDT, USDT_BINANCE_PEG, USDT_OP_BRIDGED. The exact corridors are in the service descriptor. Returns the full guide (llms.txt): what Recta is, the fee (5 % of the verified saving, nothing if none) and the call flow.

    Measured

  • recta_fit_check

    Call first, before a cross-chain stablecoin or BTC transfer: whether Recta covers the corridor, which routes it compares, which route you can declare as yours, and the contracts a route would touch. Unsigned, free, never reveals a route or a saving.

    Measured

  • recta_prepare_signed_request

    Step 1 of a free quote for a cross-chain transfer. 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: recta_request_template; its "sender" must be the signing address). If you have no wallet tool that can personal_sign, this server cannot sign for you: No signing code needed: the npm package @recta/client builds, checks and signs the request for you, and @recta/mcp (`npx -y @recta/mcp`) is a local MCP server that does it as tools: without a key it offers only the free fit check and trial; with RECTA_PRIVATE_KEY of a dedicated wallet (kept on your machine) it signs too. Evaluations are free and need no funds. Paying a fee needs the fee in USDC on Base and a USDC allowance to Permit2 (an ERC-20 approve of USDC to Permit2), besides the transfer itself when it starts from Base USDC.

    Measured

  • recta_request_template

    Returns the full body of the evaluation request for a corridor, an amount and the route you would use anyway (baseline_provider): you fill only your sender, recipient and gas ceilings, then sign it with recta_prepare_signed_request and recta_send_signed_request.

    Measured

  • recta_saving_odds

    How many recorded decisions on this corridor found a saving against each route you could declare (counts and dates only). Unsigned and free; use it to decide whether a signed evaluation is worth it.

    Measured

  • recta_send_signed_request

    Step 2: sends the request signed by the agent's own wallet to a Recta route and returns its HTTP status and JSON body. POST /v1/golden-corridor/commercial-evaluations returns, free, the cheapest provable route against the route the agent would use anyway, or an abstention. Executing a decision's route creates a fee of 5 % of the verified saving, capped by the permit the agent signs; no saving, no fee.

    Measured

  • recta_service_descriptor

    Call to check whether a planned cross-chain transfer is covered: the supported corridors (source and destination networks and assets), the bridges compared (Across, CCTP, Stargate, USDT0 and others), amount ranges, limits and the JSON Schema of every request and response.

    Measured

  • recta_status

    Call before relying on Recta in a run: whether it is ready to evaluate now, and its contract version.

    Measured

  • recta_trial_evaluation

    Unsigned trial of an evaluation: send the evaluation request body (from recta_request_template, with your sender and recipient filled) and get whether a cheaper provable route exists for this exact transfer, the saving (lower bound, USDC) and Recta's 5 % of it. Names no route, stores nothing, charges nothing; 3 a day per address. To get the route, sign the same body with recta_prepare_signed_request and recta_send_signed_request.

    Measured

Probe history

  • ok78 ms9 tools
  • ok72 ms9 tools

Status and uptime

Add badge to your README

The image links back to this page. It shows checks passed, or uptime, and the colour follows the latest status. Responses are cached for 5 to 15 minutes.

MCP Heartbeat badge

Markdown

[![MCP Heartbeat](https://mcpheartbeat.com/badge/io.github.RectaBuild/recta.svg)](https://mcpheartbeat.com/s/io.github.RectaBuild/recta)

HTML

<a href="https://mcpheartbeat.com/s/io.github.RectaBuild/recta"><img alt="MCP Heartbeat" src="https://mcpheartbeat.com/badge/io.github.RectaBuild/recta.svg"></a>

Uptime markdown

[![MCP Heartbeat uptime](https://mcpheartbeat.com/badge/io.github.RectaBuild/recta.svg?kind=uptime)](https://mcpheartbeat.com/s/io.github.RectaBuild/recta)

Served from https://mcpheartbeat.com.

Related servers

All alternatives

Same function and industry, ranked by checks passed then median latency.

Connect to this server

Claude Code

claude mcp add --transport http recta https://api.recta.build/mcp

Cursor .cursor/mcp.json

{
  "mcpServers": {
    "recta": {
      "url": "https://api.recta.build/mcp"
    }
  }
}

VS Code .vscode/mcp.json

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