Wormhole Metrics MCP Server

Wormhole Metrics MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. An MCP server that analyzes cross-chain activity on the Wormhole protocol, providing insights into transaction volumes, top assets, source-destination chain pairs, and key performance indicators (KPIs).

What you get

• Comprehensive Tools — Includes tools for cross-chain activity, money flow, top assets, chain pairs, symbols, token corridors, and KPIs
• Markdown Output — Returns data as Markdown-formatted tables for clear presentation

What the assistant can call

Once Wormhole Metrics MCP is connected, these are the calls the assistant has available:

• Description — Fetches cross-chain activity data, returning a pivot table of volumes between source and destination chains
• Parameters — - timeSpan: 7d, 30d, 90d, 1y, all-time (default: 7d)
• app — Comma-separated list of apps (default: empty)
• Example — - Prompt: "Show me the cross-chain activity for the last 7 days, measured by notional volume."
• Output — markdown
• from_date — ISO 8601 format (e.g., 2024-01-01T15:04:05Z, default: empty)
• to_date — ISO 8601 format (default: empty)
• appId — Application ID (default: empty)
• sourceChain — Source chain ID (default: empty)
• targetChain — Target chain ID (default: empty)
• Prerequisites — The Prerequisites tool exposed by this server
• Setup — Install the server as a Claude Desktop application: bash uv run mcp install main.py --name "Wormhole Metrics"

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

• Python 3.10 or higher - uv (recommended package manager)

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Wormhole Metrics MCP's toolset — Description, Parameters, app and 10 more — is a fair guide to whether it matches your workflow. It is maintained by kukapay; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Wormhole Metrics MCP.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the wormhole metrics mcp mcp server does with a few real requests.