Añade suscripciones de Stripe, créditos por llamada y pagos cripto x402 a cualquier servidor MCP, sin escribir código de facturación.
La Pasarela de Facturación MCP es un proxy de facturación alojado que se sitúa entre los agentes de IA y tu servidor MCP. Gestiona automáticamente la verificación de pagos, el seguimiento de uso y la aplicación de niveles. Registras tu servidor, estableces un plan de precios y diriges a los usuarios a la URL del proxy. No se requiere código de facturación.
Servicio en vivo: https://mcp-billing-gateway-production.up.railway.app
pip install mcp-billing-gatewayO con uvx:
uvx mcp-billing-gatewayAñade a ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) o %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"mcp-billing-gateway": {
"command": "uvx",
"args": ["mcp-billing-gateway"]
}
}
}Añade a .cursor/mcp.json en tu proyecto:
{
"mcpServers": {
"mcp-billing-gateway": {
"command": "uvx",
"args": ["mcp-billing-gateway"]
}
}
}Reinicia tu editor después de añadir la configuración para activar el servidor MCP.
Related MCP server: Agent Bazaar
Herramienta | Descripción |
| Devuelve las capacidades del servicio, métodos de pago soportados, características y documentación de integración |
El servidor MCP local proporciona descubrimiento de servicios. La funcionalidad completa de facturación se ejecuta en la pasarela alojada: regístrate como operador y haz proxy de tus servidores MCP a través de ella.
AI Agent → MCP Billing Gateway → Your MCP Server
(billing enforced here)Regístrate como operador y obtén una clave API
Registra la URL de tu servidor MCP + plan de precios
Dirige a los usuarios a tu slug de proxy: https://mcp-billing-gateway-production.up.railway.app/proxy/{your-slug}/mcp
Los usuarios pagan mediante clave API de Stripe o USDC x402: la facturación se gestiona de forma transparente
Facturación por llamada — cobra a los usuarios por llamada a herramienta (fiat o cripto)
Suscripciones — planes mensuales/anuales de Stripe con límites de llamadas
Precios escalonados — nivel gratuito + niveles de pago basados en el uso
Micropagos x402 — acepta USDC en Base de agentes de IA sin necesidad de claves API
Panel de operador — realiza un seguimiento de ingresos, uso y usuarios en tiempo real
Transporte MCP — transporte MCP HTTP completo y transmitible en el endpoint /mcp/
curl -X POST https://mcp-billing-gateway-production.up.railway.app/api/v1/operator/register \
-H "Content-Type: application/json" \
-d '{"email": "you@example.com", "name": "Your Name"}'Respuesta:
{
"operator_id": "op_abc123",
"api_key": "bg_live_xxxxxxxxxxxx",
"message": "Operator registered successfully"
}curl -X POST https://mcp-billing-gateway-production.up.railway.app/api/v1/servers \
-H "Authorization: Bearer bg_live_xxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{
"name": "My MCP Server",
"upstream_url": "https://your-mcp-server.com/mcp",
"proxy_slug": "my-server"
}'curl -X POST https://mcp-billing-gateway-production.up.railway.app/api/v1/servers/{server_id}/plans \
-H "Authorization: Bearer bg_live_xxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{
"name": "Pay as you go",
"billing_model": "per_call",
"price_per_call_usd_micro": 10000,
"free_calls_per_month": 100
}'{
"mcpServers": {
"my-server": {
"url": "https://mcp-billing-gateway-production.up.railway.app/proxy/my-server/mcp",
"headers": {
"Authorization": "Bearer CALLER_API_KEY"
}
}
}
}Método | Ideal para | Cómo |
Suscripción Stripe | Desarrolladores humanos | Plan mensual o anual vía Stripe Checkout |
Stripe por llamada | Desarrolladores humanos | Créditos consumidos por llamada a herramienta |
Micropagos x402 | Agentes de IA | USDC en Base, no se necesitan claves API |
# Using the MCP client
result = await session.call_tool("get_billing_info")
print(result)
# {
# "service": "MCP Billing Gateway",
# "version": "0.1.0",
# "payment_methods": ["stripe_subscription", "stripe_metered", "x402_crypto"],
# "features": ["Per-call usage tracking", "Tiered pricing", ...],
# "live_service": "https://mcp-billing-gateway-production.up.railway.app"
# }# 1. Register
API_KEY=$(curl -s -X POST .../api/v1/operator/register \
-H "Content-Type: application/json" \
-d '{"email": "dev@example.com", "name": "Dev"}' | jq -r .api_key)
# 2. Add your server
SERVER_ID=$(curl -s -X POST .../api/v1/servers \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "my-tool", "upstream_url": "https://my-tool.com/mcp", "proxy_slug": "my-tool"}' \
| jq -r .server_id)
# 3. Set pricing: $0.01 per call, 100 free calls/month
curl -X POST .../api/v1/servers/$SERVER_ID/plans \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "Starter", "billing_model": "per_call", "price_per_call_usd_micro": 10000, "free_calls_per_month": 100}'
# Callers now connect via: .../proxy/my-tool/mcpAccede a tu panel en:
https://mcp-billing-gateway-production.up.railway.app/dashboardRealiza un seguimiento de ingresos, uso, usuarios activos y configura tus servidores en tiempo real.
Endpoint | Método | Descripción |
| POST | Crear cuenta de operador |
| GET | Ver perfil y claves API |
| GET | Estadísticas de ingresos y uso |
Endpoint | Método | Descripción |
| POST | Registrar un servidor MCP |
| GET | Listar tus servidores |
| POST | Crear plan de precios |
Endpoint | Método | Descripción |
| ANY | Llamadas proxy con aplicación de facturación |
| ANY | Transporte MCP HTTP transmitible |
┌─────────────┐ ┌──────────────────────┐ ┌──────────────────┐
│ AI Agent / │────▶│ MCP Billing Gateway │────▶│ Your MCP Server │
│ MCP Client │◀────│ (hosted on Railway) │◀────│ (upstream) │
└─────────────┘ └──────────────────────┘ └──────────────────┘
│
├── Payment verification (Stripe / x402)
├── Usage tracking & rate limiting
├── Tier enforcement
└── Operator dashboardLa pasarela es un proxy transparente. Los usuarios interactúan con tu servidor MCP normalmente: la pasarela intercepta las solicitudes, verifica el pago, rastrea el uso y reenvía al servidor upstream.
La pasarela está abierta para su uso en la URL alojada anteriormente. Para despliegues autoalojados, clona el repositorio del servidor y despliega mediante Docker:
docker build -t mcp-billing-gateway .
docker run -p 3000:3000 mcp-billing-gatewayGet information about the MCP Billing Gateway service and integration options.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but fails to detail aspects like authentication needs, rate limits, response format, or error handling. This leaves significant gaps in understanding how the tool behaves.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse and understand quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has zero parameters, 100% schema coverage, and an output schema exists, the description's focus on purpose is adequate. However, it lacks behavioral details (e.g., response structure, error cases) that could enhance completeness, especially since no annotations are provided to fill those gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and the input schema coverage is 100%, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose, which aligns with the baseline expectation for parameterless tools.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get information') and target resource ('MCP Billing Gateway service and integration options'), making the purpose understandable. It lacks sibling tools for differentiation, but the scope is well-defined. No tautology or misleading elements are present.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool, such as for setup, troubleshooting, or comparison with other services. The description implies usage for general information retrieval but offers no context, alternatives, or exclusions, leaving the agent without operational direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.2get_billing_infoScored across 1 tool
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.
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.
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.
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.
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Monetize any MCP server: x402 paywall, pay-per-call billing in USDC on Base, agent marketplace.
MCP server for Pinchwork - an agent-to-agent task marketplace with credits-based economy
