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.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
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.
Average 4.1/5 across 1 of 1 tools scored.
There is only one tool, so there is no possibility of confusing it with another. The purpose of listing registered servers is clear and distinct.
The single tool name follows a clear verb_noun pattern ('list_registered_servers'), which is consistent and descriptive. With only one tool, there is no inconsistency to penalize.
The server appears to be a payment gateway for MCP servers, yet it only offers a listing function. A gateway would reasonably need tools for purchasing, access, or managing subscriptions, so one tool is too few for the apparent scope.
The tool only lists servers with metadata, but provides no way to actually use or pay for the listed services. This is a significant gap that prevents an agent from completing common workflows such as subscribing to or accessing a monetized server.
list_registered_serversAList all monetized MCP servers and tools available through PayGate, including prices, tool descriptions, and proxy endpoints.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Optional category filter (e.g. "tax", "crypto", "dev") |
| Name | Required | Description |
|---|---|---|
| servers | No | List of active monetized MCP servers |
| total_servers | No | Total number of active registered servers |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already communicates that this is a safe read operation. The description adds detail about the return content (prices, tool descriptions, proxy endpoints), which is useful but does not disclose deeper behavioral aspects like pagination, rate limits, or authentication requirements.
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 single sentence that front-loads the verb and resource, and includes all essential information without redundancy. Every word contributes to understanding the tool.
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?
This is a simple read-only list tool with one optional filter and an output schema already present. The description provides sufficient context about what the tool lists and what is included, without needing extra elaboration.
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 input schema fully documents the single optional 'category' parameter with a description and examples, so schema coverage is 100%. The description does not add any further parameter-specific meaning, and the baseline score of 3 applies.
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 the specific verb 'List' and identifies the exact resource: monetized MCP servers and tools available through PayGate. It further specifies the output includes prices, tool descriptions, and proxy endpoints, making the tool's scope unmistakable.
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 clearly implies the tool is for discovering available monetized servers and tools, but does not explicitly state when to use it versus alternatives. Since there are no sibling tools, the lack of explicit when-not guidance is acceptable.
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.
No comments yet. Be the first to start the discussion!
