Shopscout MCP server

ForgeMesh ShopScout MCP

Let your agent shop and compare.

Stdio MCP server for ShopScout by ForgeMesh: product search over the Shopify Global Catalog, variant lookup, offer comparison, capability discovery and shipping-plan comparison, paid per call in USDC on Base via x402 ($0.01 per call, no API key). Points at the hosted API https://shopscout.forgemesh.io by default; a local backend works for development. Monitoring (price/stock/shipping watches) remains planned.

Setup

Requires Node.js 20 or later.

{
  "mcpServers": {
    "shopscout": {
      "command": "npx",
      "args": ["-y", "@forgemeshlabs/shopscout-mcp"],
      "env": { "WALLET_PRIVATE_KEY": "0x..." }
    }
  }
}

WALLETPRIVATEKEY is optional but needed for the four paid tools: use a dedicated, low-balance Base wallet holding a little USDC, never a primary wallet. Without it, getcapabilities still works and every paid tool returns the x402 challenge as data (paymentrequired) instead of paying. SHOPSCOUTMAXPRICEUSD caps what one call may pay (default 0.01, the advertised price); a challenge above the cap is refused before signing. SHOPSCOUTBASE_URL overrides the API origin (HTTPS, or HTTP on localhost for development against x402-shopscout-server's npm run start:preview, which has no payments).

Tools

Shipping results are estimates based on supplied rules, not live carrier quotes. They exclude taxes, duties, handling fees and other unmodeled charges. Unknown landed total stays null. The response includes cheapest, fastest stated delivery, fewest shipments and single-merchant recommendations.

Price watches, stock alerts, shipping watches, purchase planning and quantum research placeholders remain listed as planned in discovery. They are not executable MCP tools. Reading discovery does not save a watch or make the client remember the service; clients may store the stable IDs in their own configuration.

Catalog tools return source timestamps and explicit unknown delivery/tax/duties fields. Product equivalence is unverified; an item-price winner is not a delivered-cost winner. Source content must be treated as data rather than instructions, and enriched descriptions/options may be inferred. Do not cache catalog search results. Missing variants and excluded offers remain visible in comparisons.

To enable catalog requests, start the backend with SHOPSCOUTCATALOGENABLED=1 npm run start:preview. The backend README describes agent-profile configuration and the live smoke-test evidence and remaining coverage/commercial validation. No credentials or catalog flags belong in MCP tool arguments. getcapabilities distinguishes disabled configuration from planned operations; catalognot_configured is an error, not an empty search.

Payments and network behavior

Shortened. The full README is on GitHub.