Relay

io.github.relayprotocolPublished by GitHub account relayprotocolv0.1.1Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyFinanceDeveloper Tools

Overview

AI-generated overview

Relay lets an assistant fetch cross-chain bridge and swap quotes, estimate fees, and track transactions through the Relay Protocol API.

What you can do
Get cross-chain bridge and swap quotes for moving assets between chains. Estimate fees before committing to a route. Track the status of submitted transactions. Optionally authenticate with an API key to raise rate limits.
When to use it
Useful when an assistant needs to look up cross-chain routes, compare bridge or swap costs, or follow the progress of a transfer across chains.
Requirements
Runs as a local process via the npm package @relayprotocol/relay-mcp over stdio. Needs network access to the Relay API; the base URL can be overridden with RELAY_API_URL. An optional RELAY_API_KEY raises rate limits.
Before you install
The optional RELAY_API_KEY is a secret passed by environment variable. Quotes and fee estimates are informational and may change; verify routes and costs before acting on them. Transaction tracking depends on data sent to the third-party Relay API.

Installation

In SourceWeft

  1. Open Relay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.