Skip to main content
Glama
forum-labs/payfetch

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.
      1
      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
      10
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI assistants a non-custodial wallet that can pay x402 endpoints and send QU on the Qubic network, but only within human-set spending caps, allowlists, and approval requests enforced in code outside the agent. Keys stay in the local OS keychain, and every payment is journaled before sending and settled from the chain afterwards.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with a prepaid, capped payment method so they can request charges without accessing real accounts. Enforces spending limits, requires human approval for larger transactions, and supports out-of-band approvals via CLI, dashboard, or Telegram.
      MIT

    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

    ActivityInactive
    ResponsivenessLimited data