A
licenseNot graded
qualityA
maintenanceMCP server that lets any AI agent operate a wallet directly on-chain: create wallets, send, swap, bridge, and deploy contracts across EVM and Bitcoin networks.
2
MIT
wallet-inspector-mcp
by kukapay
Related Servers
Alternatives to wallet-inspector-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes blockchain data as native tools for AI agents, enabling read-only queries like wallet balances and token holdings on Ethereum, Polygon, and Base.MIT
- AlicenseNot gradedqualityBmaintenanceMulti-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.31CC BY-4.0
- AlicenseNot gradedqualityBmaintenanceAn 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.1MIT
- AlicenseBqualityCmaintenanceAn MCP server that enables AI agents to interact with the Solana blockchain through 20 tools for wallet management, SPL token operations, blockchain exploration, and DeFi integration via Jupiter.21MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents real-time access to DeFi across multiple chains, enabling non-custodial crypto trading, portfolio queries, and transaction execution.147MIT
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
ResponsivenessNo issues