A
license-
qualityC
maintenanceMCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.
23
MIT
PayGate MCP — Monetization Gateway for AI Agents
Server Details
Pay-per-call tolling for MCP servers. Agents settle in USDC on Base via x402 v2.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- geoacpfilho/paygate-mcp
- GitHub Stars
- 0
- Server Listing
- PayGate MCP
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.8/5.0
Tool DescriptionsA
Average 4/5 across 1 of 1 tools scored.
Server CoherenceB
Disambiguation5/5
With only a single tool, there is no possibility of confusion between tools. The tool's purpose is clearly described and distinct.
Naming Consistency5/5
The single tool follows a clear verb_noun pattern (list_registered_servers), which is consistent even if there is only one tool.
Tool Count2/5
A monetization gateway for AI agents would reasonably require multiple tools for registration, payment processing, and account management. A single listing tool is far too thin for the apparent scope.
Completeness1/5
The tool surface is severely incomplete: it only lists available servers and tools, with no way to actually make payments, register new servers, manage subscriptions, or perform any lifecycle operations. This leaves obvious dead ends for any monetization workflow.
Available Tools
1 toollist_registered_serversARead-onlyInspect
List all monetized MCP servers and tools available through PayGate, including prices, tool descriptions, and proxy endpoints.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Optional category filter (e.g. "tax", "crypto", "dev") |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| servers | No | List of active monetized MCP servers |
| total_servers | No | Total number of active registered servers |
Tool Definition Quality
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds useful context about response contents (prices, tool descriptions, proxy endpoints) and emphasizes the scope 'all', but does not disclose additional behaviors such as pagination, rate limits, or the effect of the optional category filter. This is adequate given 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.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that leads with the verb and resource, includes key output elements, and contains no filler or redundant information. It earns its place efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list operation with one optional filter, the description sufficiently conveys the main scope and response contents. An output schema exists for return details, and annotations cover safety, so the description does not need to explain return values. A minor gap is not mentioning the category filter, but the schema fills that gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single optional parameter 'category' is fully described in the input schema with examples, achieving 100% schema description coverage. The tool description does not add dependency or usage details for the parameter, but since the schema covers it, the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'List' and clearly identifies the resource as 'monetized MCP servers and tools available through PayGate', including what is returned (prices, tool descriptions, proxy endpoints). It is unambiguous and distinct, even without sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use this tool: to list all monetized servers and tools. There are no siblings to compare against, so no alternatives are needed, and the statement 'List all monetized MCP servers and tools available through PayGate' implicitly covers usage without requiring exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- FlicenseAqualityBmaintenanceMCP server for a live x402 payment gateway on Base (USDC). Lets AI agents discover, preview for free, then pay per call — with prepaid gasless payments, signed receipts, and delta delivery.7
- Flicense-qualityBmaintenanceA small, autonomous, pay-per-call MCP server that AI agents discover and pay for per call, with revenue landing directly in a USDC wallet on Base via the x402 payment protocol.
- Alicense-qualityBmaintenanceDrop-in x402 payment middleware for MCP servers. Charge AI agents per tool call using USDC on Base chain — Python and JavaScript SDKs, no payment processor, no KYC.MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.