# LayerHop (remote · mcp.layerhop.com)

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

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

> **Recent critical change**: Authorization (2026-10-20). See the changelog below before you install this server.

## Components

- remote · `mcp.layerhop.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-layerhop-mcp/mcp.md), [page](https://verifymcp.io/servers/com-layerhop-mcp/mcp)
- npm · `@layerhop/mcp`: 74/100, [markdown](https://verifymcp.io/servers/com-layerhop-mcp/layerhop-mcp.md), [page](https://verifymcp.io/servers/com-layerhop-mcp/layerhop-mcp)

## Channel facts

- Endpoint: `https://mcp.layerhop.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (disable_deposit_address).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 4911 tokens (~56/item across 87 items; 15 tools + 72 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http com-layerhop-mcp 'https://mcp.layerhop.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-layerhop-mcp": {
      "url": "https://mcp.layerhop.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-layerhop-mcp": {
      "type": "http",
      "url": "https://mcp.layerhop.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-layerhop-mcp]
url = "https://mcp.layerhop.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-layerhop-mcp": {
      "type": "remote",
      "url": "https://mcp.layerhop.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-layerhop-mcp --url 'https://mcp.layerhop.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-layerhop-mcp:
    url: "https://mcp.layerhop.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-layerhop-mcp": {
      "Transport": "http",
      "Url": "https://mcp.layerhop.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-layerhop-mcp -t streamable-http -u 'https://mcp.layerhop.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-layerhop-mcp": {
      "type": "http",
      "url": "https://mcp.layerhop.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 68, 0)

- [functional regression] Resource “Blast tokens” was removed

### 2026-10-21 (score 68, +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.

### 2026-10-20 (score 67, −7)

- [critical regression] Authorization: partial → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “disable_deposit_address”, which the server declares destructive
- [functional regression] 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”

### 2026-10-19 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-18 (score 73)

First indexed and scored.

## MCP tools (15)

### `list_chains` (~46 tokens)

List supported chains

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.

### `list_tokens` (~94 tokens)

List tokens on a chain

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.

Input parameters:

- `chain` (string|number, required): The chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.

### `get_quote` (~588 tokens)

Get swap/bridge quotes

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.

Input parameters:

- `amount` (string|number, required): 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.
- `fromChain` (string|number, required): Source chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.
- `fromToken` (string, required): Token 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.
- `fromTokenDecimals` (integer): 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).
- `recipient` (string): Address that receives funds on the destination chain. Defaults to sender when both chains use the same VM; REQUIRED for EVM <-> Solana.
- `sender` (string, required): Wallet 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.
- `slippageBps` (integer): Max slippage in basis points (1 bp = 0.01%). Default 50 (= 0.5%).
- `toChain` (string|number, required): Destination chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.
- `toToken` (string, required): Token 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.
- `toTokenDecimals` (integer): 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).

### `build_transaction` (~141 tokens)

Build the unsigned transaction for a quote

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.

Input parameters:

- `quoteId` (string, required): quoteId from get_quote (starts with "q_"). Quotes expire after a short time (see expiresAt).

### `simulate_transaction` (~124 tokens)

Dry-run a quote's transaction

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.

Input parameters:

- `quoteId` (string, required): quoteId from get_quote (starts with "q_"). Quotes expire after a short time (see expiresAt).

### `report_submitted` (~127 tokens)

Report a broadcast transaction

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.

Input parameters:

- `quoteId` (string, required): quoteId from get_quote (starts with "q_"). Quotes expire after a short time (see expiresAt).
- `txHash` (string, required): Source-chain transaction hash (EVM 0x...) or Solana signature (base58).

### `get_order_status` (~102 tokens)

Get swap/bridge order status

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.

Input parameters:

- `provider` (string, required): The provider of the quote that was executed (the `provider` field from get_quote / build_transaction).
- `txHash` (string, required): Source-chain transaction hash (EVM) or signature (Solana).

### `list_orders` (~116 tokens)

List orders for a wallet

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.

Input parameters:

- `address` (string, required): Wallet address (EVM 0x... or Solana base58).
- `cursor` (string): nextCursor from a previous list_orders call, for the next page.
- `limit` (integer): Max orders to return (default set by the API).
- `status` (string): Only orders with this status.

### `get_swap_link` (~386 tokens)

Get a layerhop.com swap link

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.

Input parameters:

- `amount` (string|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.
- `fromChain` (string|number, required): Source chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.
- `fromToken` (string, required): Token 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.
- `recipient` (string): Optional destination address to prefill (the user can still edit it).
- `slippageBps` (integer): Max slippage in basis points (1 bp = 0.01%). Default 50 (= 0.5%).
- `toChain` (string|number, required): Destination chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.
- `toToken` (string, required): Token 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.

### `create_deposit_address` (~575 tokens)

Create a deposit address

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.

Input parameters:

- `amount` (string|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.
- `fromChain` (string|number, required): Source (deposit) chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.
- `fromToken` (string, required): The 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.
- `fromTokenDecimals` (integer): 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).
- `label` (string): Your reference for this address (1-64 chars), filterable in list_deposit_addresses.
- `metadata` (object): Up to 20 string key-value pairs stored on the address.
- `recipient` (string, required): Address that receives toToken on toChain.
- `refundTo` (string, required): The user's OWN address on fromChain for refunds. NEVER an exchange (CEX) deposit address: refunds never go back to an exchange.
- `reusable` (boolean): true (default): reusable for this route with any amount. false: one-time address for exactly `amount`.
- `toChain` (string|number, required): Destination chain: slug ("base", "solana", "ethereum", "arbitrum"...) or numeric chain id (Solana is 7565164). See list_chains.
- `toToken` (string, required): Token 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.

### `list_deposit_addresses` (~108 tokens)

List deposit addresses

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.

Input parameters:

- `cursor` (string): nextCursor from a previous call, for the next page.
- `label` (string): Only addresses with this label.
- `limit` (integer): Max addresses to return (default set by the API).
- `status` (string): Only addresses with this status.

### `get_deposit_address` (~149 tokens)

Get a deposit address and its deposits

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.

Input parameters:

- `id` (string, required): Deposit address id (starts with "da_").

### `refresh_deposit_address` (~79 tokens)

Check a deposit address for deposits now

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.

Input parameters:

- `id` (string, required): Deposit address id (starts with "da_").

### `disable_deposit_address` (~82 tokens)

Disable a deposit address

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.

Input parameters:

- `id` (string, required): Deposit address id (starts with "da_").

### `simulate_deposit` (~175 tokens)

Simulate a deposit (test mode only)

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.

Input parameters:

- `amount` (string|number): Deposit amount in HUMAN units of the address token ("25" = 25 USDC). Give this or amountBaseUnits.
- `amountBaseUnits` (string): Deposit amount in base units (e.g. "25004001" to test a refund for a 6-decimal token). Give this or amount.
- `id` (string, required): Deposit address id (starts with "da_").

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-layerhop-mcp/mcp#diagnostics

## Score history

- 2026-10-22: 68
- 2026-10-21: 68
- 2026-10-20: 67
- 2026-10-19: 74
- 2026-10-18: 73

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

## Links

- Remote endpoint: https://mcp.layerhop.com/mcp
- Repository: https://github.com/layerhop/layerhop-js
- Website: https://docs.layerhop.com/guides/ai-agents
- Changelog RSS feed: https://verifymcp.io/servers/com-layerhop-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-layerhop-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-layerhop-mcp/mcp