Skip to main content
Glama

Tenzro Li.Fi MCP

by network.tenzro
OverviewDiscussionsAdmin

Server Details

Li.Fi MCP: cross-chain aggregation — quotes, routes, status, chains, tokens, execution.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
tenzro/tenzro-network
GitHub Stars
0

TDQS

A4.1/5.0

Scored across 9 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: getting chains, connections, gas prices, quotes, routes, status, specific token, all tokens, and supported tools. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a uniform 'lifi_get_<noun>' pattern, using snake_case consistently. This makes tool selection predictable and easy to navigate.

Tool Count5/5

With 9 tools, the server covers the essential needs for querying cross-chain swap data without being bloated. The count is proportional to the complexity of the domain.

Completeness5/5

The tool set covers all necessary operations for retrieving cross-chain swap information: chain discovery, token details, route options, quotes, status, and protocol metadata. The only missing piece is execution, which is often handled separately.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 9 tool updates
    • Changedlifi_get_chains1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedlifi_get_connections1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedlifi_get_gas_prices1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedlifi_get_quote1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedlifi_get_routes1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedlifi_get_status1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedlifi_get_token1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedlifi_get_tokens1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedlifi_get_tools1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
  2. 9 tool updates
    • First observedlifi_get_chains
    • First observedlifi_get_connections
    • First observedlifi_get_gas_prices
    • First observedlifi_get_quote
    • First observedlifi_get_routes
    • First observedlifi_get_status
    • First observedlifi_get_token
    • First observedlifi_get_tokens
    • First observedlifi_get_tools

Related MCP Connectors

Related MCP Servers

  • LI.FI MCP Server

    demomagic
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to interact with LI.FI's cross-chain infrastructure, providing access to blockchain networks, token data, bridges, and transaction services through a standardized protocol.
    -
  • deBridge by debridge-finance

    deBridgeofficial

    debridge-finance
    A
    license
    A
    quality
    C
    maintenance
    deBridge MCP finds optimal cross-chain swap routes, check fees and conditions, and initiate non-custodial trades across major blockchain networks. Supported: Ethereum, Solana, Arbitrum, Base, BNB Chain, Polygon, Optimism, Avalanche, Linea, Berachain, Tron, Cronos, Gnosis, Monad, Sonic, Flow, HyperEVM, Sei, Story, Injective, Abstract, MegaETH, Mantle, Plasma, Zilliqa, Sophon, Bob, Neon, and more
    5
    54
    32
    MIT
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources