martdata

martdata is a small local bridge to the hosted HasData Walmart MCP server, which returns Walmart storefront data as JSON. It can pull one product page in full from an item id or URL, page through that product's customer reviews, and run keyword or category searches across a storefront with price, fulfillment and sort filters.

The bridge holds no product data of its own. It answers the tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning whatever comes back untouched. The captured surface is three read-only fetches over public storefront data: there is no cart, checkout, order or payment tool in it, and no individual contact data is returned.

Tools

• hasdata_walmart_product_getWalmartProduct — fetch one Walmart product in full, by itemId or by url (the URL wins when both are given). Optional: domain (walmart.com / walmart.ca), language (en / es / fr), and otherOffers to also collect competing sellers' offers. Returns title, brand, price and availability, the buy-box seller, ratings, variants, fulfillment details and the other-sellers block. No argument is marked required in the captured schema: itemId and url are alternatives for each other.

• hasdata_walmart_reviews_getWalmartReviews — the customer reviews of one product, ten a page, by itemId or url. Optional: domain, language, page, sort (most relevant, most recent, most helpful, highest or lowest rated, oldest), rating (one star value), aspectId (one frequent-mention topic), condition, and verifiedPurchasesOnly. Returns each review with its rating, text, author and vote counts, plus the item's rating breakdown, AI review summary, per-aspect scores and the filters block naming the values later calls can filter by.

• hasdata_walmart_search_getSearchResults — search a storefront by keyword q, or browse a category with catId, or scrape a full search URL via url. Optional: domain, language, sort (best match, price low-to-high or high-to-low, bestseller, highly rated, new arrivals), page, minPrice and maxPrice, deliveryType (shipping / pickup), and facet narrowing in name:value form. Returns the product list with prices, ratings, sellers and fulfillment details, plus the facets block and pagination.

Related MCP server: Crawdar Business Research

Configuration

• HASDATA_WALMART_MCP_URL (optional) — override the upstream endpoint. Defaults to https://mcp.hasdata.com/mcp?apis=walmart. (The override hook is this rebuild's own labelled reconstruction.)

• HASDATA_API_KEY (optional) — when set, every upstream request carries an x-api-key: <key> header, for the caller's own HasData API key. When it is not set, no key header is sent. (The header name and the env name are pinned by the original's registry record; forwarding the key from this env var is a labelled reconstruction — the original surface was captured keyless.)

Forwarding mechanics

On the first tool call the client opens a streamable HTTP session upstream: a JSON-RPC initialize request (protocolVersion 2025-03-26, clientInfo name martdata), then a notifications/initialized notification, then the tools/call request carrying the caller's arguments unchanged. When the upstream answers initialize with an Mcp-Session-Id header, that value rides on every later request of the session, which is reused for the life of the process. Replies may arrive as plain JSON or as server-sent events; both are read.

Successful upstream results pass through verbatim, including any isError flag the upstream sets. Failures — a JSON-RPC error, a non-2xx status, an unreadable response, or a request that cannot be completed — come back as an isError result whose text starts with martdata error: (this rendering is this rebuild's own labelled reconstruction).

CLI

Each tool is also a subcommand taking one JSON argument string:

npx @reneturcios/martdata hasdata_walmart_product_getWalmartProduct '{"itemId":"14977205582"}'
npx @reneturcios/martdata hasdata_walmart_reviews_getWalmartReviews '{"itemId":"14977205582","sort":"mostRecent"}'
npx @reneturcios/martdata hasdata_walmart_search_getSearchResults '{"q":"coffee maker","maxPrice":90}'
npx @reneturcios/martdata --version

Exit codes: 0 on success, 1 on an isError result, 2 on a usage error.

MCP server

npx -y @reneturcios/martdata mcp

MCP client config:

{
  "mcpServers": {
    "martdata": {
      "command": "npx",
      "args": ["-y", "@reneturcios/martdata", "mcp"]
    }
  }
}

Docker

docker run -i ghcr.io/cloudcorprecords/martdata
docker run --rm ghcr.io/cloudcorprecords/martdata --version

The container's default command is mcp, so the first form is a stdio MCP server; any other arguments reach the CLI normally.

Development

npm install
npm run build
npm test
npm run dev

The test suite runs entirely against a stubbed JSON-RPC upstream — no live network calls.

License

MIT — see LICENSE.