Skip to main content
Glama
kukapay

Bridge Metrics MCP

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Bridge Metrics MCP

No user-submitted related servers found.

    Related Servers

    • Arbitrum Bridge MCP Server

      WuodOdhis
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to perform cross-chain bridging operations using natural language intents, with support for multiple protocols (Across, Stargate) and advanced security features like oracle validation and slippage protection. Provides comprehensive bridging tools including quote estimation, transaction building, and approval management across Arbitrum and Ethereum networks.
      MIT

    • Relay MCP Server

      relayprotocol
      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

    • arb-dex-mcp

      donnywin85
      A
      license
      A
      quality
      B
      maintenance
      Provides live cross-DEX market data on six EVM chains, including per-venue prices, liquidity, and gross spreads with optimal trade sizes. Enables AI agents to query real on-chain data for BSC, Polygon, Arbitrum, Base, Avalanche, and Optimism via MCP tools.
      4
      44 npm
      MIT
    • orbit-api by Orbit-bridge

      orbit-apiofficial

      Orbit-bridge
      F
      license
      Not graded
      quality
      F
      maintenance
      MCP server for cross-chain bridging, enabling AI agents to find routes, estimate costs, check risks, execute transfers, and track status across blockchains.
      -
    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

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clear distinct purpose: listing bridges/chains, daily token stats, historical aggregate volumes, and transaction details. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent 'verb_noun' pattern in snake_case: 'get_' for data retrieval and 'list_' for enumeration. No mixing of styles or vague verbs.

    Tool Count5/5

    5 tools is well-scoped for the domain of bridge metrics. It covers discovery (list_bridges, list_chains) and detailed queries (day stats, historical volumes, transactions) without being overwhelming or sparse.

    Completeness5/5

    The tool set provides comprehensive coverage for a read-only bridge metrics API: listing all bridges and chains, retrieving daily token breakdowns, historical aggregate volumes, and individual transactions with filters. No obvious gaps for typical use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources