Skip to main content
Glama
kukapay

wallet-inspector-mcp

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to wallet-inspector-mcp

No user-submitted related servers found.

    Related Servers

    • mcw

      devIykee
      A
      license
      Not graded
      quality
      B
      maintenance
      Multi-chain wallet MCP server that enables AI agents to manage Bitcoin, Ethereum, Solana, and Tron wallets via tools for addresses, balances, transactions, and token operations.
      56 npm
      CC BY-4.0

    • defi-mcp

      matiosera3-ops
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI agents direct, on-chain access to DeFi data on EVM chains — wallet balances, Aave v3 lending positions, and live token prices, with no centralized API in the middle.
      35 PyPI
      1
      MIT

    • @y0exchange/mcp

      y0exchange
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI agents real-time access to DeFi across multiple chains, enabling non-custodial crypto trading, portfolio queries, and transaction execution.
      13 npm
      7
      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

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_wallet_activity focuses on general activity (like transfers, interactions), get_wallet_balance retrieves current token holdings, and get_wallet_transactions fetches detailed transaction lists. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'get_wallet_' as a prefix, followed by a specific noun (activity, balance, transactions). This uniformity enhances readability and predictability across the toolset.

    Tool Count3/5

    With only 3 tools, the set feels thin for a wallet inspector domain, lacking operations like updating or managing wallets, or querying specific transaction details. While the tools cover basic read operations, the scope is minimal and may limit agent capabilities.

    Completeness2/5

    The toolset is severely incomplete for a wallet inspector. It only provides read operations (get) without any create, update, or delete capabilities, and misses key functions like analyzing transaction patterns, checking token approvals, or interacting with smart contracts, leaving significant gaps for agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources