Skip to main content
Glama
warengonzaga

Relay Protocol MCP Server

by warengonzaga

Related Servers

Alternatives to Relay Protocol MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides cross-chain bridge and swap tools for AI agents using the Relay Protocol to interact with multiple blockchain networks. It enables agents to query supported chains, obtain transaction quotes, and generate unsigned transaction data for token transfers and swaps.
      10
      38 npm
      4
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables AI agents to interact with any EVM-compatible blockchain through natural language, supporting token swaps, cross-chain bridges, staking, lending, governance, gas optimization, and portfolio tracking across networks like Ethereum, BSC, Polygon, Arbitrum, and more.
      100
      30 npm
      41
      -
    • F
      license
      Not graded
      quality
      F
      maintenance
      Enables cross-chain cryptocurrency swap quotes and operations using the deBridge DLN protocol. Provides read-only access to swap estimates, supported chains, token information, and order status tracking across multiple blockchain networks.
      1
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables cross-chain swap execution across 12 venues and 17 chains, including native Bitcoin as source or destination, with tools for quoting, execution, status, and health checks. No signup, API key, or protocol fee required.
      5
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Provides access to Tatum's blockchain API across 40+ networks, enabling developers to interact with blockchain data, manage notifications, estimate fees, access RPC nodes, and work with smart contracts through natural language.
      31
      87 npm
      15
      MIT

    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

    ActivityInactive
    ResponsivenessNo issues