Skip to main content
Glama
sapph1re

MCP Billing Gateway SDK

by sapph1re
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MCP Billing Gateway SDK

No user-submitted related servers found.

    Related Servers

    • JWT Doctor

      Baneado98
      A
      license
      Not graded
      quality
      C
      maintenance
      Template for creating MCP servers with a server-side paywall gate, enabling free local usage and premium hosted tier with Stripe and x402 payment lanes.
      MIT

    • Header Doctor

      Baneado98
      A
      license
      Not graded
      quality
      C
      maintenance
      A template for MCP servers that enforces a paywall gate, offering free local execution and monetizing premium features via Stripe or x402 payments.
      MIT

    • Prepcast MCP

      Bbadhub
      F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive framework for building and deploying commercial MCP servers with integrated billing, usage metering, and Stripe payment processing. It enables developers to monetize AI tools through a complete ecosystem including API key management, affiliate tracking, and automated deployment scripts.
      -

    • OpenAPI Doctor

      Baneado98
      A
      license
      A
      quality
      C
      maintenance
      A template for building MCP servers with a built-in paywall gate that offers free local execution and premium server-side execution via Stripe and x402 payment lanes.
      1
      MIT

    • Agent Bazaar

      TombStoneDash
      A
      license
      Not graded
      quality
      C
      maintenance
      Per-call billing and metering proxy for MCP tool servers. Providers set pricing via the open MCP Billing Spec (MIT), consumers pay through Stripe Connect with signed receipts and SLA monitoring.
      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

    B3.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined as retrieving billing information, making disambiguation trivial.

    Naming Consistency5/5

    The single tool name 'get_billing_info' follows a clear verb_noun pattern (get + billing_info), which is consistent with itself. Since there are no other tools, there is no inconsistency to evaluate, and the naming is straightforward.

    Tool Count2/5

    A single tool is too few for a server named 'MCP Billing Gateway SDK', which suggests a broader scope for managing billing operations. This minimal set likely leaves significant gaps in functionality, such as creating, updating, or deleting billing data, making it inappropriate for comprehensive billing tasks.

    Completeness1/5

    The tool set is severely incomplete for a billing gateway domain, as it only provides a read operation (get_billing_info) without any support for create, update, delete, or other essential billing workflows. This will cause agent failures when attempting to perform full billing lifecycle management.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources