Skip to main content
Glama
FoxRick

paygentic

by FoxRick
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to paygentic

No user-submitted related servers found.

    Related Servers

    • Procfy

      mcp-dir
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables financial management through the Procfy API, allowing AI agents to manage transactions, bank accounts, contacts, and more via natural language.
      1
      MIT

    • remit.md MCP Server

      pay-skill
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to perform financial transactions such as direct payments, escrows, and bounty management using natural language with zero code integration. It provides a comprehensive suite of tools for fund streaming, subscriptions, and reputation tracking to facilitate secure agent-to-agent commerce.
      11 npm
      MIT

    • paybot-mcp

      RBKunnela
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to perform and manage payments through the Model Context Protocol, including paying, checking balances and history, registering bots, setting spending limits, discovering supported networks and tokens, inspecting commissions, and managing bot pools. It also supports governed tool calls with policy decisions, human approval, and tamper-evident audit traces.
      12
      19 npm
      Apache 2.0

    • Magpie MCP Server

      domdanao
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access Magpie Payment Platform APIs for processing payments, creating checkout sessions, sending invoices, and managing payment links through natural conversation.
      29 npm
      2
      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.5/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a well-defined and distinct purpose, covering wallet management, invoices, policies, transactions, and account setup. Even similar actions like sending money and requesting payment are clearly differentiated by their descriptions.

    Naming Consistency5/5

    All tools follow a consistent `verb_noun` pattern with the `paygentic_` prefix. The verbs are clear and the nouns are specific, making the tool names predictable and easy to interpret.

    Tool Count5/5

    With 13 tools, the server covers a comprehensive set of operations for a payment/wallet system without being overwhelming. The count is well within the typical 3-15 range for a focused service.

    Completeness4/5

    The server covers core operations like creating wallets, handling invoices, setting policies, and sending money. Minor gaps exist, such as missing update/delete for wallets and invoices, but these are not critical for basic functionality.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources