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.

Relay

NPM · @RELAYPROTOCOL/RELAY-MCP · SCANNED SEP 20

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

Available components

npm · @relayprotocol/relay-mcp 78
0 this week 78 Trust /100
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 Security98
  • 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
  • 31 of 96 dependencies flagged as unhealthy. 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 193 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
  • 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 Management93
  • Stability observed for 28 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
Install

How do I install the Relay MCP server?

Relay runs locally as an npm package, launched with npx -y @relayprotocol/relay-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 · @relayprotocol/relay-mcp

# add to Claude Code
claude mcp add reservoirprotocol-relay-mcp -- npx -y @relayprotocol/relay-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "reservoirprotocol-relay-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@relayprotocol/relay-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "reservoirprotocol-relay-mcp": {
      "command": "npx",
      "args": [
        "-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"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "reservoirprotocol-relay-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@relayprotocol/relay-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add reservoirprotocol-relay-mcp -t stdio -c npx -a -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.

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 15 Sept 26 −4
    • Stability: pass → 0.77 functional
  • 14 Sept 26 +1
    • Stability: 0.97 → pass security
  • 12 Sept 26 +1

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

  • 10 Sept 26 +1

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

  • 9 Sept 26 −3
    • Stability: pass → 0.83 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 20 Sept 2026 · Analysed npm/@relayprotocol/relay-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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. 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
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.

NameTypeReqDescription
amountstringyesAmount in the origin token's smallest unit.
destinationChainIdnumberyesDestination chain ID.
destinationCurrencystringyesDestination token address. "0x0000000000000000000000000000000000000000" for native.
originChainIdnumberyesSource chain ID.
originCurrencystringyesOrigin token address. "0x0000000000000000000000000000000000000000" for native.
senderstringyesSender 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.

NameTypeReqDescription
amountstringyesAmount to bridge in the token's smallest unit (wei for ETH). Example: "1000000000000000000" for 1 ETH.
currencystringyesToken address to bridge. Use "0x0000000000000000000000000000000000000000" for native ETH.
destinationChainIdnumberyesDestination chain ID (e.g. 8453 for Base).
originChainIdnumberyesSource chain ID (e.g. 1 for Ethereum).
recipientstring–Recipient wallet address. Defaults to sender if not provided.
senderstringyesSender 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.

NameTypeReqDescription
amountstring–Pre-filled input amount in human-readable units (e.g. "0.1" for 0.1 ETH).
destinationChainIdnumberyesDestination chain ID (e.g. 8453 for Base). This determines the Relay app page.
fromChainIdnumber–Origin chain ID (e.g. 1 for Ethereum). If omitted, user picks in the UI.
fromCurrencystring–Origin token address. "0x0000000000000000000000000000000000000000" for native.
toAddressstring–Recipient wallet address.
toCurrencystring–Destination token address. "0x0000000000000000000000000000000000000000" for native.
tradeTypestring–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.

NameTypeReqDescription
vmTypestring–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.

NameTypeReqDescription
chainIdsarray–Filter to specific chain IDs (e.g. [1, 8453] for Ethereum and Base). Omit for all chains.
limitnumber–Max number of token groups to return. Defaults to 20.
termstring–Search by token name or symbol (e.g. "USDC", "ethereum").
verifiedboolean–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.

NameTypeReqDescription
amountstringyesAmount to swap in the origin token's smallest unit (wei for ETH).
destinationChainIdnumberyesDestination chain ID. Can be the same as originChainId for same-chain swaps.
destinationCurrencystringyesToken address to swap to. Use "0x0000000000000000000000000000000000000000" for native ETH.
originChainIdnumberyesSource chain ID (e.g. 1 for Ethereum).
originCurrencystringyesToken address to swap from. Use "0x0000000000000000000000000000000000000000" for native ETH.
recipientstring–Recipient wallet address. Defaults to sender.
senderstringyesSender 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.

NameTypeReqDescription
cursorstring–Pagination cursor from a previous response. Omit for the first page.
limitnumber–Max number of transactions to return. Defaults to 10.
userstringyesWallet 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.

NameTypeReqDescription
requestIdstringyesThe Relay request ID for the transaction to check.

No output schema declared.

No examples provided.

Common questions

What is the Relay MCP server?

Relay is an MCP server listed in the public MCP registry as io.github.reservoirprotocol/relay-mcp. Cross-chain bridge and swap quotes, fee estimation, and transaction tracking via Relay Protocol. This page covers its npm package (@relayprotocol/relay-mcp).

Is the Relay MCP server safe to use?

Relay scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 Relay MCP server expose?

Relay exposes 8 tools: get_supported_chains, get_supported_tokens, get_bridge_quote, get_swap_quote, estimate_fees, and 3 more. Their descriptions and schemas cost roughly 1,244 tokens of context every time the server is loaded.

Is the Relay MCP server still maintained?

Relay is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Relay MCP server under?

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