Skip to main content
Glama
Fizzl13

presign-guard-wallet-mcp

by Fizzl13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to presign-guard-wallet-mcp

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

    • 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
    • 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

    • agentic-pay

      ShieldCubed
      A
      license
      Not graded
      quality
      D
      maintenance
      Non-custodial payment engine for AI agents supporting BTC, ETH, USDT, USDC, XRP, XMR, and ZEC. Exposes wallet, invoice, and payment tools over MCP with per-agent spend limits, plus x402 pay-per-call support.
      47 npm
      Business Source 1.1
    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/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools target distinct actions: sending USDC, sending native coin, pausing, viewing status, discovering services, and paying an x402 endpoint. send_usdc and pay_x402 both move USDC out of the wallet, so an agent could momentarily conflate a direct transfer with a 402 payment, but the descriptions draw a reasonably clear line.

    Naming Consistency4/5

    Names follow a predictable snake_case verb_noun pattern (send_usdc, send_native, pause_spending, find_services, pay_x402). wallet_status is noun-first rather than verb-first, a minor deviation that stays readable and unambiguous.

    Tool Count5/5

    Six tools is a tight, well-scoped set for a guarded spending wallet, and each one earns its place: transfer, pay, pause, inspect, discover. Nothing feels redundant or missing at the count level.

    Completeness3/5

    Core money-moving and safety flows are covered, but the lifecycle has gaps: pause_spending implies the owner resumes later yet there is no resume/unpause tool, and there is no transaction or payment history surface. Agents can work around these, but they are notable omissions for a wallet.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources