Skip to main content

Tenzro LayerZero V2 MCP

by network.tenzro

Overview Discussions Admin

Server Details

LayerZero V2 MCP: EndpointV2 quotes, OFT transfers, Stargate V2, Value Transfer API, DVNs.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status: Unhealthy
Uptime: 0.0% over 42 days
Last Tested: 2026-09-28 23:45
Transport: Streamable HTTP
URL
Repository: tenzro/tenzro-network
GitHub Stars: 0

TDQS

A4.3/5.0

Scored 2026-06-13 15:50 across 21 tools

Disambiguation5/5

All tools have distinct purposes: quoting, sending, listing, tracking, etc. There is no overlap; each tool targets a specific operation or data retrieval for LayerZero V2 cross-chain interactions.

Naming Consistency5/5

All tools follow a consistent 'lz_verb_noun' pattern in snake_case, making it easy to infer functionality from the name. Examples include lz_quote_fee, lz_send_message, lz_list_chains.

Tool Count5/5

21 tools is well-scoped for a cross-chain messaging/bridging server. It covers core LayerZero, OFT, Stargate, and Value Transfer API without being overwhelming.

Completeness5/5

The tool set covers the full lifecycle: quoting fees, building calldata, broadcasting transactions, tracking messages, and querying metadata (chains, deployments, tokens). There are no obvious gaps for the intended use case.

Tool Schema Changelog

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

21 tool updatesMay 16, 2026

Changedlz_broadcast_signed_tx1 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"
+}

Changedlz_encode_options1 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"
+}

Changedlz_get_chain_rpc1 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"
+}

Changedlz_get_deployments1 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"
+}

Changedlz_get_message1 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"
+}

Changedlz_get_messages_by_address1 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"
+}

Changedlz_list_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"
+}

Changedlz_list_dvns1 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"
+}

Changedlz_oft_list1 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"
+}

Changedlz_oft_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"
+}

Changedlz_oft_send1 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"
+}

Changedlz_quote_fee1 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"
+}

Changedlz_send_message1 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"
+}

Changedlz_stargate_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"
+}

Changedlz_stargate_send1 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"
+}

Changedlz_track_message1 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"
+}

Changedlz_transfer_build1 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"
+}

Changedlz_transfer_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"
+}

Changedlz_transfer_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"
+}

Changedlz_transfer_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"
+}

Changedlz_transfer_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"
+}

1 tool updateMay 6, 2026
- Addedlz_broadcast_signed_tx
20 tool updatesMay 2, 2026
- First observedlz_encode_options
- First observedlz_get_chain_rpc
- First observedlz_get_deployments
- First observedlz_get_message
- First observedlz_get_messages_by_address
- First observedlz_list_chains
- First observedlz_list_dvns
- First observedlz_oft_list
- First observedlz_oft_quote
- First observedlz_oft_send
- First observedlz_quote_fee
- First observedlz_send_message
- First observedlz_stargate_quote
- First observedlz_stargate_send
- First observedlz_track_message
- First observedlz_transfer_build
- First observedlz_transfer_chains
- First observedlz_transfer_quote
- First observedlz_transfer_status
- First observedlz_transfer_tokens

Related MCP Connectors

tenzro-layerzero A
xyz.tenzro
LayerZero V2 tools over MCP: message quotes, OFT transfers, Stargate bridging, DVN lookups.
Blockchain Web3 & Decentralized Tech
2
tenzro-lifi A
xyz.tenzro
Li.Fi tools over MCP: cross-chain quotes, routes, execution status, chains, tokens, balances.
Blockchain Cryptocurrency
2
Tenzro Li.Fi MCP A
network.tenzro
Li.Fi MCP: cross-chain aggregation — quotes, routes, status, chains, tokens, execution.
Blockchain Cryptocurrency
2
tenzro-chainlink A
xyz.tenzro
Chainlink tools over MCP: CCIP cross-chain, data feeds, data streams, VRF, proof of reserve.
Blockchain Web3 & Decentralized Tech
2

Related MCP Servers

@quackai/q402-mcpofficial
Blockchain Cryptocurrency Finance
quackai-org
A
license
A
quality
C
maintenance
MCP server for gasless USDC, USDT, RLUSD, and USDG payments across 12 EVM chains via EIP-7702, enabling quote, route, and settle stablecoin payments from any MCP client.
Updated 8 days ago (2026-09-21 08:23 UTC)
50
826 npm
Apache 2.0
Stargate Bridge MCP
Blockchain Cryptocurrency Web3 & Decentralized Tech
kukapay
A
license
A
quality
D
maintenance
An MCP server that enables cross-chain token transfers via the Stargate protocol.
Updated a year ago (2025-10-27 12:19 UTC)
4
1
MIT
deBridgeofficial
Blockchain Web3 & Decentralized Tech Cryptocurrency
debridge-finance
A
license
A
quality
D
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
Updated 19 days ago (2026-09-09 22:54 UTC)
5
34 npm
31
MIT
genpark-cross-chain-bridge
Blockchain Web3 & Decentralized Tech
Alpha-Park
F
license
Not graded
quality
B
maintenance
Enables automated auditing of cross-chain bridge token reserves and monitoring for anomalous outflows on LayerZero and Wormhole, integrating with MCP-compliant clients for deterministic Web3 security analysis.
Updated 24 days ago (2026-09-05 01:08 UTC)
8
-

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources