# MCP Billing Gateway (remote · mcp-billing-gateway-production.up.railway.app)

Billing proxy for MCP servers. Adds Stripe and x402 crypto payments without writing billing code.

- Trust score: 76/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp-billing-gateway-production.up.railway.app`: 76/100 (this document), [markdown](https://verifymcp.io/servers/sapph1re-mcp-billing-gateway/mcp-billing-gateway-production.md), [page](https://verifymcp.io/servers/sapph1re-mcp-billing-gateway/mcp-billing-gateway-production)
- pypi · `mcp-billing-gateway`: 67/100, [markdown](https://verifymcp.io/servers/sapph1re-mcp-billing-gateway/mcp-billing-gateway.md), [page](https://verifymcp.io/servers/sapph1re-mcp-billing-gateway/mcp-billing-gateway)

## Channel facts

- Endpoint: `https://mcp-billing-gateway-production.up.railway.app/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 778 tokens (~64/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_server" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the MCP Billing Gateway server?

MCP Billing Gateway is a hosted endpoint at https://mcp-billing-gateway-production.up.railway.app/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http sapph1re-mcp-billing-gateway 'https://mcp-billing-gateway-production.up.railway.app/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "sapph1re-mcp-billing-gateway": {
      "url": "https://mcp-billing-gateway-production.up.railway.app/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sapph1re-mcp-billing-gateway": {
      "type": "http",
      "url": "https://mcp-billing-gateway-production.up.railway.app/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sapph1re-mcp-billing-gateway]
url = "https://mcp-billing-gateway-production.up.railway.app/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sapph1re-mcp-billing-gateway": {
      "type": "remote",
      "url": "https://mcp-billing-gateway-production.up.railway.app/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sapph1re-mcp-billing-gateway --url 'https://mcp-billing-gateway-production.up.railway.app/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sapph1re-mcp-billing-gateway:
    url: "https://mcp-billing-gateway-production.up.railway.app/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "sapph1re-mcp-billing-gateway": {
      "Transport": "http",
      "Url": "https://mcp-billing-gateway-production.up.railway.app/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sapph1re-mcp-billing-gateway -t streamable-http -u 'https://mcp-billing-gateway-production.up.railway.app/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "sapph1re-mcp-billing-gateway": {
      "type": "http",
      "url": "https://mcp-billing-gateway-production.up.railway.app/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 76, 0)

- [security] Stability: 0.97 → pass

### 2026-09-17 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (12)

### `register_operator` (~39 tokens)

Register a new operator account with Stripe Connect onboarding

Input parameters:

- `email` (string, required): Operator email address
- `name` (string, required): Operator or company name

### `get_operator_info` (~27 tokens)

Get current operator profile and status

Input parameters:

- `api_key` (string, required): Operator API key

### `list_servers` (~28 tokens)

List all MCP servers registered by the operator

Input parameters:

- `api_key` (string, required): Operator API key

### `create_server` (~123 tokens)

Register a new MCP server for billing

Input parameters:

- `api_key` (string, required): Operator API key
- `auth_mode` (string): Auth mode: header (default) or query
- `description` (string): Server description
- `is_public` (boolean): Whether to list in public server directory
- `name` (string, required): Server display name
- `proxy_slug` (string, required): URL slug for the billing proxy endpoint
- `transport` (string): Transport type: http (default) or stdio
- `upstream_url` (string, required): Upstream MCP server URL

### `get_server` (~36 tokens)

Get server details including pricing plans

Input parameters:

- `api_key` (string, required): Operator API key
- `server_id` (string, required): Server ID

### `update_server` (~99 tokens)

Update server settings (name, description, upstream_url, is_public, status)

Input parameters:

- `api_key` (string, required): Operator API key
- `description` (string): New description
- `is_public` (boolean): Public listing toggle
- `name` (string): New server name
- `server_id` (string, required): Server ID
- `status` (string): Server status (active/paused)
- `upstream_url` (string): New upstream URL

### `delete_server` (~40 tokens)

Soft-delete a server (can be restored)

Input parameters:

- `api_key` (string, required): Operator API key
- `server_id` (string, required): Server ID to delete

### `create_plan` (~155 tokens)

Create a pricing plan for a server

Input parameters:

- `api_key` (string, required): Operator API key
- `billing_model` (string, required): Billing model
- `free_calls_per_month` (number): Free calls per month
- `is_default` (boolean): Set as default plan for this server
- `name` (string, required): Plan name
- `price_per_call_usd_micro` (number): Price per call in USD micros (1/1,000,000)
- `server_id` (string, required): Server ID
- `subscription_call_limit` (number): Max calls per subscription period
- `subscription_interval` (string): Subscription interval (month/year)
- `subscription_price_usd_cents` (number): Monthly subscription price in cents

### `list_plans` (~37 tokens)

List pricing plans for a server

Input parameters:

- `api_key` (string, required): Operator API key
- `server_id` (string, required): Server ID

### `update_plan` (~98 tokens)

Update a pricing plan

Input parameters:

- `api_key` (string, required): Operator API key
- `free_calls_per_month` (number): New free call limit
- `is_active` (boolean): Activate or deactivate plan
- `is_default` (boolean): Set as default plan
- `name` (string): New plan name
- `plan_id` (string, required): Plan ID
- `price_per_call_usd_micro` (number): New price per call

### `get_usage` (~69 tokens)

Get usage analytics for a server (calls, revenue, top callers)

Input parameters:

- `api_key` (string, required): Operator API key
- `from` (string): Start date (YYYY-MM-DD)
- `server_id` (string, required): Server ID
- `to` (string): End date (YYYY-MM-DD)

### `get_revenue` (~27 tokens)

Get revenue summary and payout history

Input parameters:

- `api_key` (string, required): Operator API key

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sapph1re-mcp-billing-gateway/mcp-billing-gateway-production#diagnostics

## Score history

- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 74
- 2026-09-13: 74
- 2026-09-12: 73
- 2026-09-11: 73
- 2026-09-10: 72
- 2026-09-09: 72
- 2026-09-08: 72
- 2026-09-07: 71
- 2026-09-06: 71
- 2026-09-05: 70
- 2026-09-04: 70
- 2026-09-03: 69
- 2026-09-02: 69
- 2026-09-01: 68
- 2026-08-31: 68
- 2026-08-30: 67
- 2026-08-29: 67
- 2026-08-28: 66
- 2026-08-27: 66
- 2026-08-26: 65
- 2026-08-25: 65
- 2026-08-24: 65
- 2026-08-23: 64
- 2026-08-22: 64

## Common questions

### What is the MCP Billing Gateway server?

MCP Billing Gateway is listed in the public MCP registry as io.github.sapph1re/mcp-billing-gateway. Billing proxy for MCP servers. Adds Stripe and x402 crypto payments without writing billing code. This page covers its hosted endpoint (https://mcp-billing-gateway-production.up.railway.app/mcp/).

### Is the MCP Billing Gateway server safe to use?

MCP Billing Gateway scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MCP Billing Gateway server expose?

MCP Billing Gateway exposes 12 tools: register_operator, get_operator_info, list_servers, create_server, get_server, and 7 more. Their descriptions and schemas cost roughly 778 tokens of context every time the server is loaded.

### Does the MCP Billing Gateway server require authentication?

No. We connected to MCP Billing Gateway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MCP Billing Gateway server still maintained?

MCP Billing Gateway is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp-billing-gateway-production.up.railway.app/mcp/
- Repository: https://github.com/sapph1re/mcp-billing-gateway-sdk
- Changelog RSS feed: https://verifymcp.io/servers/sapph1re-mcp-billing-gateway/mcp-billing-gateway-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/sapph1re-mcp-billing-gateway/mcp-billing-gateway-production.json
- HTML version of this page: https://verifymcp.io/servers/sapph1re-mcp-billing-gateway/mcp-billing-gateway-production