payclaw Proxy MCP
Server Details
Pay-per-use HTTP proxy. Each proxy_request tool call costs 0.001 USDC on Base Mainnet via x402 protocol. Requires an x402-aware agent to pay automatically.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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.
Tool Definition Quality
Average 3.4/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion between tools. The single tool's purpose is clear and unambiguous.
With only one tool, naming consistency is not applicable; the tool name 'proxy_request' uses a clear verb_noun pattern that aligns with its function.
A single tool for a proxy service feels too minimal. While it covers the basic request forwarding, the lack of auxiliary tools (e.g., configuration, logging) suggests the surface is under-scoped for typical usage.
The tool fulfills its core purpose of forwarding HTTPS requests, but there are notable gaps: no support for different HTTP methods explicitly, no error handling details, and no management capabilities. The surface is borderline adequate.
Available Tools
1 toolproxy_requestBInspect
Forward an HTTP request to any HTTPS API. Costs 0.001 USDC per call via x402 on Base Mainnet.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | HTTPS endpoint to call | |
| body | No | Optional request body (JSON string) | |
| method | No | GET | |
| headers | No | Optional HTTP headers |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so description carries full burden. Mentions forwarding and cost, but does not disclose return behavior (response structure, status codes), error handling, timeout, or authentication specifics. Agent lacks critical behavioral details.
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, immediately front-loaded with the action, then cost. 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 no output schema and no annotations, description should cover expected output and edge cases. It only provides purpose and cost, leaving agent uninformed about return format, errors, and limitations.
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 75% and parameter descriptions are already clear. Description adds no additional semantics to parameters besides cost context which is not parameter-specific.
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?
Clearly states verb+resource: forward HTTP request to any HTTPS API. No siblings so no need for differentiation. Cost information is an added bonus.
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?
No guidance on when to use vs alternatives (none listed), but purpose is broad. Does not provide when-not-to-use or prerequisites beyond HTTPS. Cost information gives some usage context.
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!