MCP Billing Gateway
REMOTE · MCP-BILLING-GATEWAY-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS
Billing proxy for MCP servers. Adds Stripe and x402 crypto payments without writing billing code.
Available components
Last scanned (21 hours ago)
Scores higher than 8% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Finance and Payments
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 25 Oct 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 19 Aug 26 0
First indexed and scored.
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 4 Nov 2026 · Probed https://mcp-billing-gateway-production.up.railway.app/mcp/
TLS unreached
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 Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
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/ | Unreachable | ||
| http (plaintext) | http://mcp-billing-gateway-production.up.railway.app/mcp/ | HTTPS enforced |
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.
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/'
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 23 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?
Its publisher declares no required credentials for MCP Billing Gateway. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the MCP Billing Gateway server still maintained?
MCP Billing Gateway is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.