Skip to main content
Glama
hifriendbot

AgentWallet MCP Server

by hifriendbot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to AgentWallet MCP Server

No user-submitted related servers found.

    Related Servers

    • waiaas

      waiaas
      A
      license
      C
      quality
      C
      maintenance
      Self-hosted wallet MCP server for AI agents. Provides 42 tools for multi-chain crypto operations: transfers, token management, DeFi (swap, lend, stake, bridge, perp), NFT, smart contracts, and x402 payments. Supports EVM and Solana with policy engine, spending limits, and human approval.
      60
      29
      MIT

    • obol

      halfkey
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to access Solana wallet analytics, token data, and DeFi tools via pay-per-request USDC micropayments using the x402 protocol, without API keys or subscriptions.
      13
      19 npm
      MIT

    • Solana MCP Server

      visioneth
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to read chain data, execute transactions, swap tokens, and manage wallets on Solana through 38 tools across 7 modules. Supports write operations with a private key and includes built-in prompts for common workflows.
      38
      1
      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.4/5.0

    Scored across 40 tools

    Disambiguation3/5

    Several overlapping tools exist: sign_transaction/send_transaction/simulate_transaction, transfer/transfer_token, and pay_x402/quote_x402/discover_x402 have intertwined purposes. Descriptions do provide strong guidance, but the boundaries still require careful reading and misselection is plausible.

    Naming Consistency4/5

    Mostly consistent verb_noun snake_case (list_wallets, get_balance, create_paywall), with only minor deviations like check_approval and spend_policy that are still readable. No mixing of camelCase or chaotic patterns.

    Tool Count2/5

    40 tools is heavy for the server's apparent scope, packing wallet management, DeFi helpers, x402 payments, paywalls, and ledger tooling into one surface. This likely forces agents to scan a large registry and increases the chance of poor tool selection.

    Completeness4/5

    Coverage is broad and lifecycle-rich: wallet CRUD, transfers, approvals, paywalls, payments, policy, receipts, and custody reporting are all present. Only minor gaps exist, such as no explicit update_wallet for labels/limits and no transaction history listing for broadcasted sends outside the ledger view.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources