# xyz.tenzro/tenzro-lifi (remote · lifi-mcp.tenzro.xyz)

Li.Fi tools over MCP: cross-chain quotes, routes, execution status, chains, tokens, balances.

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `lifi-mcp.tenzro.xyz`: 66/100 (this document), [markdown](https://verifymcp.io/servers/xyz-tenzro-tenzro-lifi/lifi-mcp.md), [page](https://verifymcp.io/servers/xyz-tenzro-tenzro-lifi/lifi-mcp)

## Channel facts

- Endpoint: `https://lifi-mcp.tenzro.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1139 tokens (~126/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http xyz-tenzro-tenzro-lifi https://lifi-mcp.tenzro.xyz/mcp
```

### Codex

```toml
[mcp_servers.xyz-tenzro-tenzro-lifi]
url = "https://lifi-mcp.tenzro.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-tenzro-tenzro-lifi": {
      "type": "remote",
      "url": "https://lifi-mcp.tenzro.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-tenzro-tenzro-lifi --url https://lifi-mcp.tenzro.xyz/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-tenzro-tenzro-lifi:
    url: "https://lifi-mcp.tenzro.xyz/mcp"
```

### Other

```json
{
  "mcpServers": {
    "xyz-tenzro-tenzro-lifi": {
      "type": "http",
      "url": "https://lifi-mcp.tenzro.xyz/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (9)

### `lifi_get_chains` (~43 tokens)

Get all blockchain networks supported by LI.FI for cross-chain transfers and swaps. Returns chain IDs, names, native tokens, and supported bridge/exchange protocols.

Output parameters:

- `result`: Underlying response payload verbatim.

### `lifi_get_connections` (~118 tokens)

Get available cross-chain connections between two chains. Optionally filter by source and destination tokens. Shows which bridges and exchanges can transfer between the specified chains.

Input parameters:

- `from_chain` (integer, required): Source chain ID (e.g. 1 for Ethereum)
- `from_token` (string|null): Source token address (optional, filters connections to specific token)
- `to_chain` (integer, required): Destination chain ID (e.g. 137 for Polygon)
- `to_token` (string|null): Destination token address (optional, filters connections to specific token)

Output parameters:

- `result`: Underlying response payload verbatim.

### `lifi_get_gas_prices` (~70 tokens)

Get current gas prices for LI.FI-supported chains. Optionally filter by chain IDs. Returns gas prices in native units for each chain.

Input parameters:

- `chains` (string|null): Comma-separated chain IDs (e.g. '1,137,42161'). Omit for all chains.

Output parameters:

- `result`: Underlying response payload verbatim.

### `lifi_get_quote` (~204 tokens)

Get a single best quote for a cross-chain swap or bridge transfer. Returns the optimal route with estimated output, fees, execution time, and transaction data ready to sign.

Input parameters:

- `from_address` (string, required): Sender wallet address (0x...)
- `from_amount` (string, required): Amount in smallest unit (wei for ETH, base units for ERC-20)
- `from_chain` (integer, required): Source chain ID (e.g. 1 for Ethereum)
- `from_token` (string, required): Source token address (e.g. '0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48' for USDC)
- `slippage` (number|null): Slippage tolerance as decimal (default 0.03 = 3%)
- `to_chain` (integer, required): Destination chain ID (e.g. 137 for Polygon)
- `to_token` (string, required): Destination token address

Output parameters:

- `result`: Underlying response payload verbatim.

### `lifi_get_routes` (~163 tokens)

Get multiple route options for a cross-chain swap or bridge transfer, ranked by output amount. Use this for comparing routes across different bridges and DEXes. Returns routes with fees, estimated time, and step-by-step breakdown.

Input parameters:

- `from_address` (string, required): Sender wallet address (0x...)
- `from_amount` (string, required): Amount in smallest unit (wei for ETH, base units for ERC-20)
- `from_chain_id` (integer, required): Source chain ID
- `from_token_address` (string, required): Source token address
- `slippage` (number|null): Slippage tolerance as decimal (default 0.03 = 3%)
- `to_chain_id` (integer, required): Destination chain ID
- `to_token_address` (string, required): Destination token address

Output parameters:

- `result`: Underlying response payload verbatim.

### `lifi_get_status` (~126 tokens)

Check the status of a cross-chain transfer by transaction hash. Returns status (PENDING, DONE, FAILED, NOT_FOUND), bridge used, source/destination chain info, and amounts.

Input parameters:

- `bridge` (string|null): Bridge name (optional, e.g. 'stargate', 'hop', 'across')
- `from_chain` (integer|null): Source chain ID (optional, helps disambiguate)
- `to_chain` (integer|null): Destination chain ID (optional, helps disambiguate)
- `tx_hash` (string, required): Transaction hash to check status for

Output parameters:

- `result`: Underlying response payload verbatim.

### `lifi_get_token` (~142 tokens)

Get detailed information about a specific token on a specific chain, including address, symbol, decimals, name, and logo URI.

Input parameters:

- `chain_id` (integer, required): Chain ID (e.g. 1 for Ethereum, 137 for Polygon, 42161 for Arbitrum)
- `token_address` (string, required): Token contract address (e.g. '0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48' for USDC on Ethereum). Use '0x0000000000000000000000000000000000000000' for native tokens.

Output parameters:

- `result`: Underlying response payload verbatim.

### `lifi_get_tokens` (~71 tokens)

Get tokens available on LI.FI-supported chains. Optionally filter by chain IDs. Returns token addresses, symbols, decimals, and logos.

Input parameters:

- `chains` (string|null): Comma-separated chain IDs to filter tokens (e.g. '1,137,42161'). Omit for all chains.

Output parameters:

- `result`: Underlying response payload verbatim.

### `lifi_get_tools` (~39 tokens)

Get available bridge and DEX exchange tools integrated into LI.FI. Returns protocol names, supported chains, and tool types (bridge vs exchange).

Output parameters:

- `result`: Underlying response payload verbatim.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-tenzro-tenzro-lifi/lifi-mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 65
- 2026-07-29: 64
- 2026-07-28: 64
- 2026-07-27: 63
- 2026-07-26: 62

## Links

- Remote endpoint: https://lifi-mcp.tenzro.xyz/mcp
- Changelog RSS feed: https://verifymcp.io/servers/xyz-tenzro-tenzro-lifi/lifi-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-tenzro-tenzro-lifi/lifi-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/xyz-tenzro-tenzro-lifi/lifi-mcp