Skip to main content
Glama
tatumio

Tatum MCP Server

Official
by tatumio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Tatum MCP Server

No user-submitted related servers found.

    Related Servers

    • singularity

      DarkStarMatters
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying blockchains across EVM, Solana, Bitcoin/UTXO, and Cosmos through a unified interface, with tools for resolving addresses, checking balances, fetching transactions and blocks, reading contracts, decoding calldata, and building unsigned transfers.
      329 npm
      2
      MIT

    • Web3 MCP

      adroamccullinp
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to interact with multiple blockchains including Solana, Ethereum, Cardano, THORChain, XRP Ledger, TON, and UTXO chains through simple RPC endpoints for balances, transactions, swaps, and network queries.
      Apache 2.0

    • Relay Protocol MCP Server

      warengonzaga
      A
      license
      A
      quality
      C
      maintenance
      Enables cross-chain bridging, multi-chain token swaps, and real-time pricing across over 50 blockchain networks using the Relay Protocol REST API. It allows users to browse thousands of tokens, generate quotes, and monitor transaction status directly through natural language.
      9
      1
      MIT

    • 3xpl MCP Server

      exekerey
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to interact with blockchain data across 48 networks via the 3xpl JSON API, supporting tools for transactions, addresses, blocks, and more.
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 26 tools

    Disambiguation2/5

    There is significant overlap and ambiguity among tools, especially in the fee estimation category where multiple tools (bsc_estimate_gas, celo_estimate_gas, eth_estimate_gas, estimate_gas, etc.) serve similar purposes for different blockchains, making it difficult for an agent to choose the correct one without deep chain-specific knowledge. The blockchain data tools also have overlapping functionalities, such as get_balances_v4, get_wallet_balances_v4, and get_wallet_portfolio_v4, which can confuse agents about which to use for balance queries.

    Naming Consistency3/5

    The naming is mixed with some consistency within categories but overall inconsistent patterns. Fee estimation tools use a mix of chain-specific prefixes (e.g., bsc_estimate_gas, eth_estimate_gas) and generic names (estimate_gas, estimate_fee_blockchain), while blockchain data tools follow a get_*_v4 pattern but with variations like check_owner_v4. Gateway tools use a consistent gateway_* prefix, but the overall set lacks a unified naming convention.

    Tool Count2/5

    With 26 tools, the count is too high for the apparent scope of blockchain data and fee estimation, leading to redundancy and complexity. Many tools could be consolidated (e.g., multiple chain-specific gas estimators into a unified tool), making the set feel bloated and difficult for agents to navigate efficiently.

    Completeness4/5

    The tool set covers a broad range of blockchain operations including fee estimation, data queries (balances, owners, metadata, collections), and gateway functionalities, with good coverage across multiple blockchains. However, there are minor gaps such as lack of tools for transaction submission or smart contract interaction, which might limit full lifecycle coverage but are not critical for the data-focused domain.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources