xyz.tenzro/tenzro-lifi

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

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

Available components

+3 this week 66 66 Trust /100

Trust breakdown (6 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 →

Endpoint Security57

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
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. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability72

AI-judged instruction clarity (good).Pass
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. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · lifi-mcp.tenzro.xyz

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http xyz-tenzro-tenzro-lifi 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"

// 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.

2 Aug 26 +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.
31 Jul 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
30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
28 Jul 26 +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.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 62

First indexed and scored.

Show 5 earlier entries Hide earlier entries

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 3 Aug 2026 · Probed https://lifi-mcp.tenzro.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=lifi-mcp.tenzro.xyz	CN=YE1,O=Let's Encrypt,C=US	18 Jul 2026	16 Oct 2026	ECDSA 256	ECDSA-SHA384	506439f1c36669b89c08e732d153a64dab3
SANs: lifi-mcp.tenzro.xyz
CN=YE1,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://lifi-mcp.tenzro.xyz/mcp	Verified	200
http (plaintext)	http://lifi-mcp.tenzro.xyz/mcp	HTTPS enforced	308	https://lifi-mcp.tenzro.xyz/mcp

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.

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 Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
result	—	yes	Underlying 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.

Input Output Examples

Name	Type	Req	Description
from_chain	integer	yes	Source chain ID (e.g. 1 for Ethereum)
from_token	string\|null	—	Source token address (optional, filters connections to specific token)
to_chain	integer	yes	Destination chain ID (e.g. 137 for Polygon)
to_token	string\|null	—	Destination token address (optional, filters connections to specific token)

Name	Type	Req	Description
result	—	yes	Underlying 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.

Input Output Examples

Name	Type	Req	Description
chains	string\|null	—	Comma-separated chain IDs (e.g. '1,137,42161'). Omit for all chains.

Name	Type	Req	Description
result	—	yes	Underlying 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.

Input Output Examples

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

Name	Type	Req	Description
result	—	yes	Underlying 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.

Input Output Examples

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

Name	Type	Req	Description
result	—	yes	Underlying 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.

Input Output Examples

Name	Type	Req	Description
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	yes	Transaction hash to check status for

Name	Type	Req	Description
result	—	yes	Underlying 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.

Input Output Examples

Name	Type	Req	Description
chain_id	integer	yes	Chain ID (e.g. 1 for Ethereum, 137 for Polygon, 42161 for Arbitrum)
token_address	string	yes	Token contract address (e.g. '0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48' for USDC on Ethereum). Use '0x0000000000000000000000000000000000000000' for native tokens.

Name	Type	Req	Description
result	—	yes	Underlying 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.

Input Output Examples

Name	Type	Req	Description
chains	string\|null	—	Comma-separated chain IDs to filter tokens (e.g. '1,137,42161'). Omit for all chains.

Name	Type	Req	Description
result	—	yes	Underlying 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 Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
result	—	yes	Underlying response payload verbatim.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	62
27 Jul	63
28 Jul	64
29 Jul	64
30 Jul	65
31 Jul	65
1 Aug	65
2 Aug	66
3 Aug	66