Stargate Bridge MCP
Related Servers
Alternatives to Stargate Bridge MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceHosted MCP server that exposes Stargate's API to AI agents via a deterministic, 1:1 tool mapping, enabling crypto/DeFi interactions without authentication.-

orbit-apiofficial
FlicenseNot gradedqualityFmaintenanceMCP server for cross-chain bridging, enabling AI agents to find routes, estimate costs, check risks, execute transfers, and track status across blockchains.-- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables cross-chain token swapping between different blockchains using 1inch Fusion+ API, along with portfolio management tools for tracking assets across chains.1-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that delivers real-time cross-chain bridge rates and optimal transfer routes to onchain AI agents.7 npm5MIT
- AlicenseAqualityDmaintenanceAn MCP server that tracks stablecoin peg integrity across multiple blockchains.44MIT

Armor Crypto MCPofficial
AlicenseCqualityDmaintenanceAn MCP server providing unified access to blockchain operations, bridging, swapping, and crypto trading strategies for AI agents.37178GPL 3.0
TDQS
Scored across 4 tools
Each tool has a distinct role in the bridging workflow: listing chains, listing bridgeable tokens for a source, fetching quotes, and executing transfers. There is no overlap; even though bridge_transfer internally fetches a quote, its purpose is execution, distinct from get_quotes which only retrieves options.
All tool names follow a consistent verb_noun pattern in snake_case: list_* for discovering chains and tokens, get_quotes for fetching quotes, and bridge_transfer for execution. This makes the API predictable and easy to navigate.
With exactly 4 tools, the server is well-scoped for its purpose. It provides the necessary discovery, quoting, and execution capabilities without unnecessary bloat, fitting comfortably within the ideal 3-15 tool range.
The tool set covers the full cross-chain bridging lifecycle: discover supported chains, identify bridgeable token destinations, obtain quotes with slippage parameters, and execute the transfer. No critical operations are missing for the stated purpose, and the workflow is complete without dead ends.