Skip to main content
Glama
GoBuy Product Trust MCP Server

GoBuy Product Trust MCP Server

Official

GoBuy Product Trust MCP Server

A public, read-only MCP server that gives AI agents GoBuy marketplace-evidence scores — and the reference evaluator for the GPV-1 Pre-Purchase Verification Specification.

Public endpoint: https://mcp.gobuy.ai/mcp — keyless, no authentication, read-only. Service statistics: https://mcp.gobuy.ai/stats.

Tools (5)

  • check_product_trust {retailer, product_id} — inspect one Amazon, Walmart, Target, or Best Buy listing: Evidence Score (0-100), verdict, observed/missing signals, freshness. This is the GPV-1 gate evaluator (score >= 55 PASS - 35-54 FLAG - < 35 or not-indexed BLOCK).

  • compare_products {products: [...]} — inspect and rank 2-20 listings by Evidence Score.

  • analyze_reviews — per-review forensics: review integrity score, adjusted rating, suspicious-review flags, Verified Purchase checks.

  • check_store_score {domain} — GoBuy Store Score for any storefront (Shopify and others): agent-readiness plus trust signals, tiers A-D.

  • scan_store {domain} — on-demand deep storefront scan.

Example:

{ "retailer": "amazon", "product_id": "B0BXYCS74H" }

Related MCP server: Shop Search MCP

GPV-1 — Pre-Purchase Verification

This server's check_product_trust is the reference evaluator for GPV-1, the open pre-purchase verification specification: eight rules (R1-R8) that must all be true before an agent proceeds to checkout. Machine-readable ruleset: docs.gobuy.ai/standard/v1.json. Reference integration: verify-then-checkout (Next.js boilerplate - a secured shopping agent in 5 minutes).

Evidence disclaimer

Evidence Scores describe available marketplace records, not product quality, safety, value, suitability, seller legitimacy, or a purchase recommendation. Retailers do not endorse GoBuy.

Client configuration

Any MCP Client

{ "mcpServers": { "gobuy-product-trust": { "url": "https://mcp.gobuy.ai/mcp" } } }

Claude Desktop

{ "mcpServers": { "gobuy-product-trust": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.gobuy.ai/mcp"] } } }

Inspector

npx @modelcontextprotocol/inspector -> Streamable HTTP -> https://mcp.gobuy.ai/mcp -> list tools -> call check_product_trust.

Transports

  • stdio (for mcp-proxy bridges, e.g. Glama deploys): set MCP_TRANSPORT=stdio. The server speaks MCP over stdin/stdout; stdout carries only JSON-RPC, all logs go to stderr.

  • HTTP (default): listens on PORT (default 3000), endpoint /mcp, health at GET /mcp, stats at GET /stats.

Limits

No client authentication required. Rate limited per IP: 60/minute, 1,000/day (429 + Retry-After). Everything is free within rate limits; an optional free API key raises them.

License

MIT

Changelog

  • 2026-10-14: stdio transport (MCP_TRANSPORT=stdio) for mcp-proxy deployments; stdout reserved for JSON-RPC, logs to stderr.

Available Tools

2 tools
check_product_trustA
Read-only

Return the indexed 0–100 marketplace-evidence score and complete available signal breakdown for one retailer listing.

Inputs: retailer (required), product_id (required).

compare_productsA
Read-only

Compare 2–20 retailer listings and rank them by marketplace-evidence score. This is not purchase advice.

Inputs: products (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers