A
licenseB
qualityB
maintenanceMachine-readable merchant verification infrastructure for AI shopping agents and agentic commerce systems.
1
3
MIT
x402 Merchant Check
Server Details
Context for agentic buying decisions: merchant trust and price fairness via x402 history.
- 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.
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
A4.6/5.0
Tool DescriptionsA
Average 4.7/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only a single tool, there is no possibility of confusing it with another tool. Its purpose is clearly defined as merchant checking.
Naming Consistency5/5
The tool name 'check_merchant' follows a clear verb_noun pattern, which is internally consistent. Even with one tool, the naming convention is sound.
Tool Count3/5
The server has exactly one tool, which feels thin for a general-purpose server. However, the narrow scope of 'merchant check' makes a single tool acceptable, though borderline.
Completeness5/5
The tool covers the full merchant-checking workflow, including reliability tier, category, and price fairness assessment. There are no obvious missing operations or dead ends for this specific purpose.
Available Tools
1 toolcheck_merchantAInspect
x402 Merchant Check — provides context for agentic buying decisions. Checks merchant reliability and price fairness before purchase, using on-chain x402 transaction history. Returns a tier (trusted/caution/avoid) with reasons, the merchant's category (data_api/compute/content_generation/financial_data/storage/other, null if not yet classified), and — if price is given — a price-fairness assessment compared against other merchants in the same category. $0.01 USDC per query, paid via x402.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| price | No | Quoted price in USD-equivalent, if checking fairness | |
| resource_type | No | Deprecated, accepted but unused — price-fairness now compares against the merchant's own on-chain-derived category automatically, no need to supply this. | |
| merchant_wallet_address | Yes | EVM address of the merchant's receiving wallet |
Tool Definition Quality
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries full responsibility for behavioral disclosure. It transparently reveals a $0.01 USDC per-query cost via x402, details the return values, and explains that resource_type is deprecated and unused. This exceeds typical transparency.
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 concise and well-structured, starting with a clear purpose statement and then adding essential details about outputs, cost, and behavior. Every sentence contributes value without fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description thoroughly describes return values (tier, reasons, category, price-fairness) and covers cost and payment. It also explains the deprecated parameter, making the tool's behavior sufficiently complete for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that supplying price triggers a fairness assessment against other merchants and clarifying that the deprecated category is auto-derived, enhancing parameter understanding.
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 clearly states that the tool checks merchant reliability and price fairness before purchase, using on-chain transaction history. It specifies the exact outputs (tier, category, price-fairness assessment), making its purpose unambiguous and distinct.
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 explicitly frames the tool for 'agentic buying decisions' and 'before purchase', giving clear usage context. It does not state exclusions or alternatives, but with no sibling tools, that is acceptable and the context is strong.
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
- Flicense-qualityBmaintenanceMCP server that scores merchant risk and reputation via a paid check_merchant tool, returning trust tiers and price-fairness readings for shopping agents.
- AlicenseAqualityAmaintenancex402-trust gives AI agents a "check before you pay" layer for the x402 ecosystem.12242MIT
- AlicenseAqualityFmaintenanceCounterparty risk scoring for agentic commerce. Scores wallets, domains, IPs, and companies 0-100 before AI agents transact via x402 micropayments on Base13MIT