Skip to main content
Glama

Related Servers

Alternatives to gexno-web3

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to fetch live multi-chain portfolio, token info, gas prices, and token prices across Ethereum, Base, Polygon, Arbitrum, and Optimism with a single call. No API key required.
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Read-only on-chain intelligence for AI agents on Base, providing tools to read balances, token metadata, gas, and transaction status live from chain without API keys.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to perform pay-per-call security verification of wallets, tokens, contracts, dApps, agents, and more via a remote endpoint with no installation.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query on-chain data across EVM chains like Base, Optimism, Avalanche, Celo, and Arbitrum, including balances, transactions, gas, and smart contract interactions.
      49 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Lets AI agents check whether an EVM wallet address carries an EIP-7702 delegation across eight chains (Ethereum, Base, BNB Chain, Arbitrum, OP, Polygon, Gnosis, Unichain) and learn how to obtain a deeper paid report with delegate bytecode heuristics and risk levels. Read-only, never touching private keys or seed phrases.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to trace Ethereum transactions and addresses, check recipients before payment, and run wallet checkups for risky approvals, returning route evidence as plain text and JSON.
      MIT

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools target clearly distinct resources: an Ethereum wallet lookup versus an NFT metadata resolver. Their descriptions make the boundary unambiguous, with no overlap in purpose.

    Naming Consistency5/5

    Both names follow the same predictable lookup_noun pattern (lookup_wallet, lookup_nft). The convention is consistent and easy for an agent to infer.

    Tool Count3/5

    Only two tools are provided, which feels thin for a Web3 server even if the scope is deliberately narrow. Each tool is meaningful, but the surface is borderline minimal.

    Completeness2/5

    The surface covers wallet summaries and NFT metadata only, leaving obvious Web3 gaps such as transaction lookup, ERC-20/token balances, ENS resolution, or contract data. Agents would frequently hit dead ends for common blockchain queries.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data