AramidBridgeMCP
Related Servers
Alternatives to AramidBridgeMCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables interaction with the DorkFi lending protocol on Voi and Algorand, supporting market discovery, position queries, liquidation scanning, and transaction preparation without signing or broadcasting.10MIT
- AlicenseAqualityDmaintenanceEnables interaction with the DorkFi lending protocol on Voi and Algorand, supporting market queries, user positions, liquidation scanning, TVL analytics, and transaction preparation.21MIT
- AlicenseBqualityDmaintenanceProvides normalized reads and unsigned transaction payloads for ASA, ARC-200, and ARC-72 assets on Algorand and Voi mainnets via the Model Context Protocol.29MIT
- AlicenseNot gradedqualityDmaintenanceLow-level blockchain interface MCP server for Algorand and Voi networks, providing account/asset/app inspection, transaction search, block retrieval, TEAL compilation, and transaction simulation.MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with the Algorand blockchain through 25+ specialized tools for account management, payments, asset creation, NFT operations, and network monitoring. Supports both mainnet and testnet with instant finality and low fees.8 npm1MIT
- 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
TDQS
Scored across 2 tools
get_supported_assets is a read-only query for available assets and routes; bridge_txn is a transaction builder. Their purposes are clearly distinct with no overlap, so an agent can easily select the right tool.
Both tools use snake_case with a consistent verb_noun pattern: get_supported_assets and bridge_txn. The abbreviation 'txn' is minor and does not break the pattern.
Only 2 tools are provided, which is below the typical 3-15 range. While each tool earns its place for a minimal bridge service, the count feels thin for a production bridging MCP.
The surface covers asset discovery and transaction building but lacks tools for checking bridge status, estimating fees, or retrieving transaction history. These are notable gaps for a bridge lifecycle, though signing is delegated to UluWalletMCP.