1. Conduid
  2. Browser
  3. Lifi MCP
MCP server · Browser

Lifi MCP

MCP server that integrates with the [LI.FI API](https://li.quest)

Unclaimed MIT last commit a year ago browser
47Fair

Scored 5 months ago · breakdown

About Lifi MCP

Lifi MCP is an MCP server published by mcpflow in the Browser category: mCP server that integrates with the [LI.FI API](https://li.quest).

Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/mcpflow/lifi-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Lifi MCP

Powered by Claude · Grounded in docs

I know everything about Lifi MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

3 checks have not been run yet.

README

LI.FI MCP Server

⚠️ IMPORTANT SECURITY DISCLAIMER ⚠️

DO NOT use this tool with your main wallet keystore or wallets containing significant funds!

This tool is for testing and experimental purposes only. There is potential for loss of funds due to:

  • Software bugs or security vulnerabilities
  • Transaction errors or misconfigurations
  • Network issues or smart contract failures

Neither LI.FI nor the developers of this tool are responsible for any loss of funds resulting from the use of this freely available open-source software.

Use at your own risk with test wallets only.

This MCP server integrates with the LI.FI API to provide cross-chain swap functionality across multiple liquidity pools and bridges.

Components

Tools

Token Information

  • GetTokens

    • Fetch all tokens known to the LI.FI services
    • Parameters: chains, chainTypes, minPriceUSD
  • GetToken

    • Get detailed information about a specific token
    • Parameters: chain (required), token (required)

Chain Information

  • GetChains

    • Get information about all supported chains
    • Parameters: chainTypes
  • GetChainById

    • Find a chain by its numeric ID
    • Parameters: id (required)
  • GetChainByName

    • Find a chain by name, key, or ID (case insensitive)
    • Parameters: name (required)

Cross-Chain Operations

  • GetQuote

    • Get a quote for a token transfer (cross-chain or same-chain)
    • Parameters: fromChain, toChain, fromToken, toToken, fromAddress, fromAmount, etc.
  • GetStatus

    • Check the status of a cross-chain transfer
    • Parameters: txHash (required), bridge, fromChain, toChain
  • GetConnections

    • Returns all possible connections between chains
    • Parameters: fromChain, toChain, fromToken, toToken, chainTypes
  • GetTools

    • Get available bridges and exchanges
    • Parameters: chains

Wallet Operations

  • GetWalletAddress

    • Get the Ethereum address for the loaded private key
  • GetNativeTokenBalance

    • Get the native token balance of a wallet
    • Parameters: rpcUrl (required), address (required)
  • GetTokenBalance

    • Get the balance of a specific ERC20 token for a wallet
    • Parameters: rpcUrl, tokenAddress, walletAddress
  • GetAllowance

    • Check the allowance of an ERC20 token for a specific spender
    • Parameters: rpcUrl, tokenAddress, ownerAddress, spenderAddress

Transaction Operations

  • ExecuteQuote

    • Execute a quote transaction using the stored private key
    • Parameters: rpcUrl, transactionRequest
  • ApproveToken

    • Approve a specific amount of ERC20 tokens to be spent by another address
    • Parameters: rpcUrl, tokenAddress, spenderAddress, amount
  • TransferToken

    • Transfer ERC20 tokens to another address
    • Parameters: rpcUrl, tokenAddress, to, amount
  • TransferNative

    • Transfer native cryptocurrency to another address
    • Parameters: rpcUrl, to, amount

Getting Started

Installation

Using the Install Script

You can install the LI.FI MCP server using the following command:

curl https://raw.githubusercontent.com/lifinance/lifi-mcp/refs/heads/main/install.sh | bash

Using Go Install

Alternatively, you can install using Go:

go install github.com/lifinance/lifi-mcp@latest

Wallet Management

Using an Existing Keystore

Run the server with an Ethereum keystore file:

lifi-mcp server --keystore <keystore-name> --password <keystore-password>

The server will search for a file containing this name in the standard Ethereum keystore directory:

  • Linux: ~/.ethereum/keystore
  • macOS: ~/Library/Ethereum/keystore
  • Windows: %APPDATA%\Ethereum\keystore

Creating a New Wallet

Create a new wallet keystore:

lifi-mcp new-wallet --name <wallet-name> --password <wallet-password>

This generates a new Ethereum wallet, saves it to the standard keystore location, and displays the wallet address.

Usage with Desktop App

To integrate this server with the desktop app, add the following to your app's server configuration:

{
  "mcpServers": {
    "lifi": {
      "command": "lifi-mcp",
      "args": ["server"]
    }
  }
}

For wallet functionality, include keystore parameters:

{
  "mcpServers": {
    "lifi": {
      "command": "lifi-mcp",
      "args": ["server", "--keystore", "your-keystore", "--password", "your-password"]
    }
  }
}

License

MIT

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Lifi MCP

How do I install Lifi MCP?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Lifi MCP safe to use with an AI agent?

Its trust score is 47 out of 100 (fair). It passes 2 of the 3 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Lifi MCP still maintained?

The last commit was a year ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.