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

NPM · @LAYERHOP/MCP · 2 COMPONENTS

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

74 Trust /100

Last scanned (14 hours ago)

Scores higher than 43% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
  • 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 3646 tokens (~45/item across 81 items; 9 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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.

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

  • 19 Oct 26 +1

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

  • 18 Oct 26 72

    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 · Analysed npm/@layerhop/mcp@0.5.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,724 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.

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

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_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 runs locally as an npm package, launched with npx -y @layerhop/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @layerhop/mcp

# add to Claude Code
claude mcp add com-layerhop-mcp -- npx -y @layerhop/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 npm package (@layerhop/mcp).

Is the LayerHop MCP server safe to use?

LayerHop scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. It declares no install or post-install scripts. 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 9 tools: list_chains, list_tokens, get_quote, build_transaction, simulate_transaction, and 4 more. Their descriptions and schemas cost roughly 1,724 tokens of context every time the server is loaded.

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.

What licence is the LayerHop MCP server under?

LayerHop declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.