Skip to main content
Glama
Sign In
AgentWallet MCP Server

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
      D
      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
      69 npm
      MIT

    • clawsafe

      KostikGo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables autonomous AI agents to make policy-gated Solana micropayments, fetch x402 paid APIs, send SOL/USDC, and perform Jupiter swaps using an isolated burner wallet with enforced spend limits.
      Apache 2.0
    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

    Disambiguation4/5

    Most tools have clearly distinct targets: sign_transaction vs send_transaction vs transfer vs transfer_token are separated by explicit descriptions, and pay_x402/quote_x402/discover_x402 form a clear read-vs-pay gradient. The weakest area is the payments/reporting cluster (get_paywall_payments, get_x402_revenue, list_payments, export_receipts, get_usage), where an agent must read carefully to pick the right history/aggregate view, and approve_token vs approve_permit2 requires understanding Permit2.

    Naming Consistency4/5

    The dominant pattern is snake_case verb_noun (get_balance, create_paywall, list_wallets, check_token_risk), which is applied broadly and predictably. Deviations are minor but present: bare-verb or noun-only names such as transfer, spend_policy, wallet_mode, buy_verification_credits, and pay_x402/quote_x402/discover_x402 which lead with the domain noun instead of the verb.

    Tool Count2/5

    40 tools is well past the point where the surface stays legible for a single agent, and several do not earn their place: buy_verification_credits is an explicit no-op kept only for backwards compatibility, export_wallet_key explains rather than performs, and get_usage/wallet_mode are near-informational. The domain is genuinely broad (wallets, EVM+Solana transfers, DeFi approvals, x402 paywalls, ledger/policy), but the set could be consolidated to roughly 20-25 without losing capability.

    Completeness4/5

    Coverage is strong across the lifecycle: wallet create/list/get/delete/pause/unpause, native and token balances, transfers, approvals and allowance checks, contract calls, simulation, paywall CRUD, x402 discover/quote/pay, plus ledger, receipts and policy introspection. Gaps are modest — no wallet metadata/limit update, no lookup of a transaction or payment by hash, and no explicit transaction-status polling after broadcast.

    Maintenance

    ActivityActive
    ResponsivenessMixed handling

    Resources