Skip to main content
Glama

Related Servers

Alternatives to AramidBridgeMCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with the DorkFi lending protocol on Voi and Algorand, supporting market discovery, position queries, liquidation scanning, and transaction preparation without signing or broadcasting.
      10
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with the DorkFi lending protocol on Voi and Algorand, supporting market queries, user positions, liquidation scanning, TVL analytics, and transaction preparation.
      21
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Low-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
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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

    A3.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues