Skip to main content
Glama
plural-pinelabs

pinelabs-mcp

by plural-pinelabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to pinelabs-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

    • razorpay-mcp

      indiamcp
      A
      license
      B
      quality
      D
      maintenance
      An MCP (Model Context Protocol) server that connects AI assistants like Claude directly to your Razorpay account.
      14
      22 npm
      1
      MIT

    • Interswitch MCP Server

      Dairus01
      A
      license
      C
      quality
      D
      maintenance
      An MCP server that enables AI assistants to interact with Interswitch APIs for payments, transfers, VAS, cardless paycodes, Transaction Search, Card 360, lending, payouts, agency banking, and fintech card-processing utilities.
      74
      79 npm
      1
      MIT
    • novapay-mcp by NovaPay

      novapay-mcpofficial

      NovaPay
      A
      license
      A
      quality
      D
      maintenance
      MCP server for NovaPay that enables AI agents to create payment links, poll payment status, manage session lifecycle, and generate merchant keys.
      9
      8 npm
      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.6/5.0

    Scored across 59 tools

    Disambiguation3/5

    Most tools target distinct resources and actions, but there are several near-overlapping lookup variants such as get_payment_link_details vs get_payment_link_by_id, get_order_details vs get_order_by_order_id, and get_payout_details vs get_payout_payments. The descriptions clarify the differences, but the naming and overlapping purposes still create real ambiguity for an agent selecting a tool.

    Naming Consistency4/5

    The set largely follows a consistent verb_noun pattern (create_*, get_*, update_*, delete_*, cancel_*), which makes navigation predictable. Minor deviations like list_plural_apis, fetch_order_payments, search_transaction, and detect_stack slightly break the pattern but do not make the naming chaotic.

    Tool Count1/5

    59 tools is far beyond the recommended scope for an MCP server and will create significant selection overhead for agents. Although the tools are organized across payments, subscriptions, payouts, settlements, docs, and code generation, the sheer count is an extreme mismatch for a usable agent-facing toolset.

    Completeness4/5

    The tool surface covers the major lifecycle operations for payment links, orders, payments, refunds, plans, subscriptions, presentations, payouts, and settlements. Minor gaps exist, such as no customer management tools despite subscriptions requiring a customer_id, and no single-refund lookup by refund ID, but these are workaroundable in most workflows.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources