Skip to main content
Glama
NovaPay

novapay-mcp

Official
by NovaPay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to novapay-mcp

No user-submitted related servers found.

    Related Servers

    • AdvinPay MCP by AdvinPay

      AdvinPay MCPofficial

      AdvinPay
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server to connect AI assistants to the AdvinPay payment API, enabling PIX charges, transaction queries, and documentation search.
      MIT

    • lipila-mcp

      zencoder01
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the Lipila payment gateway, enabling AI agents to initiate mobile money and card collections, disburse funds, check transaction statuses, and verify webhook callbacks.
      1
      -

    • adaptis-mcp-server

      fredericktvf
      F
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that lets AI agents interact with the Adaptis (MEG) payment gateway, enabling payment link creation, transaction queries, refunds, and integration helpers like generating signed forms and verifying callbacks.
      -

    • AgentPay

      joepangallo
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AgentPay — the payment gateway for autonomous AI agents. Fund a wallet once, give your agent the key, and it discovers, provisions, and pays for tool APIs on its own. One key, every tool.
      112 npm
      1
      MIT

    • merchant-mcp

      autopaylab
      A
      license
      Not graded
      quality
      C
      maintenance
      A universal MCP server that provides a single merchant interface for AI agents across multiple protocols, enabling catalog browsing, checkout creation, and transaction status queries.
      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

    A4.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: key generation, two session creation flows, two payment addition flows, status retrieval, and three lifecycle operations. The distinction between acquiring and checkout sessions is clear, and void/expire/complete_hold have explicit use-case boundaries.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (generate_keys, create_acquiring_session, add_checkout_payment, etc.). The verbs and objects are uniformly structured, with no mixed casing or naming style deviations.

    Tool Count5/5

    With 9 tools, the set is well-scoped for a payment processing server. Each tool serves a distinct step in the payment lifecycle—onboarding, session creation, payment addition, status polling, and post-payment actions—without redundancy or bloat.

    Completeness5/5

    The tool set covers the full payment session lifecycle: key generation, session creation for both acquiring and checkout, payment addition, status tracking, and resolution via hold completion, void, or expiration. There are no obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources