xyz.tenzro/tenzro-layerzero
REMOTE · LAYERZERO-MCP.TENZRO.XYZ · SCANNED AUG 17
LayerZero V2 tools over MCP: message quotes, OFT transfers, Stargate bridging, DVN lookups.
Available components
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.
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
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
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.
How do I install the xyz.tenzro/tenzro-layerzero MCP server?
xyz.tenzro/tenzro-layerzero is a hosted endpoint at https://layerzero-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 · layerzero-mcp.tenzro.xyz
claude mcp add --transport http xyz-tenzro-tenzro-layerzero 'https://layerzero-mcp.tenzro.xyz/mcp'
{
"mcpServers": {
"xyz-tenzro-tenzro-layerzero": {
"url": "https://layerzero-mcp.tenzro.xyz/mcp"
}
}
} {
"servers": {
"xyz-tenzro-tenzro-layerzero": {
"type": "http",
"url": "https://layerzero-mcp.tenzro.xyz/mcp"
}
}
} [mcp_servers.xyz-tenzro-tenzro-layerzero] url = "https://layerzero-mcp.tenzro.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-tenzro-tenzro-layerzero": {
"type": "remote",
"url": "https://layerzero-mcp.tenzro.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-tenzro-tenzro-layerzero --url 'https://layerzero-mcp.tenzro.xyz/mcp' --transport streamable-http
mcp_servers:
xyz-tenzro-tenzro-layerzero:
url: "https://layerzero-mcp.tenzro.xyz/mcp" {
"McpServers": {
"xyz-tenzro-tenzro-layerzero": {
"Transport": "http",
"Url": "https://layerzero-mcp.tenzro.xyz/mcp"
}
}
} assistant mcp add xyz-tenzro-tenzro-layerzero -t streamable-http -u 'https://layerzero-mcp.tenzro.xyz/mcp'
{
"mcpServers": {
"xyz-tenzro-tenzro-layerzero": {
"type": "http",
"url": "https://layerzero-mcp.tenzro.xyz/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 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.
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 17 Aug 2026 · Probed https://layerzero-mcp.tenzro.xyz/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of layerzero-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://layerzero-mcp.tenzro.xyz/mcp | Unreachable | ||
| http (plaintext) | http://layerzero-mcp.tenzro.xyz/mcp | Inconclusive | 404 |
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 →
lz_broadcast_signed_tx ~236
Broadcast a pre-signed Ethereum transaction via eth_sendRawTransaction on the source chain RPC. Use this as the canonical broadcast path for calldata produced by lz_send_message (EndpointV2.send), lz_oft_send (OFT.send), lz_stargate_send (StargatePoolNative.sendToken), and lz_transfer_build (Value Transfer API steps). Returns the transaction hash on success. The caller must construct calldata, sign locally with msg.value = nativeFee from the corresponding quote tool, then submit the RLP-encoded signed tx hex here.
| Name | Type | Req | Description |
|---|---|---|---|
| signed_tx_hex | string | yes | Pre-signed Ethereum transaction in hex format (the 0x-prefixed RLP-encoded signed transaction). Construct calldata via lz_send_message / lz_oft_send / lz_stargate_send / lz_transfer_build, sign local… |
| src_chain | string | yes | Source chain name (e.g. 'ethereum', 'arbitrum', 'base', 'optimism', 'polygon', 'avalanche', 'bsc') |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_encode_options ~141
Encode LayerZero TYPE_3 options bytes for use with EndpointV2.quote() and EndpointV2.send(). TYPE_3 (version tag 0x0003) is the current standard options format for LayerZero V2. Builds binary options with executor worker ID 0x01 and option type 1 (lzReceive) with configurable gas limit and native token drop amount. Returns the hex-encoded options bytes.
| Name | Type | Req | Description |
|---|---|---|---|
| gas_limit | integer|null | – | Gas limit for lzReceive execution on destination (default: 200000) |
| native_drop | integer|null | – | Native token amount to drop on destination in wei (default: 0) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_get_chain_rpc ~69
Get the public RPC URL for a supported chain by name. These RPC URLs are used by the server for eth_call queries against EndpointV2.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_name | string | yes | Chain name to get RPC URL for (e.g. 'ethereum', 'arbitrum', 'base') |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_get_deployments ~48
Get LayerZero V2 deployment addresses across all supported chains. Returns EndpointV2, SendLib, ReceiveLib, DVN, and Executor addresses from the LayerZero Metadata API.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_get_message ~67
Get a LayerZero message by its GUID (Global Unique Identifier). The GUID is returned by EndpointV2.send() and can also be found in the Scan API message tracking response.
| Name | Type | Req | Description |
|---|---|---|---|
| guid | string | yes | LayerZero message GUID (hex, with or without 0x prefix) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_get_messages_by_address ~95
Get LayerZero messages for a specific wallet address. Queries the Scan API for all messages sent or received by the given address. Returns message details including status, source/destination chains, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address to get LayerZero messages for (hex, with or without 0x prefix) |
| limit | integer|null | – | Maximum number of messages to return (default: 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_list_chains ~95
List all 16 chains supported by this LayerZero MCP server with their Endpoint IDs (EIDs). Includes Ethereum, Arbitrum, Optimism, Polygon, BSC, Avalanche, Base, Solana, zkSync, Sei, Sonic, Berachain, Story, Monad, MegaETH, and Tron. EIDs are used in EndpointV2.quote() and EndpointV2.send() to identify destination chains.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_list_dvns ~65
List all Decentralized Verifier Networks (DVNs) registered in the LayerZero V2 protocol. DVNs verify cross-chain messages by attesting to source chain state on the destination chain. Returns DVN names, addresses, supported chains, and configuration details.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_oft_list ~47
List all available OFT (Omnichain Fungible Token) deployments registered in the LayerZero Metadata API. Returns token symbols, contract addresses, supported chains, and deployment details.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_oft_quote ~130
Quote an OFT (Omnichain Fungible Token) transfer via the LayerZero Metadata API. Returns estimated fees, exchange rates, and transfer details for bridging tokens between chains using LayerZero's OFT standard.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to transfer (in base units as string) |
| dst_chain | string | yes | Destination chain name (e.g. 'arbitrum') |
| src_chain | string | yes | Source chain name (e.g. 'ethereum') |
| token_symbol | string | yes | Token symbol (e.g. 'USDC', 'USDT', 'ETH') |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_oft_send ~294
Build transaction calldata for an OFT (Omnichain Fungible Token) send() call on any OFT contract. OFT V2 uses uint64 amountSD (shared decimals) instead of uint256 amountLD. Returns the hex-encoded calldata for OFT.send(SendParam, MessagingFee, refundAddress). The caller must first call lz_quote_fee or lz_oft_quote to get the messaging fee, then sign and broadcast this transaction with msg.value = nativeFee.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to send in shared decimals (amountSD, uint64 — OFT V2 uses shared decimals, not local decimals) |
| dst_chain | string | yes | Destination chain name (e.g. 'arbitrum', 'base', 'solana') |
| gas_limit | integer|null | – | Gas limit for lzReceive on destination (default: 200000) |
| min_amount | string|null | – | Minimum amount to receive in shared decimals (minAmountSD, uint64 — default: 90% of amount) |
| oft_address | string | yes | OFT contract address on the source chain (hex, 20 bytes) |
| recipient | string | yes | Recipient address (hex, 20 bytes for EVM — will be left-padded to bytes32) |
| src_chain | string | yes | Source chain name (e.g. 'ethereum', 'arbitrum', 'base') |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_quote_fee ~220
Estimate cross-chain messaging fee via LayerZero EndpointV2.quote() eth_call. Returns the native fee and LZ token fee required to send a message from the source chain to the destination endpoint. Uses the on-chain EndpointV2 contract at 0x1a44076050125825900e736c501f859c50fE728c. Selector: 0xdb9d28c6.
| Name | Type | Req | Description |
|---|---|---|---|
| dst_eid | integer | yes | Destination chain LayerZero Endpoint ID (e.g. 30110 for Arbitrum) |
| message_hex | string | yes | Hex-encoded message payload (with or without 0x prefix) |
| options_hex | string|null | – | Hex-encoded LayerZero V3 options bytes (default: lzReceive with 200000 gas if omitted) |
| sender_hex | string | yes | Hex-encoded sender address (20 bytes, with or without 0x prefix) |
| src_chain | string | yes | Source chain name (e.g. 'ethereum', 'arbitrum', 'base') |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_send_message ~195
Build transaction calldata for EndpointV2.send() to dispatch a cross-chain message via LayerZero V2. Returns the hex-encoded calldata that should be submitted as a transaction to the EndpointV2 contract on the source chain. The caller must sign and broadcast the transaction with msg.value set to the nativeFee from lz_quote_fee. Selector: 0x5e280f11.
| Name | Type | Req | Description |
|---|---|---|---|
| dst_eid | integer | yes | Destination chain LayerZero Endpoint ID |
| message_hex | string | yes | Hex-encoded message payload |
| options_hex | string|null | – | Hex-encoded LayerZero V3 options bytes (default: lzReceive with 200000 gas if omitted) |
| receiver | string | yes | Hex-encoded receiver address as bytes32 (left-padded to 32 bytes) |
| src_chain | string | yes | Source chain name (e.g. 'ethereum', 'arbitrum', 'base') |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_stargate_quote ~222
Quote a Stargate V2 native bridge transfer fee. Calls quoteSend() on the StargatePoolNative contract (ETH, USDC, or USDT) to get the exact LayerZero messaging fee for bridging between supported EVM chains. Returns the fee in wei and the minimum amount received after slippage. Supported tokens: ETH (Ethereum/Optimism/Arbitrum/Base), USDC (6 chains), USDT (6 chains).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to bridge in base units (wei for ETH, micro-units for USDC/USDT) |
| dst_chain | string | yes | Destination chain name (e.g. 'base', 'ethereum', 'arbitrum') |
| src_chain | string | yes | Source chain name (e.g. 'optimism', 'ethereum', 'base', 'arbitrum') |
| token | string | yes | Token symbol: 'ETH', 'USDC', or 'USDT' |
| wallet_address | string | yes | Sender/recipient wallet address (hex, 20 bytes) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_stargate_send ~260
Build transaction calldata for a Stargate V2 sendToken() bridge transfer. Returns hex-encoded calldata, the target contract address, and the msg.value to include. The caller must sign and broadcast the transaction. For native ETH, msg.value = nativeFee + bridgeAmount. For ERC-20 tokens (USDC/USDT), approve the pool contract first, then msg.value = nativeFee only. Supported: ETH (4 chains), USDC (6 chains), USDT (6 chains).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to bridge in base units (wei for ETH, micro-units for USDC/USDT) |
| dst_chain | string | yes | Destination chain name (e.g. 'base', 'ethereum', 'arbitrum') |
| slippage_bps | integer|null | – | Slippage tolerance in basis points (default: 50 = 0.5%) |
| src_chain | string | yes | Source chain name (e.g. 'optimism', 'ethereum', 'base', 'arbitrum') |
| token | string | yes | Token symbol: 'ETH', 'USDC', or 'USDT' |
| wallet_address | string | yes | Sender/recipient wallet address (hex, 20 bytes) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_track_message ~92
Track a cross-chain LayerZero message by the source transaction hash. Queries the LayerZero Scan API for message status: INFLIGHT, CONFIRMING, DELIVERED, FAILED, or BLOCKED. Returns the full message details including source/destination chains, GUID, and current status.
| Name | Type | Req | Description |
|---|---|---|---|
| tx_hash | string | yes | Transaction hash to track LayerZero message for (with or without 0x prefix) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_transfer_build ~75
Build signable transaction steps from a Value Transfer API quote. Takes a quoteId from lz_transfer_quote and returns pre-built transaction calldata (to, data, value) that the caller can sign and broadcast. Handles approval and bridge steps automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| quote_id | string | yes | Quote ID returned from lz_transfer_quote |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_transfer_chains ~55
List all chains supported by the LayerZero Value Transfer API. Returns 130+ chains including Solana, all EVM L1s and L2s, and their chain keys for use in lz_transfer_quote.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_transfer_quote ~285
Get a cross-chain transfer quote from the LayerZero Value Transfer API. This is the newest LayerZero API (replaces deprecated Stargate REST API) supporting 130+ chains including Solana. Returns quotes with fees, estimated times, and a quote ID for building transaction steps. Use 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE as the token address for native ETH.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to transfer in base units (wei for ETH, smallest unit for tokens) |
| dst_address | string | yes | Recipient wallet address on the destination chain |
| dst_chain | string | yes | Destination chain key (e.g. 'base', 'solana', 'ethereum') |
| dst_token | string | yes | Destination token address (use 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE for native ETH) |
| src_address | string | yes | Sender wallet address on the source chain |
| src_chain | string | yes | Source chain key (e.g. 'optimism', 'ethereum', 'base', 'solana') |
| src_token | string | yes | Source token address (use 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE for native ETH, or contract address for ERC-20) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_transfer_status ~56
Check the status of a Value Transfer API transfer by its quote ID. Returns current transfer status, source/destination transaction hashes, and delivery progress.
| Name | Type | Req | Description |
|---|---|---|---|
| quote_id | string | yes | Quote ID or transfer ID to check status for |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
lz_transfer_tokens ~72
List tokens available for cross-chain transfer via the LayerZero Value Transfer API. Optionally filter by chain. Returns token addresses, symbols, decimals, and which chains they're available on.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string|null | – | Filter tokens by chain key (optional, e.g. 'optimism', 'solana') |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
What is the xyz.tenzro/tenzro-layerzero MCP server?
xyz.tenzro/tenzro-layerzero is an MCP server listed in the public MCP registry as xyz.tenzro/tenzro-layerzero. LayerZero V2 tools over MCP: message quotes, OFT transfers, Stargate bridging, DVN lookups. This page covers its hosted endpoint (https://layerzero-mcp.tenzro.xyz/mcp).
Is the xyz.tenzro/tenzro-layerzero MCP server safe to use?
xyz.tenzro/tenzro-layerzero 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-layerzero MCP server expose?
xyz.tenzro/tenzro-layerzero exposes 21 tools: lz_broadcast_signed_tx, lz_encode_options, lz_get_chain_rpc, lz_get_deployments, lz_get_message, and 16 more. Their descriptions and schemas cost roughly 2,819 tokens of context every time the server is loaded.
Does the xyz.tenzro/tenzro-layerzero MCP server require authentication?
Its publisher declares no required credentials for xyz.tenzro/tenzro-layerzero. 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-layerzero MCP server still maintained?
xyz.tenzro/tenzro-layerzero 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.