Skip to main content
Glama
OraCool

bepaid-mcp

by OraCool
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to bepaid-mcp

No user-submitted related servers found.

    Related Servers

    • PayFast MCP

      theYahia
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with the South African PayFast payment gateway to manage transactions, subscriptions, and refunds. It allows users to create payments, query transaction statuses, and check settlement balances through the MCP protocol.
      8
      16 npm
      MIT
    • AgentTax MCP Server by AgentTax

      AgentTax MCP Serverofficial

      AgentTax
      A
      license
      A
      quality
      F
      maintenance
      Enables MCP tool developers and AI agents to track payments, calculate sales tax liability, and ensure tax compliance across US jurisdictions.
      6
      MIT

    • MyFatoorah MCP

      kuwaitdevs
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP hosts like Claude, VS Code, Cursor, and others to discover payment methods, create payment links, verify payments, inspect invoices, and manage refunds through focused tools, with a guided safe payment workflow and a restricted generic API escape hatch.
      7
      20 npm
      MIT

    • Payment-Risk-Exception-AI

      Beste-Oztunc
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides tools for retrieving transaction context and recording AI decisions or creating human reviews for payment risk exceptions. Enables LLM agents to handle exception transactions in a hybrid payment-decisioning workflow.
      -
    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.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a clearly distinct action: listing a period's transactions, looking up a single transaction (or by tracking_id), exporting to a file, and creating a payment link. The list/get distinction is standard and well-explained, leaving no realistic misselection risk.

    Naming Consistency5/5

    All four names share the bepaid_ prefix and follow a clean verb_noun pattern (list_transactions, get_transaction, export_transactions, create_payment_link). No style mixing or vague verbs.

    Tool Count4/5

    Four tools is a tight, focused set for transaction lookup/export plus payment-link creation, with each tool earning its place. It sits at the low end of the ideal 3-15 range, so slightly thin but not mismatched.

    Completeness3/5

    The read/reporting surface is solid (list, get, export) and creation of a payment link is covered, but there are no write/lifecycle operations such as refunds, payment cancellation, or status/webhook management. Notable gaps exist for an agent handling full payment workflows.

    Resources