Skip to main content
Glama
investorphem

AbaPay

by investorphem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to AbaPay

No user-submitted related servers found.

    Related Servers

    • voulti-mcp

      csacanam
      A
      license
      Not graded
      quality
      B
      maintenance
      Accept crypto payments from AI agents: create an invoice in one call and get a hosted checkout link (USDC/USDT on Celo, Base, Arbitrum, Polygon, BSC). No API key, instant self-custody settlement.
      MIT

    • agentic-pay

      ShieldCubed
      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
    • ShieldZ Crypto Payments by ShieldZCash

      ShieldZ Crypto Paymentsofficial

      ShieldZCash
      A
      license
      A
      quality
      B
      maintenance
      Keyless crypto payments for AI agents. One MCP call turns any wallet address into a non-custodial crypto payment link or tip jar, no API key and no account, with funds settling straight to your wallet at a 0% platform fee (USDC/USDT, BTC, LTC, DASH, DOGE, ZCASH).
      3
      34 npm
      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
    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.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct operation: capabilities discovery, balance check, plan listing, international catalogue browsing, transaction history, schedule management (list/cancel/create), and payment (single or batch). The only close pair pay_bill/pay_bill_batch is clearly separated by recipient count (1 vs 2-20), and descriptions explicitly disambiguate.

    Naming Consistency4/5

    Most tools follow verb_noun (check_balance, list_plans, cancel_schedule, pay_bill, schedule_bill, pay_bill_batch), and list_* groups are consistent. transaction_history breaks the pattern as a noun phrase rather than a verb-based action (e.g., get_transactions), but overall the naming is predictable.

    Tool Count5/5

    10 tools provide a well-scoped surface for a bill-payment platform, covering capabilities, balances, plans, history, single/batch payments, and schedules without bloat. Each tool serves a clear purpose and the count is appropriate.

    Completeness4/5

    The server covers the main lifecycle: pay, schedule, list schedules, cancel, balance, history, and plan discovery. The only notable gap is no update operation for schedules—users must cancel and recreate—but this is a minor workaround. Overall the surface is nearly complete.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources