
Martdata
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 11, 2026
Walmart data as JSON: product details, customer reviews, and storefront search with filters.
Overview
Martdata's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Martdata in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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, byitemIdor byurl(the URL wins when both are given). Optional:domain(walmart.com/walmart.ca),language(en/es/fr), andotherOffersto 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:itemIdandurlare alternatives for each other.hasdata_walmart_reviews_getWalmartReviews— the customer reviews of one product, ten a page, byitemIdorurl. 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, andverifiedPurchasesOnly. 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 keywordq, or browse a category withcatId, or scrape a full search URL viaurl. Optional:domain,language,sort(best match, price low-to-high or high-to-low, bestseller, highly rated, new arrivals),page,minPriceandmaxPrice,deliveryType(shipping/pickup), andfacetnarrowing inname:valueform. Returns the product list with prices, ratings, sellers and fulfillment details, plus the facets block and pagination.
Configuration
HASDATA_WALMART_MCP_URL(optional) — override the upstream endpoint. Defaults tohttps://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 anx-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:
Exit codes: 0 on success, 1 on an isError
result, 2 on a usage error.
MCP server
MCP client config:
Docker
The container's default command is mcp, so the first
form is a stdio MCP server; any other arguments reach
the CLI normally.
Development
The test suite runs entirely against a stubbed JSON-RPC upstream — no live network calls.
License
MIT — see LICENSE.
Source: README.md at commit 64a7526
Tools
0Version history
1- v0.1.0LatestNov 11, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts