Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

xyz.tenzro/tenzro-lifi

REMOTE · LIFI-MCP.TENZRO.XYZ · SCANNED AUG 21

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

Available components

remote · lifi-mcp.tenzro.xyz 0
−55 this week 0 Trust /100

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security0
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety–

Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.

Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the xyz.tenzro/tenzro-lifi MCP server?

xyz.tenzro/tenzro-lifi is a hosted endpoint at https://lifi-mcp.tenzro.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · lifi-mcp.tenzro.xyz

# add to Claude Code
claude mcp add --transport http xyz-tenzro-tenzro-lifi 'https://lifi-mcp.tenzro.xyz/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "xyz-tenzro-tenzro-lifi": {
      "url": "https://lifi-mcp.tenzro.xyz/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "xyz-tenzro-tenzro-lifi": {
      "type": "http",
      "url": "https://lifi-mcp.tenzro.xyz/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add xyz-tenzro-tenzro-lifi --url 'https://lifi-mcp.tenzro.xyz/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  xyz-tenzro-tenzro-lifi:
    url: "https://lifi-mcp.tenzro.xyz/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "xyz-tenzro-tenzro-lifi": {
      "Transport": "http",
      "Url": "https://lifi-mcp.tenzro.xyz/mcp"
    }
  }
}
# add to Vellum
assistant mcp add xyz-tenzro-tenzro-lifi -t streamable-http -u 'https://lifi-mcp.tenzro.xyz/mcp'
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Aug 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 17 Aug 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 16 Aug 26 −13

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 15 Aug 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 13 Aug 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Aug 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: 0.47 → unverified ▼ security
    • HTTPS: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 8 Aug 26 +1

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

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Aug 2026 · Probed https://lifi-mcp.tenzro.xyz/mcp

TLS unreached

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of lifi-mcp.tenzro.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
tenzro.xyz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://lifi-mcp.tenzro.xyz/mcp Unreachable
http (plaintext) http://lifi-mcp.tenzro.xyz/mcp Inconclusive 404
MCP tools · 9 exposed · ~976 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
lifi_get_chains ~43

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
result–yesUnderlying response payload verbatim.

No examples provided.

lifi_get_connections ~118

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.

NameTypeReqDescription
from_chainintegeryesSource chain ID (e.g. 1 for Ethereum)
from_tokenstring|null–Source token address (optional, filters connections to specific token)
to_chainintegeryesDestination chain ID (e.g. 137 for Polygon)
to_tokenstring|null–Destination token address (optional, filters connections to specific token)
NameTypeReqDescription
result–yesUnderlying response payload verbatim.

No examples provided.

lifi_get_gas_prices ~70

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

NameTypeReqDescription
chainsstring|null–Comma-separated chain IDs (e.g. '1,137,42161'). Omit for all chains.
NameTypeReqDescription
result–yesUnderlying response payload verbatim.

No examples provided.

lifi_get_quote ~204

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.

NameTypeReqDescription
from_addressstringyesSender wallet address (0x...)
from_amountstringyesAmount in smallest unit (wei for ETH, base units for ERC-20)
from_chainintegeryesSource chain ID (e.g. 1 for Ethereum)
from_tokenstringyesSource token address (e.g. '0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48' for USDC)
slippagenumber|null–Slippage tolerance as decimal (default 0.03 = 3%)
to_chainintegeryesDestination chain ID (e.g. 137 for Polygon)
to_tokenstringyesDestination token address
NameTypeReqDescription
result–yesUnderlying response payload verbatim.

No examples provided.

lifi_get_routes ~163

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.

NameTypeReqDescription
from_addressstringyesSender wallet address (0x...)
from_amountstringyesAmount in smallest unit (wei for ETH, base units for ERC-20)
from_chain_idintegeryesSource chain ID
from_token_addressstringyesSource token address
slippagenumber|null–Slippage tolerance as decimal (default 0.03 = 3%)
to_chain_idintegeryesDestination chain ID
to_token_addressstringyesDestination token address
NameTypeReqDescription
result–yesUnderlying response payload verbatim.

No examples provided.

lifi_get_status ~126

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.

NameTypeReqDescription
bridgestring|null–Bridge name (optional, e.g. 'stargate', 'hop', 'across')
from_chaininteger|null–Source chain ID (optional, helps disambiguate)
to_chaininteger|null–Destination chain ID (optional, helps disambiguate)
tx_hashstringyesTransaction hash to check status for
NameTypeReqDescription
result–yesUnderlying response payload verbatim.

No examples provided.

lifi_get_token ~142

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

NameTypeReqDescription
chain_idintegeryesChain ID (e.g. 1 for Ethereum, 137 for Polygon, 42161 for Arbitrum)
token_addressstringyesToken contract address (e.g. '0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48' for USDC on Ethereum). Use '0x0000000000000000000000000000000000000000' for native tokens.
NameTypeReqDescription
result–yesUnderlying response payload verbatim.

No examples provided.

lifi_get_tokens ~71

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

NameTypeReqDescription
chainsstring|null–Comma-separated chain IDs to filter tokens (e.g. '1,137,42161'). Omit for all chains.
NameTypeReqDescription
result–yesUnderlying response payload verbatim.

No examples provided.

lifi_get_tools ~39

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
result–yesUnderlying response payload verbatim.

No examples provided.

Common questions

What is the xyz.tenzro/tenzro-lifi MCP server?

xyz.tenzro/tenzro-lifi is an MCP server listed in the public MCP registry as xyz.tenzro/tenzro-lifi. Li.Fi tools over MCP: cross-chain quotes, routes, execution status, chains, tokens, balances. This page covers its hosted endpoint (https://lifi-mcp.tenzro.xyz/mcp).

Is the xyz.tenzro/tenzro-lifi MCP server safe to use?

xyz.tenzro/tenzro-lifi scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the xyz.tenzro/tenzro-lifi MCP server expose?

xyz.tenzro/tenzro-lifi exposes 9 tools: lifi_get_chains, lifi_get_connections, lifi_get_gas_prices, lifi_get_quote, lifi_get_routes, and 4 more. Their descriptions and schemas cost roughly 976 tokens of context every time the server is loaded.

Does the xyz.tenzro/tenzro-lifi MCP server require authentication?

Its publisher declares no required credentials for xyz.tenzro/tenzro-lifi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the xyz.tenzro/tenzro-lifi MCP server still maintained?

xyz.tenzro/tenzro-lifi has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 9 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.