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.

LayerHop

REMOTE · MCP.LAYERHOP.COM · 2 COMPONENTS

Best-price cross-chain swap quotes across 70 chains (EVM + Solana). Holds no keys, never signs.

68 Trust /100

Last scanned (21 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 22 Oct 2026.

Category Crypto and Web3

Recent critical change

Authorization (20 Oct 2026). See the changelog before you install this server.

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 Security57
Transport & Reachability100
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 4911 tokens (~56/item across 87 items; 15 tools + 72 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 22 Oct 26 0
    • Resource “Blast tokens” was removed ▼ functional
  • 21 Oct 26 +1

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

  • 20 Oct 26 −7
    • Authorization: partial → fail ▼ critical
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “disable_deposit_address”, which the server declares destructive security
    • Schema quality: 45 → 56 ▼ functional
    • New resource “Hyperliquid tokens” functional
    • Server version: 0.1.0 → 0.7.0 functional
    • New tool “get_deposit_address” functional
    • New tool “list_deposit_addresses” functional
    • New tool “refresh_deposit_address” functional
    • New tool “simulate_deposit” functional
    • New tool “create_deposit_address” functional
  • 19 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 18 Oct 26 73

    First indexed and scored.

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 22 Oct 2026 · Probed https://mcp.layerhop.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.layerhop.com CN=YR2,O=Let's Encrypt,C=US 17 Oct 2026 15 Jan 2027 RSA 4096 SHA256-RSA 687f6a63b1c7680d204aa81470775a7ce69
SANs: mcp.layerhop.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.layerhop.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
layerhop.com. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.layerhop.com/mcp Verified 200
http (plaintext) http://mcp.layerhop.com/mcp HTTPS enforced 302 https://mcp.layerhop.com/mcp
MCP tools · 15 exposed · ~2,892 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
build_transaction ~141

Turn a quoteId from get_quote into the UNSIGNED transaction the user's own wallet must sign: EVM {chainId, to, data, value in wei, optional ERC-20 approval to send first} or Solana {serializedTx base64}. Includes plain-language signing steps. The LayerHop MCP server holds no private keys and never signs or broadcasts transactions. Only use this when the user has their own signer and explicitly wants raw transaction data, after they confirmed the quote; otherwise give them the swap link.

NameTypeReqDescription
quoteIdstringyesquoteId from get_quote (starts with "q_"). Quotes expire after a short time (see expiresAt).

No output schema declared.

No examples provided.

create_deposit_address ~575

Create an address the user sends tokens to; every deposit is swapped/bridged and delivered as toToken on toChain to recipient. No wallet connection or signing needed. Non-custodial: the address belongs to the liquidity provider (Relay), LayerHop never holds funds. Tell the user: send ONLY srcToken on srcChain to the address (other tokens or chains may be lost for good), at least $1 worth; refundTo must be the user's own address on srcChain, never an exchange (CEX) deposit address. Needs a LayerHop API key; test keys (lh_test_) give a fake sandbox address that must never receive real funds. The LayerHop MCP server holds no private keys and never signs or broadcasts transactions.

NameTypeReqDescription
amountstring|number–HUMAN units of fromToken ("25" = 25 USDC). Required when reusable is false (the exact amount to send); otherwise only sizes the estimate. Minimum worth $1.
fromChainstring|numberyesSource (deposit) chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.
fromTokenstringyesThe ONLY token the user may send to the address (source) token: symbol from list_tokens ("USDC", "ETH", "SOL") or the token contract address / SPL mint. Use "native" for the chain's gas coin.
fromTokenDecimalsinteger–Only needed when fromToken is an address that is not in list_tokens: the token's decimals (e.g. 6 for USDC, 18 for most ERC-20s).
labelstring–Your reference for this address (1-64 chars), filterable in list_deposit_addresses.
metadataobject–Up to 20 string key-value pairs stored on the address.
recipientstringyesAddress that receives toToken on toChain.
refundTostringyesThe user's OWN address on fromChain for refunds. NEVER an exchange (CEX) deposit address: refunds never go back to an exchange.
reusableboolean–true (default): reusable for this route with any amount. false: one-time address for exactly `amount`.
toChainstring|numberyesDestination chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.
toTokenstringyesToken to deliver (destination) token: symbol from list_tokens ("USDC", "ETH", "SOL") or the token contract address / SPL mint. Use "native" for the chain's gas coin.

No output schema declared.

No examples provided.

disable_deposit_address ~82

Disable a deposit address: LayerHop stops tracking it (no more orders or webhooks for it). The provider may still process funds sent to it later, so the user must stop using it. Cannot be undone. Confirm with the user first. Needs a LayerHop API key.

NameTypeReqDescription
idstringyesDeposit address id (starts with "da_").

No output schema declared.

No examples provided.

get_deposit_address ~149

Get one deposit address with its 20 most recent deposits (orders, quoteId starting with dep_): amount deposited and delivered, status (submitted, pending, filled, refunded, failed) and tx hashes. Tell the user: send ONLY srcToken on srcChain to the address (other tokens or chains may be lost for good), at least $1 worth; refundTo must be the user's own address on srcChain, never an exchange (CEX) deposit address. Needs a LayerHop API key; test keys (lh_test_) give a fake sandbox address that must never receive real funds. Read-only.

NameTypeReqDescription
idstringyesDeposit address id (starts with "da_").

No output schema declared.

No examples provided.

get_order_status ~102

Check the status of a swap or bridge after the source transaction was sent: pending, filled (funds delivered), refunded, failed, or unknown (some same-chain providers; check the tx on an explorer). Read-only.

NameTypeReqDescription
providerstringyesThe provider of the quote that was executed (the `provider` field from get_quote / build_transaction).
txHashstringyesSource-chain transaction hash (EVM) or signature (Solana).

No output schema declared.

No examples provided.

get_quote ~588

Get the best price to swap or bridge tokens, within one chain or across chains (EVM <-> Solana). Asks every liquidity provider and returns the best quote plus alternatives with human-readable amounts, minimum received after slippage, fees (LayerHop fee, partner fee, provider fee, gas) and ETA. Returns a quoteId (valid until expiresAt) and a layerhop.com swapLink a human can open to review and sign. Read-only: The LayerHop MCP server holds no private keys and never signs or broadcasts transactions. Always show the user the fees and output and get confirmation before proceeding.

NameTypeReqDescription
amountstring|numberyesAmount to send in HUMAN units of fromToken as a decimal string, e.g. "100" for 100 USDC or "0.05" for 0.05 ETH. NOT base units/wei/lamports. Must be greater than 0.
fromChainstring|numberyesSource chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.
fromTokenstringyesToken to send (source) token: symbol from list_tokens ("USDC", "ETH", "SOL") or the token contract address / SPL mint. Use "native" for the chain's gas coin.
fromTokenDecimalsinteger–Only needed when fromToken is an address that is not in list_tokens: the token's decimals (e.g. 6 for USDC, 18 for most ERC-20s).
recipientstring–Address that receives funds on the destination chain. Defaults to sender when both chains use the same VM; REQUIRED for EVM <-> Solana.
senderstringyesWallet address that sends the funds on the source chain (0x... for EVM, base58 for Solana). Only used to build the quote; no access is needed.
slippageBpsinteger–Max slippage in basis points (1 bp = 0.01%). Default 50 (= 0.5%).
toChainstring|numberyesDestination chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.
toTokenstringyesToken to receive (destination) token: symbol from list_tokens ("USDC", "ETH", "SOL") or the token contract address / SPL mint. Use "native" for the chain's gas coin.
toTokenDecimalsinteger–Only needed when toToken is an address that is not in list_tokens: the token's decimals (e.g. 6 for USDC, 18 for most ERC-20s).

No output schema declared.

No examples provided.

get_swap_link ~386

Create a https://layerhop.com/swap link prefilled with the swap, which the user opens to review the live quote and fees and sign in their own wallet. This is the default, safest way to execute a swap. The LayerHop MCP server holds no private keys and never signs or broadcasts transactions. The amount is in human units.

NameTypeReqDescription
amountstring|number–Amount to send in HUMAN units of fromToken as a decimal string, e.g. "100" for 100 USDC or "0.05" for 0.05 ETH. NOT base units/wei/lamports. Must be greater than 0.
fromChainstring|numberyesSource chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.
fromTokenstringyesToken to send (source) token: symbol from list_tokens ("USDC", "ETH", "SOL") or the token contract address / SPL mint. Use "native" for the chain's gas coin.
recipientstring–Optional destination address to prefill (the user can still edit it).
slippageBpsinteger–Max slippage in basis points (1 bp = 0.01%). Default 50 (= 0.5%).
toChainstring|numberyesDestination chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.
toTokenstringyesToken to receive (destination) token: symbol from list_tokens ("USDC", "ETH", "SOL") or the token contract address / SPL mint. Use "native" for the chain's gas coin.

No output schema declared.

No examples provided.

list_chains ~46

List every blockchain LayerHop can swap from or to: slug, numeric chain id, name, VM type (evm or svm = Solana) and native coin. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_deposit_addresses ~108

List the deposit addresses of the API key's account and mode (live or test), newest first: address, route, status, deposit count. Needs a LayerHop API key. Read-only.

NameTypeReqDescription
cursorstring–nextCursor from a previous call, for the next page.
labelstring–Only addresses with this label.
limitinteger–Max addresses to return (default set by the API).
statusstring–Only addresses with this status.

No output schema declared.

No examples provided.

list_orders ~116

List LayerHop orders (swaps built or submitted through LayerHop) where the address is the sender or recipient, newest first, with status. Public data (addresses only). Read-only.

NameTypeReqDescription
addressstringyesWallet address (EVM 0x... or Solana base58).
cursorstring–nextCursor from a previous list_orders call, for the next page.
limitinteger–Max orders to return (default set by the API).
statusstring–Only orders with this status.

No output schema declared.

No examples provided.

list_tokens ~94

List LayerHop's built-in tokens on one chain (symbol, contract address or mint, decimals). Symbols can be used directly in get_quote; other tokens can be quoted by address. Read-only.

NameTypeReqDescription
chainstring|numberyesThe chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.

No output schema declared.

No examples provided.

refresh_deposit_address ~79

Ask LayerHop to check a deposit address for new deposits right away (instead of waiting for the next scheduled check). Call it when the user says they sent funds, then call get_deposit_address after ~15-30 s. Needs a LayerHop API key.

NameTypeReqDescription
idstringyesDeposit address id (starts with "da_").

No output schema declared.

No examples provided.

report_submitted ~127

Tell LayerHop that the user's wallet broadcast the transaction for a quoteId, so the order is tracked (status, webhooks). Call this once after broadcasting, with the EVM tx hash (0x + 64 hex) or Solana signature. Idempotent. Does not sign or send anything.

NameTypeReqDescription
quoteIdstringyesquoteId from get_quote (starts with "q_"). Quotes expire after a short time (see expiresAt).
txHashstringyesSource-chain transaction hash (EVM 0x...) or Solana signature (base58).

No output schema declared.

No examples provided.

simulate_deposit ~175

TEST MODE ONLY (lh_test_ key and a test deposit address): record a fake deposit so the integration can be tested end to end; it becomes a test order that settles with webhooks. The amount decides the outcome: base units ending in 4001 -> refunded, 4002 -> failed, anything else -> filled. Moves no real funds. Fails with a live key.

NameTypeReqDescription
amountstring|number–Deposit amount in HUMAN units of the address token ("25" = 25 USDC). Give this or amountBaseUnits.
amountBaseUnitsstring–Deposit amount in base units (e.g. "25004001" to test a refund for a 6-decimal token). Give this or amount.
idstringyesDeposit address id (starts with "da_").

No output schema declared.

No examples provided.

simulate_transaction ~124

Build the transaction for a quoteId and dry-run it on-chain (EVM eth_call + gas estimate from the sender; Solana simulateTransaction) without sending anything or recording an order. Reports whether it would succeed, gas / compute units, whether an ERC-20 approval is still needed, and the error if it would fail. Read-only: The LayerHop MCP server holds no private keys and never signs or broadcasts transactions.

NameTypeReqDescription
quoteIdstringyesquoteId from get_quote (starts with "q_"). Quotes expire after a short time (see expiresAt).

No output schema declared.

No examples provided.

Install

How do I install the LayerHop MCP server?

LayerHop is a hosted endpoint at https://mcp.layerhop.com/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 · mcp.layerhop.com

# add to Claude Code
claude mcp add --transport http com-layerhop-mcp 'https://mcp.layerhop.com/mcp'
Common questions

What is the LayerHop MCP server?

LayerHop is an MCP server listed in the public MCP registry as com.layerhop/mcp. Best-price cross-chain swap quotes across 70 chains (EVM + Solana). Holds no keys, never signs. This page covers its hosted endpoint (https://mcp.layerhop.com/mcp).

Is the LayerHop MCP server safe to use?

LayerHop scores 68 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 LayerHop MCP server expose?

LayerHop exposes 15 tools: list_chains, list_tokens, get_quote, build_transaction, simulate_transaction, and 10 more. Their descriptions and schemas cost roughly 2,892 tokens of context every time the server is loaded.

Does the LayerHop MCP server require authentication?

No. We connected to LayerHop without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the LayerHop MCP server still maintained?

LayerHop is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.