GoBuy Product Trust MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Local HTTP port. | 3000 |
| INTERNAL_API_URL | Yes | The GoBuy API origin URL. |
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 |
|---|---|
| check_product_trustA | Return the indexed 0–100 marketplace-evidence score and complete available signal breakdown for one retailer listing. |
| compare_productsA | Compare 2–20 retailer listings and rank them by marketplace-evidence score. This is not purchase advice. |
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 2 tools
The two tools have clearly distinct purposes: check_product_trust scores a single retailer listing, while compare_products ranks 2-20 listings against each other. The descriptions make the singular-vs-multi scope explicit, so an agent cannot reasonably confuse them.
Both names follow the same predictable verb_noun snake_case pattern (check_product_trust, compare_products). The leading verbs (check, compare) also accurately signal the differing action.
Two tools is on the thin side, but the domain (scoring and comparing retailer listings) is narrow enough that each tool earns its place. A slightly broader surface (e.g. batch or signal-discovery) would round it out.
The core workflow of inspecting one listing and comparing several is covered, which matches the stated purpose. Minor gaps exist: no batch check for a list of single products, no operation to discover or list available signals/retailers independently.