Galactic Bridge MCP
Related Servers
Alternatives to Galactic Bridge MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI agents to perform gasless cross-chain transactions by paying with supported tokens on one chain and executing on another, all without exposing private keys.194 npm1Apache 2.0
- AlicenseCqualityCmaintenanceEnables AI agents to interact with any EVM-compatible blockchain through natural language, supporting token swaps, cross-chain bridges, staking, lending, governance, gas optimization, and portfolio tracking across networks like Ethereum, BSC, Polygon, Arbitrum, and more.10030 npm41-

Bink MCP Serverofficial
FlicenseNot gradedqualityDmaintenanceEnables AI agents to perform blockchain operations like wallet management, token info, DeFi swaps, cross-chain bridging, and price checking across Ethereum, BNB Chain, and Solana.-- AlicenseNot gradedqualityDmaintenanceEnables AI agents to perform cross-chain bridging operations using natural language intents, with support for multiple protocols (Across, Stargate) and advanced security features like oracle validation and slippage protection. Provides comprehensive bridging tools including quote estimation, transaction building, and approval management across Arbitrum and Ethereum networks.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform complex crypto operations like cross-chain routing, contract decoding, portfolio management, and anti-rug security checks, returning unsigned transactions for safe signing by the agent.MIT
- AlicenseAqualityDmaintenanceProvides cross-chain bridge and swap tools for AI agents using the Relay Protocol to interact with multiple blockchain networks. It enables agents to query supported chains, obtain transaction quotes, and generate unsigned transaction data for token transfers and swaps.1038 npm4MIT
TDQS
Scored across 3 tools
Each tool addresses a distinct step in the bridge workflow: listing supported chains, discovering token deployments, and resolving a specific route. There is no meaningful overlap between the three tools.
All tool names follow a consistent snake_case verb_noun pattern: list_supported_networks, scan_token_networks, find_bridge_route. The naming style and verb usage are uniform across the set.
Three tools is a well-scoped and appropriate size for this server's purpose. Each tool covers a necessary leg of the bridge-route discovery process without redundancy.
The tool set fully covers the intended discovery workflow: knowing supported networks, locating a token on those networks, and resolving an executable bridge route. The explicit decision not to sign/send transactions is a stated boundary, not a gap.