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
web3agent
by Apegurus
Related Servers
Alternatives to web3agent
No user-submitted related servers found.
Related Servers
Syeniteofficial
FlicenseNot gradedqualityDmaintenanceA DeFi MCP server enabling AI agents to query lending rates, execute swaps/bridges, monitor positions, and access prediction markets across 30+ chains with a trust layer for calldata verification.-- 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.07MIT
- AlicenseBqualityCmaintenanceMCP server for Autonomous Intelligence, enabling AI agents to perform non-custodial, rug-gated multi-chain token swaps including safety checks, quotes, and execution.717 npmMIT
Armor Crypto MCPofficial
AlicenseCqualityCmaintenanceAn MCP server providing unified access to blockchain operations, bridging, swapping, and crypto trading strategies for AI agents.37179GPL 3.0- AlicenseNot gradedqualityAmaintenanceNon-custodial BVCC Agent Wallet MCP server: let an AI agent check balances, send native/ERC-20, approve, and swap on Uniswap v3/v4 across Ethereum, BNB Chain, Arbitrum and Base, within on-chain enforced limits.96 npm2MIT
TDQS
C2.8/5.0
Scored across 195 tools
Disambiguation2/5
With 195 tools, there is substantial overlap between tool families (e.g., evm_get_balance, get_balance, and explorer_get_historical_balance; multiple token-resolution tools). Descriptions help in some cases, but the sheer number of near-synonymous operations makes misselection likely, especially across market, explorer, and EVM domains.
Naming Consistency2/5
Naming conventions are inconsistent: some tools use snake_case with domain prefixes (market_get_*), others use bare verbs (get_address, sign_message), and there are duplicate variants like convert_to_base_units vs convert_to_base_unit and get_token_allowance vs get_token_allowance_evm. This mix of patterns and redundant suffixes reduces predictability.
Tool Count1/5
195 tools is an extreme count that overwhelms rather than serves the user. Many tools are redundant or deprecated (see market_get_ticker), and the surface area is far too large for an agent to navigate effectively. Even for a broad web3 domain, this is excessive and poorly curated.
Completeness3/5
Core web3 workflows are covered: market data, contract interaction, wallet operations, swaps, bridges, and job protocols. However, there are notable gaps such as NFT transfers, contract deployment, and unified lifecycle management for some token operations. The presence of deprecated tools and duplicate implementations further muddies coverage.
Maintenance
ActivityStale
ResponsivenessNo issues