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.
Available components
Last scanned (21 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 4 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 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
- 13 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
- 15 Aug 26 0
- Schema quality: 1046 → 1165 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.2.0 → 0.3.1 functional
- New tool “verify_ownership” functional
- “list_registered_servers” added an optional parameter “verified_only” cosmetic
- 14 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://paygate-mcp.rendercriativo.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rendercriativo.workers.dev | CN=WE1,O=Google Trust Services,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 922a81f5e5c2f33d0e575376c2509d85 |
| SANs: rendercriativo.workers.dev, *.rendercriativo.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of paygate-mcp.rendercriativo.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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://paygate-mcp.rendercriativo.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://paygate-mcp.rendercriativo.workers.dev/mcp | Served over HTTP | 200 |
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 →
get_earnings ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your seller key. |
No output schema declared.
No examples provided.
get_my_listing ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your seller key. |
No output schema declared.
No examples provided.
list_registered_servers ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
register_server ~271
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.
| Name | Type | Req | Description |
|---|---|---|---|
| default_price_usd | number | – | Price per call applied to every imported tool. Defaults to 0.02. |
| string | – | Optional contact address. | |
| name | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
set_tool_price ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Exact name of the tool to update. |
No output schema declared.
No examples provided.
verify_ownership ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your seller key. |
No output schema declared.
No examples provided.
How do I install the PayGate MCP — Monetization Gateway for AI Agents server?
PayGate MCP — Monetization Gateway for AI Agents is a hosted endpoint at https://paygate-mcp.rendercriativo.workers.dev/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 · paygate-mcp.rendercriativo.workers.dev
claude mcp add --transport http geoacpfilho-paygate-monetize-monetization-x402 'https://paygate-mcp.rendercriativo.workers.dev/mcp'
What is the PayGate MCP — Monetization Gateway for AI Agents server?
PayGate MCP — Monetization Gateway for AI Agents is listed in the public MCP registry as io.github.geoacpfilho/paygate-monetize-monetization-x402. Monetize any MCP server: x402 paywall, pay-per-call billing in USDC on Base, agent marketplace. This page covers its hosted endpoint (https://paygate-mcp.rendercriativo.workers.dev/mcp).
Is the PayGate MCP — Monetization Gateway for AI Agents server safe to use?
PayGate MCP — Monetization Gateway for AI Agents scores 82 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 PayGate MCP — Monetization Gateway for AI Agents server expose?
PayGate MCP — Monetization Gateway for AI Agents exposes 6 tools: list_registered_servers, register_server, set_tool_price, get_earnings, get_my_listing, verify_ownership. Their descriptions and schemas cost roughly 798 tokens of context every time the server is loaded.
Does the PayGate MCP — Monetization Gateway for AI Agents server require authentication?
No. We connected to PayGate MCP — Monetization Gateway for AI Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PayGate MCP — Monetization Gateway for AI Agents server still maintained?
PayGate MCP — Monetization Gateway for AI Agents is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.