MCP Billing Gateway
REMOTE · MCP-BILLING-GATEWAY-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED SEP 20
Billing proxy for MCP servers. Adds Stripe and x402 crypto payments without writing billing code.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 778 tokens (~64/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · mcp-billing-gateway-production.up.railway.app
claude mcp add --transport http sapph1re-mcp-billing-gateway 'https://mcp-billing-gateway-production.up.railway.app/mcp/'
{
"mcpServers": {
"sapph1re-mcp-billing-gateway": {
"url": "https://mcp-billing-gateway-production.up.railway.app/mcp/"
}
}
} {
"servers": {
"sapph1re-mcp-billing-gateway": {
"type": "http",
"url": "https://mcp-billing-gateway-production.up.railway.app/mcp/"
}
}
} [mcp_servers.sapph1re-mcp-billing-gateway] url = "https://mcp-billing-gateway-production.up.railway.app/mcp/"
{
"$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 mcp add sapph1re-mcp-billing-gateway --url 'https://mcp-billing-gateway-production.up.railway.app/mcp/' --transport streamable-http
mcp_servers:
sapph1re-mcp-billing-gateway:
url: "https://mcp-billing-gateway-production.up.railway.app/mcp/" {
"McpServers": {
"sapph1re-mcp-billing-gateway": {
"Transport": "http",
"Url": "https://mcp-billing-gateway-production.up.railway.app/mcp/"
}
}
} assistant mcp add sapph1re-mcp-billing-gateway -t streamable-http -u 'https://mcp-billing-gateway-production.up.railway.app/mcp/'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 8 Sept 26 +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.
- 6 Sept 26 +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.
- 4 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp-billing-gateway-production.up.railway.app/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp-billing-gateway-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp-billing-gateway-production.up.railway.app/mcp/ | Verified | 200 | |
| http (plaintext) | http://mcp-billing-gateway-production.up.railway.app/mcp/ | HTTPS enforced | 301 | https://mcp-billing-gateway-production.up.railway.app/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_plan ~155
Create a pricing plan for a server
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Operator API key |
| billing_model | string | yes | Billing model |
| free_calls_per_month | number | – | Free calls per month |
| is_default | boolean | – | Set as default plan for this server |
| name | string | yes | Plan name |
| price_per_call_usd_micro | number | – | Price per call in USD micros (1/1,000,000) |
| server_id | string | yes | 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 |
No output schema declared.
No examples provided.
create_server ~123
Register a new MCP server for billing
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | 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 | yes | Server display name |
| proxy_slug | string | yes | URL slug for the billing proxy endpoint |
| transport | string | – | Transport type: http (default) or stdio |
| upstream_url | string | yes | Upstream MCP server URL |
No output schema declared.
No examples provided.
delete_server ~40
Soft-delete a server (can be restored)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Operator API key |
| server_id | string | yes | Server ID to delete |
No output schema declared.
No examples provided.
get_operator_info ~27
Get current operator profile and status
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Operator API key |
No output schema declared.
No examples provided.
get_revenue ~27
Get revenue summary and payout history
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Operator API key |
No output schema declared.
No examples provided.
get_server ~36
Get server details including pricing plans
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Operator API key |
| server_id | string | yes | Server ID |
No output schema declared.
No examples provided.
get_usage ~69
Get usage analytics for a server (calls, revenue, top callers)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Operator API key |
| from | string | – | Start date (YYYY-MM-DD) |
| server_id | string | yes | Server ID |
| to | string | – | End date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
list_plans ~37
List pricing plans for a server
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Operator API key |
| server_id | string | yes | Server ID |
No output schema declared.
No examples provided.
list_servers ~28
List all MCP servers registered by the operator
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Operator API key |
No output schema declared.
No examples provided.
register_operator ~39
Register a new operator account with Stripe Connect onboarding
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Operator email address | |
| name | string | yes | Operator or company name |
No output schema declared.
No examples provided.
update_plan ~98
Update a pricing plan
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | 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 | yes | Plan ID |
| price_per_call_usd_micro | number | – | New price per call |
No output schema declared.
No examples provided.
update_server ~99
Update server settings (name, description, upstream_url, is_public, status)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Operator API key |
| description | string | – | New description |
| is_public | boolean | – | Public listing toggle |
| name | string | – | New server name |
| server_id | string | yes | Server ID |
| status | string | – | Server status (active/paused) |
| upstream_url | string | – | New upstream URL |
No output schema declared.
No examples provided.
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.