Relay

NPM · @RELAYPROTOCOL/RELAY-MCP · SCANNED AUG 3

Cross-chain bridge and swap quotes, fee estimation, and transaction tracking via Relay Protocol.

Available components

+25 this week 63 63 Trust /100

Trust breakdown (6 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 →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency19

Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 145 days ago).Pass
Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified

Schema Quality & AI Usability73

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 1244 tokens (~155/item across 8 items; 8 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 Management23

Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @relayprotocol/relay-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add reservoirprotocol-relay-mcp -- npx -y @relayprotocol/relay-mcp

# add to Codex CLI

codex mcp add reservoirprotocol-relay-mcp -- npx -y @relayprotocol/relay-mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "reservoirprotocol-relay-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@relayprotocol/relay-mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add reservoirprotocol-relay-mcp --command npx --arg -y --arg @relayprotocol/relay-mcp

# ~/.hermes/config.yaml

mcp_servers:
  reservoirprotocol-relay-mcp:
    command: "npx"
    args: ["-y", "@relayprotocol/relay-mcp"]

// mcp.json

{
  "mcpServers": {
    "reservoirprotocol-relay-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@relayprotocol/relay-mcp"
      ]
    }
  }
}

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.

2 Aug 26 +63
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
1 Aug 26 −14
- Tool coverage: 100 → unverified ▼ functional
31 Jul 26 −6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +2
- Malware scan: pass → unverified ▼ security
- Tool coverage: unverified → 100 ▲ functional
28 Jul 26 −20
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
27 Jul 26 38

First indexed and scored.

Show 4 earlier entries Hide earlier entries

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 3 Aug 2026 · Analysed npm/@relayprotocol/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 8 exposed · ~1,244 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.

Tool Tokens

estimate_fees ~161

Estimate the fees for a bridge or swap without committing to execution. Returns a breakdown of gas fees, relayer fees, and total cost impact. Useful for comparing routes or showing users expected costs.

Input Output Examples

Name	Type	Req	Description
amount	string	yes	Amount in the origin token's smallest unit.
destinationChainId	number	yes	Destination chain ID.
destinationCurrency	string	yes	Destination token address. "0x0000000000000000000000000000000000000000" for native.
originChainId	number	yes	Source chain ID.
originCurrency	string	yes	Origin token address. "0x0000000000000000000000000000000000000000" for native.
sender	string	yes	Sender wallet address.

No output schema declared.

No examples provided.

get_bridge_quote ~198

Get a quote for bridging the same token from one chain to another (e.g. ETH on Ethereum → ETH on Base). Returns estimated output amount, fees breakdown, and time estimate. Use get_swap_quote instead if you want to change the token type.

Input Output Examples

Name	Type	Req	Description
amount	string	yes	Amount to bridge in the token's smallest unit (wei for ETH). Example: "1000000000000000000" for 1 ETH.
currency	string	yes	Token address to bridge. Use "0x0000000000000000000000000000000000000000" for native ETH.
destinationChainId	number	yes	Destination chain ID (e.g. 8453 for Base).
originChainId	number	yes	Source chain ID (e.g. 1 for Ethereum).
recipient	string	—	Recipient wallet address. Defaults to sender if not provided.
sender	string	yes	Sender wallet address.

No output schema declared.

No examples provided.

get_relay_app_url ~256

Generate a deep link to the Relay web app with pre-filled bridge/swap parameters. The user can open this URL in their browser to START a new transaction via the Relay UI. This is NOT a transaction tracking URL — do NOT use it to check on an in-progress transaction. For tracking, use get_transaction_status with the requestId.

Input Output Examples

Name	Type	Req	Description
amount	string	—	Pre-filled input amount in human-readable units (e.g. "0.1" for 0.1 ETH).
destinationChainId	number	yes	Destination chain ID (e.g. 8453 for Base). This determines the Relay app page.
fromChainId	number	—	Origin chain ID (e.g. 1 for Ethereum). If omitted, user picks in the UI.
fromCurrency	string	—	Origin token address. "0x0000000000000000000000000000000000000000" for native.
toAddress	string	—	Recipient wallet address.
toCurrency	string	—	Destination token address. "0x0000000000000000000000000000000000000000" for native.
tradeType	string	—	Trade type. Defaults to EXACT_INPUT.

No output schema declared.

No examples provided.

get_supported_chains ~78

List all blockchain networks supported by Relay for bridging and swapping. Returns chain IDs, names, native currencies, and status. Use this to resolve chain names to chain IDs before calling other tools.

Input Output Examples

Name	Type	Req	Description
vmType	string	—	Filter by virtual machine type (e.g. "evm", "svm"). Omit for all chains.

No output schema declared.

No examples provided.

get_supported_tokens ~132

Search for tokens supported by Relay across chains. Use this to find token contract addresses before getting quotes. Returns token symbol, name, address, and chain availability.

Input Output Examples

Name	Type	Req	Description
chainIds	array	—	Filter to specific chain IDs (e.g. [1, 8453] for Ethereum and Base). Omit for all chains.
limit	number	—	Max number of token groups to return. Defaults to 20.
term	string	—	Search by token name or symbol (e.g. "USDC", "ethereum").
verified	boolean	—	Only return verified tokens. Defaults to true.

No output schema declared.

No examples provided.

get_swap_quote ~218

Get a quote for swapping between different tokens, optionally across chains (e.g. ETH on Ethereum → USDC on Base, or USDC → WETH on the same chain). Returns estimated output amount, fees, and time estimate.

Input Output Examples

Name	Type	Req	Description
amount	string	yes	Amount to swap in the origin token's smallest unit (wei for ETH).
destinationChainId	number	yes	Destination chain ID. Can be the same as originChainId for same-chain swaps.
destinationCurrency	string	yes	Token address to swap to. Use "0x0000000000000000000000000000000000000000" for native ETH.
originChainId	number	yes	Source chain ID (e.g. 1 for Ethereum).
originCurrency	string	yes	Token address to swap from. Use "0x0000000000000000000000000000000000000000" for native ETH.
recipient	string	—	Recipient wallet address. Defaults to sender.
sender	string	yes	Sender wallet address.

No output schema declared.

No examples provided.

get_transaction_history ~87

Get past Relay bridge and swap transactions for a wallet address. Returns transaction IDs, statuses, chains, and timestamps. Supports pagination via cursor.

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Pagination cursor from a previous response. Omit for the first page.
limit	number	—	Max number of transactions to return. Defaults to 10.
user	string	yes	Wallet address to look up.

No output schema declared.

No examples provided.

get_transaction_status ~114

Check the status of a Relay bridge or swap transaction by requestId. Statuses: waiting — The origin chain transaction has been broadcast but not yet confirmed on-chain. pending — The relay network has picked up the request and is processing the cross-chain transfer. success — Complete. Funds have arrived on the destination chain. failure — The transaction failed. refund — The transaction was refunded to the sender.

Input Output Examples

Name	Type	Req	Description
requestId	string	yes	The Relay request ID for the transaction to check.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug