Skip to main content
Glama
forum-labs

forum-labs/payfetch

by forum-labs

Related Servers

Alternatives to forum-labs/payfetch

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A non-custodial USDC wallet on Base exposed as seven tools: address, balance, check, pay, earnings, report and recover. Spending limits (per transaction, per day, per counterparty, plus a destination allowlist) are enforced in code between deciding and signing, and the server runs locally over stdio so the key never leaves the machine.
      Apache 2.0
    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      A wallet and guardrail for AI agents, enabling spending limits, payment approvals, and real-time ledger tracking via memory or Stripe backends.
      MIT
    • A
      license
      A
      quality
      D
      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
      286 npm
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      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.
      22 npm
      Business Source 1.1

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: approving pending payments, listing receipts, fetching with payment, checking prices, and viewing spending status. No overlap in functionality.

    Naming Consistency5/5

    All tool names use descriptive verbs followed by nouns in snake_case (e.g., approve_pending, list_receipts), with consistent naming patterns throughout.

    Tool Count5/5

    5 tools is an ideal count for this server's purpose, covering the essential operations without unnecessary bloat.

    Completeness4/5

    Covers quoting, fetching, approving, auditing, and status checking. Minor gap: lack of a tool to cancel pending approvals or modify payments, but these might be intentionally excluded as operator-only actions.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive