Skip to main content
Glama
aeronlabs

aeron-wallet

Official
by aeronlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to aeron-wallet

No user-submitted related servers found.

    Related Servers

    • @bridgenode/mcp by bridgenode-ai

      @bridgenode/mcpofficial

      bridgenode-ai
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to make pay-as-you-go AI inference requests through x402 with automatic Solana USDC payments, no API keys or registration, while enforcing configurable spending limits.
      3
      118 npm
      1
      MIT No Attribution
    • 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

    • x402-rpc-gateway

      ffboers
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to sell or access Ethereum JSON-RPC requests over x402 with per-call USDC payments on Base, no accounts or API keys, including per-method pricing, policy enforcement, and privacy protections.
      1
      MIT

    • Budget Governor

      mightbesaad
      A
      license
      Not graded
      quality
      C
      maintenance
      Budget & cost control for AI agents: hard per-agent spend caps, rate limits, idempotency, and human-in-the-loop approval — enforced before each LLM call, not after the invoice. One hosted MCP endpoint (no proxy or self-hosting), settled via x402 (USDC on Base).
      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

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct concern: wallet address, balances, payment execution, payment history, and session lifecycle. There is no meaningful overlap between payment history and session listing because one is about transactions and the other about scoped spending sessions.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern: get_address, get_balance, create_session, list_sessions, revoke_session. The single exception is 'history', which is a noun rather than a verb-led name like 'get_history' or 'list_payments'.

    Tool Count5/5

    Seven tools is well-scoped for a wallet and session-management server. Each tool earns its place and the size is neither bloated nor overly thin.

    Completeness4/5

    The core wallet capabilities and session lifecycle are covered: address, balance, payment, history, create, list, and revoke. Minor gaps remain, such as no way to retrieve full session configuration details or individual payment records, but agents can work around this with the current surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources