MCP Merchant Scout
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_merchantA | Discover a UCP-enabled merchant by fetching their /.well-known/ucp profile. Returns supported capabilities, services, and payment handlers. The merchant is registered for subsequent search and lookup operations. |
| search_productsA | Search for products across all discovered UCP merchants (or a specific one). Returns matching products with prices, availability, and merchant info. Requires at least one merchant to be discovered first. |
| get_productA | Get full details for a specific product from a UCP merchant, including all variants, pricing, media, and availability. |
| compare_productsA | Compare multiple products side-by-side across merchants. Shows pricing, availability, variants, and options for each product. Results are sorted by lowest price. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct primary purpose: discovery, search, detailed lookup, and comparison. There is minor overlap between search_products and compare_products since both return pricing/availability across merchants, but their intents are clear enough to avoid serious misselection.
All tool names follow a consistent verb_noun pattern using snake_case: discover_merchant, search_products, get_product, compare_products. The naming is predictable and clearly indicates the action and target resource.
Four tools is a well-scoped size for a merchant discovery and product research server. Each tool supports a distinct stage of the workflow without unnecessary bloat or redundancy.
The core workflow of discovering merchants, searching products, retrieving details, and comparing across merchants is fully covered. Minor gaps exist, such as no way to list or remove already-discovered merchants, but these do not break the primary use case.