Skip to main content
Glama
whoyoujoshin

Aether Wallet

by whoyoujoshin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Related Servers

Alternatives to Aether Wallet

No user-submitted related servers found.

    Related Servers

    • PipRail by piprail

      PipRailofficial

      piprail
      A
      license
      A
      quality
      A
      maintenance
      A budget-bound x402 payment wallet for AI agents: it autonomously pays HTTP 402 payment-gated URLs across every major chain (EVM, Solana, and many non-EVM families). Self-custodial and backendless, your key, your RPC, with spend caps enforced before any on-chain send.
      8
      9
      MIT

    • AgentWallet MCP Server

      hifriendbot
      A
      license
      B
      quality
      A
      maintenance
      Provides permissionless wallet infrastructure for AI agents to manage wallets, sign transactions, and handle tokens across Solana and all EVM-compatible chains. It includes 29 specialized tools for on-chain operations, featuring built-in security guards and automated x402 payment processing without KYC requirements.
      40
      393 npm
      3
      MIT
    • Purple Flea Wallet by purple-flea

      Purple Flea Walletofficial

      purple-flea
      F
      license
      Not graded
      quality
      D
      maintenance
      Non-custodial HD wallet API for AI agents. Generate wallets on 6 chains (ETH, Base, SOL, BTC, TRX, XMR), check balances, send crypto, and swap cross-chain via Wagyu aggregator. 10% referral commissions.
      1 npm
      -

    • BotWallet MCP Server

      botwallet-co
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to manage USDC wallets on Solana, allowing them to send payments, create invoices, and access paid APIs within human-defined spending limits. It uses threshold signatures to provide agents with financial autonomy while ensuring secure oversight and transaction approval.
      36
      320 npm
      4
      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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a sharply distinct purpose: one reads an address's asset balances, one looks up a transaction by hash, and one searches an on-chain service directory. There is no plausible overlap in the resource or action each targets, so misselection is very unlikely.

    Naming Consistency5/5

    All three names follow the same snake_case verb_noun convention (get_balance, get_transaction_status, find_services). The verbs are intuitive and applied consistently to the resource they operate on.

    Tool Count4/5

    Three tools is on the lean side, but the server is explicitly a read-only observer with no wallet of its own, so a small, focused surface is defensible. It is slightly under-provisioned rather than bloated.

    Completeness4/5

    Balance lookup, transaction status, and service discovery cover the stated read-only purpose with no dead ends, but the surface lacks an address transaction history or asset metadata lookup, which are common adjacent needs an agent might expect.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources