Back to Browse

Shopdata MCP Server

Developer ToolsModerate6.1MCP RegistryLocal
Free

Server data from the Official MCP Registry

Amazon data as JSON: product details, reviews, keyword search, seller profiles and catalogues.

About

Amazon data as JSON: product details, reviews, keyword search, seller profiles and catalogues.

Security Report

6.1
Moderate6.1Moderate Risk

shopdata is a straightforward forwarding client for the hosted HasData Amazon MCP endpoint. It has no shell execution, filesystem access, or hardcoded secrets, and its only network destination is the pinned upstream URL. The main concerns are minor: the optional API key is sent to whatever endpoint HASDATA_AMAZON_MCP_URL points to, and the package's npm scope differs from its GitHub owner. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

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

Some servers take additional arguments. See the repository for details.

Documentation

View on GitHub

From the project's GitHub README.

shopdata

shopdata is a small local bridge to the hosted HasData Amazon MCP server, which returns public Amazon data as JSON. Give it an ASIN and it fetches that product's details or its customer reviews; give it a keyword and it runs a search on a chosen Amazon domain; give it a seller ID and it returns the seller's public storefront profile or the catalogue that seller offers.

The bridge keeps no Amazon data of its own. It serves the upstream server's tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning the result untouched. The captured surface is read-only: there is no purchase, checkout, or account tool in it.

Tools

  • hasdata_amazon_product_getProductDetails — fetch one product page by ASIN. Required: asin. Optional: domain, language, deliveryZip, shippingLocation, otherSellers (also collect the other-sellers offers block).
  • hasdata_amazon_reviews_getProductReviews — paginated customer reviews for an ASIN. Required: asin. Optional: domain, language, page, searchTerm, reviewerType, stars, format, mediaType, sortBy.
  • hasdata_amazon_search_getSearchResults — keyword search on a chosen Amazon domain. Required: q. Optional: domain, language, page, deliveryZip, shippingLocation, sortBy.
  • hasdata_amazon_seller_getSellerDetails — public storefront profile for a seller. Required: sellerId. Optional: domain, language.
  • hasdata_amazon_seller_products_getSellerProducts — paginated catalogue offered by a seller. Required: sellerId. Optional: domain, language, page.

Configuration

  • HASDATA_AMAZON_MCP_URL (optional) — override the upstream endpoint. Defaults to https://mcp.hasdata.com/mcp?apis=amazon, query string included. (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 with the caller's own HasData API key. When it is not set, no key header is sent, and no Authorization header is sent in either case. (The env and header names 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 with the upstream: a JSON-RPC initialize request (protocolVersion 2025-03-26, clientInfo name shopdata), 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 shopdata error: (this rendering is this rebuild's own labelled reconstruction).

CLI

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

npx @reneturcios/shopdata hasdata_amazon_product_getProductDetails '{"asin":"B07FZ8S74R"}'
npx @reneturcios/shopdata hasdata_amazon_search_getSearchResults '{"q":"noise cancelling headphones","sortBy":"priceLowToHigh"}'
npx @reneturcios/shopdata --version

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

MCP server

npx -y @reneturcios/shopdata mcp

MCP client config:

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

Docker

docker run -i ghcr.io/cloudcorprecords/shopdata
docker run --rm ghcr.io/cloudcorprecords/shopdata --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.

Reviews

No reviews yet

Be the first to review this server!