Skip to main content
Glama
LaplaceMan

Web3 Assistant MCP

by LaplaceMan

Related Servers

Alternatives to Web3 Assistant MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Ethereum-compatible smart contracts through their ABI, allowing both read operations (querying state) and write operations (executing transactions) dynamically based on the contract's interface.
      5 npm
      3
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables blockchain payment operations across multiple networks including Base, Ethereum, BSC, Polygon, and Avalanche. Supports balance queries, token transfers, transaction tracking, wallet management, and gas fee estimation with built-in security limits.
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI applications to interact with the Base blockchain network, allowing wallet management, smart contract deployment, token transfers, NFT operations, DeFi interactions with Morpho vaults, and onramping funds via Coinbase.
      15 npm
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      -
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI applications to interact with the Base blockchain network and Coinbase API, supporting wallet operations, smart contract deployment, token transfers, NFT management, DeFi lending through Morpho vaults, and onramp functionality.
      15 npm
      -

    TDQS

    B3.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: analyze_contract_abi is for inspecting contract functions, call_contract is for executing functions, and local_wallet_address is for retrieving wallet information. There is no overlap or ambiguity between these tools.

    Naming Consistency4/5

    The tools follow a consistent snake_case naming convention, but the naming pattern is not perfectly uniform: analyze_contract_abi and call_contract use verb_noun format, while local_wallet_address is a noun phrase. This minor deviation keeps it mostly consistent.

    Tool Count3/5

    With only 3 tools, the set feels thin for a 'Web3 Assistant' domain, which typically involves more operations like deploying contracts, checking balances, or interacting with blockchains. While the tools cover some basics, the count is borderline for the apparent scope.

    Completeness2/5

    There are significant gaps in the tool surface for Web3/blockchain interactions. Missing are essential operations such as deploying contracts, reading blockchain data (e.g., balances, transactions), or sending transactions. This incompleteness will likely cause agent failures in common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing