Monetization gateway for MCP servers. Agents call a tool, receive an x402 v2 payment challenge, sign a USDC transfer on Base, and get the result. Payment is verified before the tool runs and settled only after it returns, so failed calls are never charged. Discovery and tool listing are free.
Scored across 6 tools
Each tool has a clearly distinct purpose: earnings reporting, listing review, marketplace browsing, server registration, pricing changes, and ownership verification. There is no overlap between these operations, so an agent will not confuse them.
All tool names follow a consistent verb_noun pattern: get_earnings, get_my_listing, list_registered_servers, register_server, set_tool_price, verify_ownership. The style is uniform and predictable, making it easy to infer what each tool does.
Six tools is well-scoped for a payment and marketplace server. Each tool earns its place by covering a distinct aspect of the seller workflow without unnecessary bloat.
The tool surface covers the full lifecycle for sellers: registering a server, managing prices, viewing earnings, reviewing listing, and verifying ownership. There are no obvious dead ends or missing core operations for the stated purpose.
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 | Required | Description | Default |
|---|---|---|---|
| api_key | No | Your seller key. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint and idempotentHint, and the description adds context beyond that by detailing the output (paid calls, gross revenue, commission, net revenue per tool) and noting the api_key must come from register_server. This is useful behavioral information without contradicting the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the main purpose, and every sentence provides actionable value: what it reports, when to use it, and what it returns. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (1 parameter, no output schema, read-only semantics), the description is complete: it covers purpose, usage triggers, return contents, and required key provenance. No additional context is necessary for an agent to select and invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already covers the single parameter with 100% coverage ('Your seller key'), so the baseline is 3. The description adds meaning by specifying the api_key is specifically from register_server, which is a helpful cross-reference beyond the schema's generic description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'Report how much the user has earned selling their tools.' It clearly distinguishes itself from siblings by focusing on earnings and explicitly lists the returned metrics (paid calls, gross revenue, commission, net revenue).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly lists when to use this tool (when they ask about sales, revenue, income, how much they made, how many calls were paid, or which tool sells best), providing clear usage context. It does not explicitly mention when not to use or name alternatives, so it does not fully meet the 'explicit alternatives' bar for a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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 | Required | Description | Default |
|---|---|---|---|
| api_key | No | Your seller key. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, so the safe-read nature is covered. The description adds context by outlining the exact return fields (proxy URL, payout destination, commission rate, listed tools with prices) and the prerequisite api_key from register_server. This is meaningful behavioral transparency beyond the annotations, though it doesn't cover errors or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact, using three sentences to cover purpose, use cases, return contents, and a prerequisite. It is front-loaded with the primary action and avoids redundant phrasing. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With a single parameter and no output schema, the description adequately explains the tool's behavior and returns. It covers the key use cases and the required authentication context. The description is self-sufficient for an agent to select and invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes api_key as 'Your seller key' (100% coverage). The description enriches this by specifying that the key comes from register_server, which is a helpful source detail. Since the baseline for full schema coverage is 3, this additional context warrants a 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as retrieving the user's current sales listing ('Review what the user currently has for sale'). It enumerates specific use cases and distinguishes it from sibling tools like set_tool_price by positioning it as a pre-change check. The verb+resource combination is specific and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use the tool: when the user asks about what they're selling, prices, money destination, or before changing a listing. It implies not to use it for making changes, which differentiates from set_tool_price. However, it doesn't name sibling alternatives explicitly or state exclusions, so a 4 is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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 | Required | Description | Default |
|---|---|---|---|
| search | No | Case-insensitive match against tool names, descriptions and seller names. | |
| max_price_usd | No | Only return tools priced at or below this amount per call. | |
| verified_only | No | Return only sellers who proved they own the server they sell. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint. The description adds useful context: browsing is free, requires no key, and returns price and endpoint for each tool. There is no contradiction, and the additional details go beyond the annotations without overexplaining.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is four sentences, each earning its place. The primary purpose is front-loaded, followed by use cases and return details. No fluff, no repetition, and it is optimally sized for the tool's simplicity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite lacking an output schema, the description explicitly mentions what is returned (price per call and endpoint) and access requirements (free, no key). The tool is a simple list with three optional filters already documented in the schema. This is sufficient for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All three parameters (search, max_price_usd, verified_only) have schema descriptions, giving 100% coverage. The description does not add extra meaning to these parameters beyond what the schema already provides, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb+resource ('Find a paid tool' / 'Returns every tool on the market'), explains what it provides (price per call and endpoint), and differentiates from siblings focused on earnings, listings, and registration. This is unambiguous and immediately tells the agent what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use: when the user needs a capability you lack and is willing to pay, or asks about available paid tools/APIs. It also notes that browsing is free and needs no key. However, it does not mention when not to use it or point to alternatives like get_my_listing or register_server, so it lacks explicit exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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 | Required | Description | Default |
|---|---|---|---|
| name | Yes | Display name of the service in the marketplace. | |
| No | Optional contact address. | ||
| wallet_address | No | EVM address that receives USDC on Base. Required unless stripe_account_id is given. | |
| default_price_usd | No | Price per call applied to every imported tool. Defaults to 0.02. | |
| stripe_account_id | No | Stripe Connect account (acct_...) to receive fiat instead. Only for tools priced at $0.50 or above. | |
| target_server_url | Yes | Public HTTPS URL of the MCP server to monetize, e.g. https://example.com/mcp |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses critical behavioral details beyond the annotations: the non-custodial payment model (buyers pay directly on-chain, no commission), the fact that the server is never modified and needs no payment code, and that the api_key is shown only once and must be saved. These are essential operational traits not captured by readOnlyHint, openWorldHint, idempotentHint, or destructiveHint.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a compact paragraph, front-loaded with the core purpose and then covering usage context, payment model, server requirements, and return values. Each sentence earns its place; the list of synonyms is slightly redundant but reinforces the trigger conditions, and there is no filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given there is no output schema, the description adequately explains the return values (proxy URL and once-only secret api_key), prerequisites (HTTPS and tools/list), and the critical warning to save the key. It also covers side effects (server never modified) and the payment model, making it sufficient for accurate invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds value by specifying that target_server_url 'must be publicly reachable over HTTPS and answer tools/list' — a requirement not present in the schema. It also contextualizes wallet_address within the direct on-chain payment model, though most parameter semantics remain in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description begins with 'Start charging for an MCP server the user owns' — a specific verb and resource. It then enumerates synonyms (monetize, sell, charge, etc.) and clearly distinguishes this from sibling tools like get_earnings, list_registered_servers, or set_tool_price by focusing on the act of registration/monetization.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit when-to-use guidance: 'Use when they want to monetize, sell, charge for, get paid for...' It also adds a prerequisite (the user owns the server) and positions the tool as the entry point by stating 'every other seller tool needs it.' This clearly differentiates it from read-only or update siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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 | Required | Description | Default |
|---|---|---|---|
| api_key | No | Your seller key. | |
| is_active | No | Set false to stop selling this tool. | |
| price_usd | No | New price per call in USD. Minimum 0.01. | |
| tool_name | Yes | Exact name of the tool to update. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds the api_key requirement and clarifies the unlist action, but it introduces an inconsistency: it says 'make a tool free' while the schema states price_usd minimum is 0.01, so the claimed behavior cannot be achieved as described. This lowers transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the primary action, followed by clear use cases and a requirement. Every sentence earns its place with no fluff or repetition of schema details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is a simple mutation with good annotations and high schema coverage. The description covers the main use cases and prerequisite but leaves a behavioral gap around the 'make free' vs. minimum price contradiction, and does not mention what happens on unlist (e.g., whether is_active=false is required). It is adequate but not fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds context about api_key origin ('from register_server') but does not add meaningful semantics for other parameters beyond the schema. In fact, it conflicts with price_usd's minimum via the 'make a tool free' phrase.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with specific verbs and resource: 'Reprice or unlist something the user already sells.' It enumerates concrete use cases (raise/lower price, make free, pause selling, take off market) which fully distinguishes it from sibling read-only tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use the tool ('Use when they want to raise, lower or change a price...') and mentions a prerequisite (requires api_key from register_server). It does not explicitly name alternatives or exclusions, but the context is clear given the sibling list, so it misses the top level only by not saying 'instead of X'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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 | Required | Description | Default |
|---|---|---|---|
| api_key | No | Your seller key. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate idempotent and non-destructive behavior. The description adds the specific workflow (PayGate fetches the URL, confirms the token, awards a badge) and the benefit (increased visibility). It doesn't overstate or contradict annotations, and provides useful context beyond the structured fields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three tight sentences, front-loaded with the core purpose, followed by the procedure and value. Every sentence contributes new information, with no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple single-parameter tool, the description covers the workflow, prerequisites, and expected outcome. It does not mention error conditions or the response format, but the absence of an output schema and the low complexity make this acceptable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The sole parameter (api_key) is fully described in the schema, and the description adds meaningful provenance by specifying it comes from register_server. This clarifies which key to use and why, which the schema alone does not convey.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Prove') and resource ('ownership of the server they listed'), clearly distinguishing it from sibling tools like get_earnings or register_server. It also explains the outcome (trusted badge) and the mechanism, making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use the tool ('Use after they have published their verification token...') and notes a prerequisite (requires the api_key from register_server). It does not explicitly mention alternatives or when not to use it, but the context makes it clear this is the only verification tool among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
list_registered_servers1 field changedInput schema / properties / verified_onlyAdded value: +{
+ "description": "Return only sellers who proved they own the server they sell.",
+ "type": "boolean"
+}verify_ownershipget_earningsget_my_listinglist_registered_servers4 fields changedInput schema / properties / categoryRemoved value: -{
- "description": "Optional category filter (e.g. \"tax\", \"crypto\", \"dev\")",
- "type": "string"
-}Input schema / properties / max_price_usdAdded value: +{
+ "description": "Only return tools priced at or below this amount per call.",
+ "type": "number"
+}Input schema / properties / searchAdded value: +{
+ "description": "Case-insensitive match against tool names, descriptions and seller names.",
+ "type": "string"
+}Output schema / (root)Previous value: -{
- "properties": {
- "servers": {
- "description": "List of active monetized MCP servers",
- "items": {
- "properties": {
- "developer_name": {
- "description": "Name of the developer or service",
- "type": "string"
- },
- "proxy_mcp_url": {
- "description": "Proxy URL for agents to access tools",
- "type": "string"
- },
- "tools": {
- "items": {
- "properties": {
- "description": {
- "description": "Description of tool capabilities",
- "type": "string"
- },
- "name": {
- "description": "Name of the tool",
- "type": "string"
- },
- "price_usd": {
- "description": "Price per call in USD",
- "type": "string"
- }
- },
- "type": "object"
- },
- "type": "array"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "total_servers": {
- "description": "Total number of active registered servers",
- "type": "number"
- }
- },
- "type": "object"
-}New value: +nullregister_serverset_tool_pricelist_registered_servers
Add one secure layer between your agents and this server.