Bridge Metrics

Bridge Metrics MCP is a server that exposes real-time cross-chain bridge metrics through a programmable interface. You can query liquidity, volumes, historical data, and bridge transactions to power AI agents and analytic workflows across blockchain networks.

How to use

You interact with Bridge Metrics MCP using a compatible MCP client. The server exposes a set of tools that let you list chains, list bridges, fetch historical volumes, retrieve 24-hour token stats, and obtain transaction summaries for a bridge. Use natural language prompts or structured tool calls in your MCP client to obtain tabular results that you can feed into dashboards, models, or analyses. Typical workflows include comparing bridges by weekly or daily volumes, drilling into a chain’s historical activity, or examining token flows within a specific bridge.

How to install

Prerequisites you need before installation are Python 3.10 or higher and uv, the Python package and virtual environment manager used to run MCP servers.

Step 1. Clone the project repository to your machine.

Step 2. Install dependencies and prepare the environment using uv.

Step 3. Run the MCP server installer to register Bridge Metrics as a Claude Desktop application.

You can start with this exact setup flow to install and run Bridge Metrics MCP locally.

# Step 1: Clone the repository
# (Replace with your actual repository URL and path as you clone)
# git clone https://github.com/kukapay/bridge-metrics-mcp.git
# cd bridge-metrics-mcp

# Step 2: Install dependencies (if needed) and prepare environment
# uv sync

# Step 3: Install as a Claude Desktop application
# uv run mcp install main.py --name "Bridge Metrics"

# Example configuration snippet for the MCP runtime (config file)
{
  "mcpServers": {
    "Bridge Metrics": {
      "command": "uv",
      "args": [ "--directory", "/path/to/bridge-metrics-mcp", "run", "main.py" ]
    }
  }
}

Additional configuration and notes

The configuration example above shows how to register Bridge Metrics in your MCP runtime. You specify the runtime command and the full argument list needed to start the server from a given directory. If you customize the path, replace "/path/to/bridge-metrics-mcp" with your actual installation directory.

Tools and usage details

This MCP server provides the following capabilities you can invoke from your MCP client:

• list_chains: List all chain slugs from DeFiLlama, sorted by TVL. Output includes Name, Gecko ID, Token Symbol, Chain ID, TVL.
• list_bridges: List all bridges, optionally including chain breakdowns, sorted by 24-hour volume. Output includes ID, Name, Display Name, Last 24h Volume, Chains.
• get_historical_volumes: Fetch historical volumes for a chain or bridge with dates formatted as YYYY-MM-DD HH:MM:SS. Output includes Date, Deposit USD, Withdraw USD, Deposit Txs, Withdraw Txs.
• get_day_stats: Retrieve 24-hour token volume breakdowns, sorted by deposit USD value. Output includes Token ID, Symbol, Decimals, Deposit Amount, Deposit USD Value, Withdraw Amount, Withdraw USD Value.
• get_transactions: Fetch transaction summaries for a bridge, sorted by timestamp. Output includes Tx Hash, Timestamp, Block, From, To, Token, Amount, Type, Chain, Bridge Name, USD Value.
• prompts: Includes prompts such as analyze_bridge_volume and compare_bridges for higher-level analysis.

Notes on security and usability

Keep your MCP runtime secure and restrict access to trusted clients. Regularly update dependencies and monitor bridge data sources to ensure data integrity. If you run into issues, check that the runtime directory path in your configuration matches where Bridge Metrics is installed.

Available tools

list_chains

Lists all chain slugs from DeFiLlama, sorted by TVL, returning a table with Name, Gecko ID, Token Symbol, Chain ID, TVL.

list_bridges

Lists all bridges, optionally including chain breakdowns, sorted by 24-hour volume. Returns a table with ID, Name, Display Name, Last 24h Volume, Chains.

get_historical_volumes

Fetches historical volumes for a chain or bridge with dates formatted as YYYY-MM-DD HH:MM:SS. Output includes Date, Deposit USD, Withdraw USD, Deposit Txs, Withdraw Txs.

get_day_stats

Retrieves 24-hour token volume breakdowns, sorted by deposit USD value. Output includes Token ID, Symbol, Decimals, Deposit Amount, Deposit USD Value, Withdraw Amount, Withdraw USD Value.

get_transactions

Fetches transaction summaries for a bridge, sorted by timestamp. Output includes Tx Hash, Timestamp, Block, From, To, Token, Amount, Type, Chain, Bridge Name, USD Value.

analyze_bridge_volume

Analyze volume data for a specific bridge, synthesizing insights from historical and recent volumes.

compare_bridges

Compare two bridges based on a specified metric, such as weeklyVolume, to surface relative performance.