Skip to main content
Glama
Sign In
warengonzaga

Relay Protocol MCP Server

by warengonzaga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid
README.md
# Relay Protocol MCP Server

The first community-built MCP server for Relay Protocol.

## Status: discontinued

Relay Protocol is still active. This community project is retired because its API access is changing, and Relay's team now provides its own MCP server.

Read Relay's [Requests v3 migration guide](https://docs.relay.link/references/api/api_guides/migrating-to-requests-v3).

This server no longer fetches Relay data. It only returns a retirement notice; the original source remains here for reference.

## License

MIT. See [LICENSE](LICENSE).
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation4/5

Tools are mostly distinct with clear purposes. Slight overlap between get_execution_status and get_requests (both provide status info) and between transactions_index and transactions_single, but descriptions help differentiate.

Naming Consistency3/5

Naming follows a consistent 'relay_' prefix, but verbs are mixed: 'get_' tools are verb_noun, while 'swap_multi_input' and 'transactions_index'/'transactions_single' deviate from that pattern, causing inconsistency.

Tool Count5/5

9 tools is appropriate for the cross-chain swap domain. Each tool covers a distinct step in the workflow without being excessive or insufficient.

Completeness4/5

Core workflows (discover chains/tokens, get quotes, execute swaps, monitor status) are well-covered. Minor gaps like token approval management are absent but not critical for basic operations.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources