io.github.CloudCorpRecords/shopdata
NPM · @RENETURCIOS/SHOPDATA · 2 COMPONENTS
Amazon data as JSON: product details, reviews, keyword search, seller profiles and catalogues.
Available components
Last scanned (14 hours ago)
Scores higher than 46% of npm servers
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1260 tokens (~252/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 10 Nov 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@reneturcios/shopdata@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
hasdata_amazon_product_getProductDetails amazon_product: GET / ~301
Get Amazon Product Details Fetches a single Amazon product page by ASIN on a chosen Amazon domain (amazon.com, .co.uk, .de, .jp, etc.). Returns title, brand, current/list/deal price, currency, availability, Buy Box seller, Prime eligibility, bullet points, A+ description, rating and review count, images, category breadcrumbs, variants/sibling ASINs, and the other-sellers offers block (when otherSellers=true), plus delivery-zone-aware pricing when a shipping zip/location is set. Use for product research agents, price/stock monitoring, catalog enrichment, listing QA, Buy Box tracking, and cross-locale competitive analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | yes | The Amazon Standard Identification Number (ASIN) of the product. |
| deliveryZip | string | – | Postal code of the delivery location. |
| domain | string | – | Amazon domain to use. Default is www.amazon.com. |
| language | string | – | Optional Amazon language code. Supported values depend on the selected domain. |
| otherSellers | boolean | – | Also collect the offers of other sellers competing for this item. This takes an extra request to Amazon and costs 5 credits on top of the base. Default is false. |
| shippingLocation | string | – | The two-letter country code to define the country of the delivery address. Provide one exact documented value (238 allowed), e.g. `AU`, `CA`. |
No output schema declared.
No examples provided.
hasdata_amazon_reviews_getProductReviews amazon_reviews: GET / ~311
Get Amazon Product Reviews Paginated fetch of customer reviews for an Amazon ASIN with filters for star rating (1-5, positive, critical), reviewer type (all vs verified purchase), media-only reviews, current-variant vs all-formats, keyword search, and sort (helpful/recent). Returns per-review title, body, star rating, author name and profile, review date, helpful-vote count, variant/format attributes, and attached media URLs, plus aggregate rating histogram. Use for voice-of-customer analysis, sentiment and theme extraction, feature-request mining, competitor review benchmarking, and feeding review-summarization or Q&A agents.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | yes | The Amazon Standard Identification Number (ASIN) of the product. |
| domain | string | – | Amazon domain to use. Default is www.amazon.com. |
| format | string | – | The format type to filter reviews. Include reviews of any product format/variant or specifically to the current format/variant. |
| language | string | – | Optional Amazon language code. Supported values depend on the selected domain. |
| mediaType | string | – | The media type to filter reviews. |
| page | number | – | The page number to retrieve. |
| reviewerType | string | – | The type of reviewers to filter. |
| searchTerm | string | – | A term to search within the reviews. |
| sortBy | string | – | The criterion to sort reviews. |
| stars | string | – | The star ratings to filter reviews. |
No output schema declared.
No examples provided.
hasdata_amazon_search_getSearchResults amazon_search: GET / ~284
Get Amazon Search Results Runs a keyword search on a chosen Amazon domain with pagination, delivery zip/location scoping, and sort order (featured, price low-to-high, price high-to-low, avg-customer-review, newest). Returns the organic results list with ASIN, title, thumbnail, product URL, price and list price, currency, star rating, review count, Prime/sponsored flags, and position. Use for SERP monitoring, keyword/share-of-shelf tracking, competitor discovery, ASIN harvesting to feed downstream product/reviews endpoints, and building product-research or price-comparison agents.
| Name | Type | Req | Description |
|---|---|---|---|
| deliveryZip | string | – | Postal code of the delivery location. |
| domain | string | – | Amazon domain to use. Default is www.amazon.com. |
| language | string | – | Optional Amazon language code. Supported values depend on the selected domain. |
| page | number | – | Page number for pagination (e.g., 1 for the first page, 2 for the second page, etc.). |
| q | string | yes | The search term for which to get the search results. |
| shippingLocation | string | – | The two-letter country code to define the country of the delivery address. Provide one exact documented value (238 allowed), e.g. `AU`, `CA`. |
| sortBy | string | – | Parameter used for sorting results |
No output schema declared.
No examples provided.
hasdata_amazon_seller_getSellerDetails amazon_seller: GET / ~168
Get Amazon Seller Details Fetches the public storefront profile for an Amazon seller by sellerId on the chosen domain/language. Returns business name, seller logo, About-this-seller text, overall feedback rating and lifetime/12-month/90-day/30-day rating breakdown, feedback count, business address and contact details, and customer service info. Use for seller due-diligence and vetting, counterfeit/brand-protection workflows, MAP-violation investigations, building seller leaderboards, and enriching marketplace seller directories.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Amazon domain to use. Default is www.amazon.com. |
| language | string | – | Optional Amazon language code. Supported values depend on the selected domain. |
| sellerId | string | yes | The unique Amazon seller ID. |
No output schema declared.
No examples provided.
hasdata_amazon_seller_products_getSellerProducts amazon_seller_products: GET / ~196
Get Amazon Seller Products Paginated listing of the storefront catalog offered by a given Amazon sellerId on the chosen domain. Returns each product row with ASIN, title, image, product URL, price and list price, currency, star rating, and review count. Use to map a competitor's or 3P seller's full assortment, detect new SKU launches, build brand-protection watchlists, drive price-intelligence pipelines, and seed per-ASIN deep-dives against the product and reviews endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Amazon domain to use. Default is www.amazon.com. |
| language | string | – | Optional Amazon language code. Supported values depend on the selected domain. |
| page | number | – | Page number for pagination (e.g., 1 for the first page, 2 for the second page, etc.). |
| sellerId | string | yes | The unique Amazon seller ID. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/shopdata MCP server?
io.github.CloudCorpRecords/shopdata runs locally as an npm package, launched with npx -y @reneturcios/shopdata mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/shopdata
claude mcp add cloudcorprecords-shopdata -- npx -y @reneturcios/shopdata mcp
What is the io.github.CloudCorpRecords/shopdata MCP server?
io.github.CloudCorpRecords/shopdata is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/shopdata. Amazon data as JSON: product details, reviews, keyword search, seller profiles and catalogues. This page covers its npm package (@reneturcios/shopdata).
Is the io.github.CloudCorpRecords/shopdata MCP server safe to use?
io.github.CloudCorpRecords/shopdata scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.CloudCorpRecords/shopdata MCP server expose?
io.github.CloudCorpRecords/shopdata exposes 5 tools: hasdata_amazon_product_getProductDetails, hasdata_amazon_reviews_getProductReviews, hasdata_amazon_search_getSearchResults, hasdata_amazon_seller_getSellerDetails, hasdata_amazon_seller_products_getSellerProducts. Their descriptions and schemas cost roughly 1,260 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/shopdata MCP server still maintained?
io.github.CloudCorpRecords/shopdata is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CloudCorpRecords/shopdata MCP server under?
io.github.CloudCorpRecords/shopdata declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.CloudCorpRecords/shopdata MCP server?
VerifyMCP ran 16 checks on io.github.CloudCorpRecords/shopdata, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.