Wormhole Mcp

io.github.junct-botPublished by GitHub account junct-botv1.1.0Updated Oct 24, 2026

Wormhole - 69 tools for cross-chain transfers and bridge data

VerifiedStreamable HTTPWeb executableFinanceDeveloper Tools

Overview

AI-generated overview

Hosted MCP server exposing 69 tools for Wormhole cross-chain token bridging and messaging data across 30+ blockchains.

What you can do
  • Query Wormhole bridge and cross-chain messaging data
  • Look up token transfer routes and supported chains
  • Access Wormhole API data for bridging and messaging across 30+ blockchains
When to use it
Useful when an assistant needs Wormhole cross-chain bridge or messaging data, such as checking supported chains or transfer routes, without building its own API integration.
Requirements
A remote MCP endpoint; no local package, account, API key, environment variable or header is declared. Network access to the hosted endpoint is required.
Before you install
The server is hosted by a third party and the README states it is powered by Junct, so requests and queries pass through that operator. No authentication is declared, so do not send secrets or wallet credentials through it. The tools are not listed, so confirm whether any of them initiate or sign transfers before relying on it.

Installation

In SourceWeft

  1. Open Wormhole Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.junct-bot%2Fwormhole-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "wormhole": {
      "type": "http",
      "url": "https://wormhole.mcp.junct.dev/mcp"
    }
  }
}

README

Wormhole MCP Server

Hosted MCP server for Wormhole — giving AI agents direct access to cross-chain bridging and messaging.

Powered by Junct — the agent-readiness layer for DeFi.

Quick Connect

json
{  "mcpServers": {    "wormhole": {      "url": "https://wormhole.mcp.junct.dev/mcp"    }  }}

About

Wormhole is a cross-chain messaging protocol enabling token bridging and data transfer across 30+ blockchains. This MCP server provides 69 tools for AI agents to access Wormhole's API.

Links

Source: README.md at commit 6fb174d

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.