LI.FI MCP
Official hosted LI.FI MCP server for read-only cross-chain swap quotes and route discovery.
- Sato Score62
- ChainsMultichain
LI.FI MCP is a MCP server by LI.FI, with no code activity tracked. Sato Score 62/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →
See how to install LI.FI MCP →No code activity tracked
Listed from li.fi on 2026-07-13. Install: not attempted. Evidence →
Next step
Watch LI.FI MCP
One email if what we observe changes — its endpoint stops answering, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on https://mcp.li.quest/mcp before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
LI.FI MCP is a hosted MCP server at mcp.li.quest/mcp, operated by LI.FI, wrapping its cross-chain swap/bridge REST API for AI tools. It exposes read-only tools such as get-quote and get-chains, generating unsigned swap/route transaction objects across 58 chains, 27+ bridges, and 31+ DEXs — the agent's own wallet must sign and broadcast anything returned. An agent builder plugs this in as the cross-chain routing/quoting layer for a trading or swap agent.
Sato Score
62/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 0/20
- Interface verifiability
- 10/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 9/15
- Independent verification
- 2/10
Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).
Evidence — listed vs checked · what the words mean
Listed from li.fi on 2026-07-13. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | docs.li.fi | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | li.fi | as of 2026-10-15 |
| Install works | documented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_spec | self-reported | docs.li.fi | as of 2026-09-14 |
| MCP endpoint answers | answered — 25 tools listed | observed | mcp.li.quest | 2026-10-15 |
| Daily check record | 89 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| Deploys as | Hosted (remote MCP endpoint, no install required)confidence 0.85 | self-reported | docs.li.fi | as of 2026-07-14 |
| Sato Score | 62/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-15 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — not run by us — no falsifiable install+entry probe from deploy_spec
Runtime: remote
add {"type": "http", "url": "https://mcp.li.quest/mcp"} to your MCP client config
{"mcpServers": {"lifi": {"type": "http", "url": "https://mcp.li.quest/mcp"}}}claude mcp add --transport http satohub-lifi-mcp https://mcp.li.quest/mcp
A remote server: your client connects to the project's endpoint. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-09-14. What a deploy spec is →
Tool inventory — 25 tools, probed live 2026-10-15
get-allowance— Check how many ERC20 tokens a spender is approved to use on behalf of an owner (EVM chains only). IMPORTANT: Before executing a swap with ERC20 tokens, verify the allowance is >= the swap amount. If iget-chain-by-id— Look up chain details by numeric chain ID. Returns chain name, native token info, RPC URLs, and block explorer. Use this to convert a chain ID to human-readable information or to get RPC URLs.get-chain-by-name— Look up chain details by name or key. Performs case-insensitive matching against chain name, key, or ID. Use this when you know the chain name but need its ID or RPC URL.get-chains— Get a list of all blockchain networks supported by LI.FI. Returns chain IDs, names, native tokens, RPC URLs, and block explorer URLs. Use this to discover available chains or get RPC URLs for blockchaget-connections— Discover which token pairs can be swapped between chains. Use this to check if a specific swap route exists before calling get-quote. Returns available bridges and their supported tokens for the speciget-earn-chains— List blockchain networks that have indexed yield vaults in the Earn API. Returns chain IDs, names, and CAIP-2 identifiers. This is a SUBSET of all LI.FI-supported chains (use get-chains for the full lget-earn-portfolio— Check a wallet's active yield positions (vault deposits, staking, lending) across all supported protocols and chains in a single call. Returns each position with protocol name, asset details, balanceget-earn-protocols— List all yield protocols integrated with the Earn API. Returns protocol names in kebab-case format (e.g., 'morpho-v1', 'aave-v3', 'euler-v2', 'pendle', 'ethena-usde', 'maple') and their app URLs. Useget-earn-vault— Get full details for a specific yield vault by chain and contract address. Returns vault name, APY breakdown (base/reward/total), historical APY (apy1d/apy7d/apy30d), TVL in USD, underlying tokens witget-earn-vaults— Search and discover yield-earning vaults (DeFi yield, APY, interest, staking, lending) across 20+ protocols and 17+ chains. This is the PRIMARY tool for finding yield opportunities — use it when a useget-gas-prices— Get current gas prices for all supported EVM chains. Returns fast/standard/slow gas prices in gwei. Useful for estimating transaction costs before executing swaps or for monitoring network congestion.get-gas-suggestion— Get recommended gas parameters for a specific chain including base fee, priority fee, and estimated costs. More detailed than get-gas-prices for a single chain. Useful when constructing transactions mget-native-token-balance— Check the native token balance of any wallet address. Supports EVM chains (ETH, MATIC, etc.) and Solana (SOL). Returns the balance in the smallest unit (wei for EVM, lamports for Solana) along with thget-quote— Get a quote for swapping, bridging, or depositing into yield vaults. This is the PRIMARY tool for any token operation. Returns the best route including expected output amount, fees, estimated time, anget-quote-with-calls— Get a quote that includes custom smart contract calls on the destination chain, also known as 'Zaps' (EVM chains only). This enables complex DeFi operations in a single transaction: bridge tokens ANDget-routes— Get multiple route options for a swap to compare alternatives. Unlike get-quote which returns the single best route, this returns several options ranked by the specified order preference. Useful whenget-status— Check the status of an in-progress or completed cross-chain transfer. Use this to track bridge transactions which can take minutes to hours. Returns status (PENDING, DONE, FAILED), source/destinationget-step-transaction— Convert a route step from get-routes into executable transaction data. Use this when you've chosen a specific route from get-routes and need the transaction to sign and send. Returns the same transactget-token— Get detailed information about a specific token including its address, symbol, decimals, and current price. Use this to verify token details before a swap or to look up a token by its symbol.get-token-balance— Check the token balance of any wallet address. Supports EVM chains (ERC20 tokens) and Solana (SPL tokens). Returns the balance in the token's smallest unit along with symbol and decimals. Use this befget-token-balances— Check multiple ERC20 token balances for a wallet in a single call using Multicall3. Much more efficient than calling get-token-balance repeatedly. Also returns the native token balance. Use this to scget-tokens— Retrieve a list of all tokens supported by LI.FI across multiple chains. Use this to discover available tokens before executing swaps. Returns token addresses, symbols, decimals, and price informationget-tools— List all available bridges and DEX aggregators that LI.FI can route through. Use this to discover which protocols are available or to get bridge/exchange names for filtering in get-quote. Returns keyhealth-check— Check the health status of the LiFi MCP server. Returns server version and API connectivity status. Use this for health monitoring and orchestration.test-api-key— Test if the LI.FI API key provided in the request header is valid. Returns key status and rate limit information. Requires API key to be passed via Authorization header (Bearer token) or X-LiFi-Api-Ke
- Answers a handshake
- yes · 2026-10-15
- Answers a call
- yes — get-chains returned in 166 ms
Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.
Observed record — 91 daily checks since 2026-07-17
- Succeeded
- 90
- Failed
- 1
- Their error
- 1
- Unattributed
- 0
State changed on 2026-09-21 (responding → failing), 2026-09-22 (failing → responding).
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-15, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Multichain
- Agent types
- Data Provider, Trading
- Open source
- Unknown
- Pricing
- Free tier: 200 requests/2 hours; API key tier: 200 requests/minute
- Deploys as
- Hosted (remote MCP endpoint, no install required)
- Last checked
- 2026-10-15
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where LI.FI MCP fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are Onchain Agents?
Listing History
Recorded changes to LI.FI MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 22, 2026Sato Score tier: Low → MediumScore 36 → 62.
- Sep 21, 2026Sato Score tier: Medium → LowScore 63 → 36.
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Edited: mcp endpoint url
- Jul 14, 2026Auto-enriched: deployment options
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Bankr
ActiveCrypto execution layer and cross-chain wallet that lets agents and users trade, bridge, and manage assets via natural language, plus a skills marketplace and an x402 cloud for spinning up pay-per-call agent endpoints.
Phantom MCP
ActivePhantom's MCP server that lets AI agents view addresses, sign transactions, swap, and transfer tokens across Solana, Ethereum, Bitcoin, and Sui.
Enso
ActiveAn intent-based onchain execution engine and API that lets developers and agents bundle multi-step DeFi actions into a single transaction.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about LI.FI MCP
- Is LI.FI MCP open source?
- Unknown. Sato Hub has not found a public repository or a license statement for LI.FI MCP as of 2026-10-15.
- Which chains does LI.FI MCP support?
- LI.FI MCP lists support for Multichain as of 2026-10-15.
- Is LI.FI MCP still maintained?
- Sato Hub tracks no commit or release for LI.FI MCP; it cannot say whether it is maintained.
- How do I install or run LI.FI MCP?
- remote. Install: add {"type": "http", "url": "https://mcp.li.quest/mcp"} to your MCP client config. Entry: {"mcpServers": {"lifi": {"type": "http", "url": "https://mcp.li.quest/mcp"}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (https://mcp.li.quest/mcp).
- Is LI.FI MCP verified on Sato Hub?
- Sato Hub holds one earned check for LI.FI MCP: Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety). Its Sato Score is 62 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "LI.FI MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/lifi-mcpData last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.