# PayGate MCP — Monetization Gateway for AI Agents (remote · paygate-mcp.rendercriativo.workers.dev)

Monetize any MCP server: x402 paywall, pay-per-call billing in USDC on Base, agent marketplace.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `paygate-mcp.rendercriativo.workers.dev`: 62/100 (this document), [markdown](https://verifymcp.io/servers/geoacpfilho-paygate-monetize-monetization-x402/paygate-mcp.md), [page](https://verifymcp.io/servers/geoacpfilho-paygate-monetize-monetization-x402/paygate-mcp)

## Channel facts

- Endpoint: `https://paygate-mcp.rendercriativo.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.1`

## 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-08-20.

- **Endpoint Security**: 46/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 3 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 check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1165 tokens (~166/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http geoacpfilho-paygate-monetize-monetization-x402 https://paygate-mcp.rendercriativo.workers.dev/mcp
```

### Codex

```toml
[mcp_servers.geoacpfilho-paygate-monetize-monetization-x402]
url = "https://paygate-mcp.rendercriativo.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "geoacpfilho-paygate-monetize-monetization-x402": {
      "type": "remote",
      "url": "https://paygate-mcp.rendercriativo.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add geoacpfilho-paygate-monetize-monetization-x402 --url https://paygate-mcp.rendercriativo.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  geoacpfilho-paygate-monetize-monetization-x402:
    url: "https://paygate-mcp.rendercriativo.workers.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "geoacpfilho-paygate-monetize-monetization-x402": {
      "type": "http",
      "url": "https://paygate-mcp.rendercriativo.workers.dev/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-08-19 (score 62, +1)

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

### 2026-08-17 (score 61, +1)

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

### 2026-08-15 (score 60, +1)

- [functional regression] Schema quality: 1046 → 1165
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.2.0 → 0.3.1
- [functional] New tool “verify_ownership”
- [cosmetic] “list_registered_servers” added an optional parameter “verified_only”

### 2026-08-14 (score 59)

First indexed and scored.

## MCP tools (6)

### `list_registered_servers` (~139 tokens)

Find a paid tool that does something you cannot do yourself. Use when the user needs a capability you lack and is willing to pay per use, or asks what paid tools, APIs or data sources are available. Returns every tool on the market with its price per call in USD and the endpoint to call it. Browsing is free and needs no key.

Input parameters:

- `max_price_usd` (number): Only return tools priced at or below this amount per call.
- `search` (string): Case-insensitive match against tool names, descriptions and seller names.
- `verified_only` (boolean): Return only sellers who proved they own the server they sell.

### `register_server` (~271 tokens)

Start charging for an MCP server the user owns. Use when they want to monetize, sell, charge for, get paid for, put a price on, or make money from a server, API or tool. Buyers pay their wallet DIRECTLY on-chain — PayGate never holds the money, so there is no payout to wait for, no balance to withdraw and no commission taken. Their server is never modified and needs no payment code. Tools are imported automatically, so it must be publicly reachable over HTTPS and answer tools/list. Returns a proxy URL and a secret api_key shown only once; save it, every other seller tool needs it.

Input parameters:

- `default_price_usd` (number): Price per call applied to every imported tool. Defaults to 0.02.
- `email` (string): Optional contact address.
- `name` (string, required): Display name of the service in the marketplace.
- `stripe_account_id` (string): Stripe Connect account (acct_...) to receive fiat instead. Only for tools priced at $0.50 or above.
- `target_server_url` (string, required): Public HTTPS URL of the MCP server to monetize, e.g. https://example.com/mcp
- `wallet_address` (string): EVM address that receives USDC on Base. Required unless stripe_account_id is given.

### `set_tool_price` (~119 tokens)

Reprice or unlist something the user already sells. Use when they want to raise, lower or change a price, make a tool free, pause selling it, or take it off the market. Requires the api_key from register_server.

Input parameters:

- `api_key` (string): Your seller key.
- `is_active` (boolean): Set false to stop selling this tool.
- `price_usd` (number): New price per call in USD. Minimum 0.01.
- `tool_name` (string, required): Exact name of the tool to update.

### `get_earnings` (~85 tokens)

Report how much the user has earned selling their tools. Use when they ask about sales, revenue, income, how much they made, how many calls were paid, or which tool sells best. Returns paid calls, gross revenue, commission and net revenue, broken down per tool. Requires the api_key from register_server.

Input parameters:

- `api_key` (string): Your seller key.

### `get_my_listing` (~84 tokens)

Review what the user currently has for sale. Use when they ask what they are selling, what their prices are, where their money goes, or want to check their listing before changing it. Returns the proxy URL, payout destination, commission rate and every listed tool with its price. Requires the api_key from register_server.

Input parameters:

- `api_key` (string): Your seller key.

### `verify_ownership` (~100 tokens)

Prove the user owns the server they listed, earning a trusted badge in the marketplace. Use after they have published their verification token at /.well-known/paygate-verify on the server's domain. PayGate fetches that URL and confirms the token matches. Verified sellers can be filtered for by buyers, so this directly increases how often their tools get chosen. Requires the api_key from register_server.

Input parameters:

- `api_key` (string): Your seller key.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/geoacpfilho-paygate-monetize-monetization-x402/paygate-mcp#diagnostics

## Score history

- 2026-08-20: 62
- 2026-08-19: 62
- 2026-08-18: 61
- 2026-08-17: 61
- 2026-08-16: 60
- 2026-08-15: 60
- 2026-08-14: 59

## Links

- Remote endpoint: https://paygate-mcp.rendercriativo.workers.dev/mcp
- Repository: https://github.com/geoacpfilho/paygate-mcp
- Website: https://paygate-mcp.rendercriativo.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/geoacpfilho-paygate-monetize-monetization-x402/paygate-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/geoacpfilho-paygate-monetize-monetization-x402/paygate-mcp.json
- HTML version of this page: https://verifymcp.io/servers/geoacpfilho-paygate-monetize-monetization-x402/paygate-mcp