wormhole-mcp
Server Details
Wormhole - 69 tools for cross-chain transfers and bridge data
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- junct-bot/wormhole-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 2.7/5 across 73 of 73 tools scored. Lowest: 2/5.
Many tools have overlapping purposes, causing significant ambiguity. For example, multiple tools like 'find_vaa_by_id', 'find_duplicated_vaa_by_id', and 'get_transaction_by_id' all seem to retrieve VAA-related data with unclear distinctions. Similarly, governor-related tools (e.g., 'governor_notional_available_by_chain', 'governor_max_notional_available_by_chain') have overlapping scopes, making it hard for an agent to choose the right one without deep domain knowledge.
The naming is mixed but somewhat readable. There are consistent patterns within groups (e.g., 'find_' prefix for VAA/observation queries, 'governor_' prefix for governor data), but overall conventions vary: some use snake_case (e.g., 'api_v1_native_token_transfer_activity'), others use simpler forms (e.g., 'circulating_supply'), and there's no uniform verb-noun structure. This inconsistency can confuse agents but doesn't render the set unreadable.
With 73 tools, the count is excessive for a single server, indicating poor scoping. While Wormhole is a complex blockchain protocol, the tool surface feels bloated with many overlapping or highly specialized functions (e.g., multiple governor notional tools). A more curated set of 15-30 tools would likely suffice, making this overly heavy and difficult for agents to navigate efficiently.
The tool set appears highly complete for the Wormhole domain, covering VAAs, transactions, governor data, token transfers, and protocol analytics. There are discovery tools, CRUD-like operations for queries, and monitoring functions. Minor gaps might exist in mutation operations (e.g., creating or updating data), but given the exploratory/read-only nature implied, coverage is thorough for data retrieval and analysis.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!