Skip to main content
Glama
kukapay

Bridge Metrics MCP

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_chainsA
Fetch and return a list of all chain slugs from DeFiLlama in a table format, sorted by TVL in descending order.
No parameters required.
Returns a table of chains data with columns: name, gecko_id, tokenSymbol, chainId, tvl.
list_bridgesA
Fetch and return a list of all bridges from DeFiLlama in a table format, sorted by last24hVolume in descending order.
Parameters:
- include_chains: boolean (optional, default False) - Whether to include current previous day volume breakdown by chain.
Returns a table of bridges data with columns: id, name, displayName, last24hVolume, chains.
get_historical_volumesA
Fetch and return historical volumes for a bridge, chain, or specific bridge on a chain in a table format.
Parameters:
- chain: string (required) - Chain slug (from list_chains) or 'all' for all chains.
- bridge_id: integer (optional) - The ID of the bridge (obtain from list_bridges).
Returns a table of historical volumes with columns: date, depositUSD, withdrawUSD, depositTxs, withdrawTxs.
get_day_statsB
Fetch and return a 24hr token volume breakdown for a bridge on a specific day in a table format.
Parameters:
- timestamp: integer (required) - Unix timestamp for the day (data for 24hr period starting at 00:00 UTC).
- chain: string (required) - Chain slug (from list_chains).
- bridge_id: integer (optional) - The ID of the bridge (obtain from list_bridges).
Returns a table of token stats with columns: token id, symbol, decimals, deposit amount, deposit usd value, withdraw amount, withdraw value, sorted by deposit usd value in descending order.
get_transactionsA
Fetch and return all transactions for a bridge within a specified date range in a table format.
Parameters:
- bridge_id: integer (required) - The ID of the bridge (obtain from list_bridges).
- start_timestamp: integer (optional) - Start Unix timestamp for the date range.
- end_timestamp: integer (optional) - End Unix timestamp for the date range.
- source_chain: string (optional) - Filter transactions bridging from this source chain.
- address: string (optional) - Filter transactions where this address is 'from' or 'to' (format: {chain}:{address}).
- limit: integer (optional) - Limit number of transactions returned (max 6000).
Returns a table of transaction data with key metrics.

Prompts

Interactive templates invoked by user choice

NameDescription
analyze_bridge_volume Analyze the volume data for a specific bridge. Parameters: - bridge_name: The name of the bridge. - data: Table or JSON string of volume data from tools like get_bridge_summary or get_historical_volumes.
compare_bridges Compare two bridges based on a specific metric. Parameters: - bridge1: Name or ID of the first bridge. - bridge2: Name or ID of the second bridge. - metric: The metric to compare (e.g., 'weeklyVolume', 'monthlyVolume', default 'weeklyVolume').

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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