Apiguru Amazon Data
PYPI · APIGURU-MCP · 3 COMPONENTS · SCANNED SEP 20
Live Amazon product, review, search, deal, offer/stock and seller data across 20 marketplaces.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 32 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 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 6157 tokens (~513/item across 12 items; 12 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Apiguru Amazon Data MCP server?
Apiguru Amazon Data runs locally as a PyPI package, launched with uvx apiguru-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · apiguru-mcp
claude mcp add app-apiguru-amazon-data -- uvx apiguru-mcp
{
"mcpServers": {
"app-apiguru-amazon-data": {
"command": "uvx",
"args": [
"apiguru-mcp"
]
}
}
} {
"servers": {
"app-apiguru-amazon-data": {
"command": "uvx",
"args": [
"apiguru-mcp"
]
}
}
} codex mcp add app-apiguru-amazon-data -- uvx apiguru-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-apiguru-amazon-data": {
"type": "local",
"command": [
"uvx",
"apiguru-mcp"
],
"enabled": true
}
}
} openclaw mcp add app-apiguru-amazon-data --command uvx --arg apiguru-mcp
mcp_servers:
app-apiguru-amazon-data:
command: "uvx"
args: ["apiguru-mcp"] {
"McpServers": {
"app-apiguru-amazon-data": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"apiguru-mcp"
]
}
}
} assistant mcp add app-apiguru-amazon-data -t stdio -c uvx -a apiguru-mcp
{
"mcpServers": {
"app-apiguru-amazon-data": {
"command": "uvx",
"args": [
"apiguru-mcp"
]
}
}
} 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 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.
- 13 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 1.1.22 → 1.1.25 functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +16
- Malware scan: unverified → pass ▲ security
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 20 Sept 2026 · Analysed pypi/apiguru-mcp@1.1.25
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| 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 →
best_sellers Best-seller rankings for a category ~768
Best-seller rankings for a department of one marketplace, 50 per page. Every answer carries the department it resolved to and how (category_resolution: by slug, name or a fragment of a name, with a hint when a fragment such as 'shoes' landed on the whole 'Clothing, Shoes & Jewelry' department), available_categories (that marketplace's departments with slugs) and available_subcategories (the children of the node shown, with the ids subcategory_code takes). On amazon.com subcategory_code also takes any browse node id at any depth, or a name resolved under the department ("women's shoes", "mules & clogs"); category.subcategory_path gives the node's full path and category.heading the page's own title line. Price: $0.01 per call. No required parameters - calling it bare returns US appliances page 1. `category` accepts a slug, a display name, one of the older US department names, or a unique fragment; category_resolution.via says which, and a fragment match adds a hint naming the subcategories that carry the word, with ids. On amazon.com the whole browse tree is known: subcategory_code takes any node id or a name at any depth, subcategory_name and subcategory_path are filled without a fetch, and available_subcategories lists the node's real children (empty on a leaf). Other marketplaces name only what their navigation showed. page is capped at 5 (a 400 beyond, not a 500). `rank` is the position within the requested list on this page. Rows are the same for every marketplace; only the department vocabulary differs, and the answer carries it.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Best-seller department, by slug or by name as Amazon shows it for that marketplace (case-insensitive; a unique fragment works, and the answer's category_resolution says when a fragment was used -- 's… |
| compact | boolean | – | Return light rows: identity, price, rating, badges and one delivery_date, dropping the long delivery prose that repeats itself across three fields. false returns every field the REST API sends (rough… |
| fields | – | – | Comma-separated row fields to return instead of the light set, e.g. "asin,product_title,product_price". Rows list what they left out under _omitted_fields. |
| geo | string | – | Marketplace country code. |
| limit | integer | – | How many ranked products to return from this page (0 = all of them). A full page is up to 48 rows and about 54 KB, which most clients spill to a file instead of showing inline. The answer carries _tr… |
| page | integer | – | Result page, 1-based, 50 rows each; Amazon's lists stop at page 5. |
| subcategory_code | – | – | Browse node id under `category`: one from available_subcategories of a previous answer, or on amazon.com any node id at any depth (679410011 is Women > Shoes > Mules & Clogs) or a name resolved under… |
| Name | Type | Req | Description |
|---|---|---|---|
| available_categories | – | – | – |
| available_subcategories | – | – | – |
| category | – | – | – |
| category_resolution | – | – | – |
| data | – | – | – |
| max_page | – | – | – |
| page | – | – | – |
| page_size | – | – | – |
| request_id | – | – | – |
| success | – | – | – |
No examples provided.
deals Current Amazon deals with filters ~965
Returns the current Amazon deals feed: ASIN, title, deal price, list price, discount, deal badge, start/end time and product links. Filter by department (categories), brand id (brands), rating cut-off, price bounds, minimum discount and Prime program. Every answer carries available_filters (the category and brand ids this marketplace accepts, with names), filters_applied / filters_ignored (what took effect) and next_offset (the next page, null when the feed ends). Price: $0.01 per call. Filters are by id: categories takes a department id or name, brands takes brand ids only; available_filters in every answer lists both with names, and filters_applied / filters_ignored report what Amazon honoured. A page is 30 rows; page with offset=next_offset (null when exhausted); total_count caps at 500. min_price, max_price, min_discount and max_discount are applied to the rows after the fetch, scanning up to 3 upstream pages per call, so a page can hold fewer than 30 rows and total_count does not reflect them. An empty answer carries a hint saying why. Deal prices expire: check deal_ends_at. The older price_range and discount_range parameters are still accepted, as buckets (1-5 = under 25 / 25-50 / 50-100 / 100-200 / 200 and up; 1-4 = 10 / 25 / 50 / 70 percent off or more) or as bands such as 25-50 and 70+.
| Name | Type | Req | Description |
|---|---|---|---|
| brands | – | – | Comma-separated brand ids, e.g. 46655 for Samsung on US. Take them from brand_id on any deals row or from available_filters.brands (the brands present in the current result). Names resolve only when… |
| categories | – | – | Department to restrict to: its id from available_filters.categories, or its name as Amazon shows it for that marketplace (case-insensitive; a unique fragment such as "electronics" works). US departme… |
| compact | boolean | – | Return light rows: identity, prices, discount, badge, end time, links, brand_id and department_ids, dropping the image arrays. false returns every field the REST API sends. |
| fields | – | – | Comma-separated row fields to return instead of the light set, e.g. "asin,product_title,product_price". Rows list what they left out under _omitted_fields. |
| geo | string | – | Marketplace country code. |
| limit | integer | – | How many deals to return from this page (0 = all of them). A full page is 30 rows and roughly 35 KB with every field, which most clients spill to a file instead of showing inline. The answer carries… |
| max_discount | – | – | Largest discount percentage to return. |
| max_price | – | – | Highest deal price to return, in the marketplace currency. |
| min_discount | – | – | Smallest discount percentage to return, e.g. 50 for half price or better. |
| min_price | – | – | Lowest deal price to return, in the marketplace currency. Applied to the fetched rows; see notes. |
| min_product_star_rating | – | – | Amazon's deals feed offers one rating cut-off: 4 = four stars and up. ALL or omitted = no cut-off. Other values are rejected with a free 400. |
| offset | integer | – | Row to start at. A page is 30 rows; pass the previous answer's next_offset for the next page. |
| prime_early_access | boolean | – | Only Prime Early Access deals. A marketplace lists the programs it is running under available_filters.prime_programs; when Early Access is not running the answer is empty with a hint saying so. |
| prime_exclusive | boolean | – | Only deals in Amazon's Prime Exclusive program. |
| Name | Type | Req | Description |
|---|---|---|---|
| amazon_request_count | – | – | – |
| deals | – | – | – |
| request_id | – | – | – |
| success | – | – | – |
No examples provided.
list_capabilities List endpoints, prices and marketplaces (free) ~62
List every Apiguru endpoint with its price, required parameters and supported marketplaces, plus your current access mode, cache and session budget. Free: answers locally with no network request and no charge. Call this before paid tools if you need to plan.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
offers_stock Live offers and inventory for up to 10 ASINs ~261
Returns the current offer list per ASIN (seller, price, condition, buy-box winner) and, optionally, the actual purchasable stock quantity. Price: $0.015 per item (max 10). Billed per upstream Amazon request, which is more than one per ASIN when check_inventory is true. /scrape is a legacy alias for the same handler.
| Name | Type | Req | Description |
|---|---|---|---|
| asins | string | yes | Comma-separated ASIN list, maximum 10. Each must be 10 uppercase alphanumeric characters; malformed entries are rejected with 400. |
| check_inventory | boolean | – | Resolve the true purchasable stock quantity. Slower and bills more upstream requests, so leave off unless you need the number. |
| condition | – | – | Comma-separated condition filter: ALL, NEW, USED_LIKE_NEW, USED_VERY_GOOD, USED_GOOD, USED_ACCEPTABLE (case-insensitive). Omit for every offer. An unknown value is a free 400 listing the allowed ones… |
| geo | string | – | Marketplace country code. |
| offers_count | string | – | 'all' for every offer, 'winner' for the buy-box offer only, or a specific alphanumeric Offer ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| amazon_request_count | – | – | – |
| country_code | – | – | – |
| request_id | – | – | – |
| response_time | – | – | – |
| results | – | – | – |
No examples provided.
product_details Full product detail for a single ASIN ~262
Fetches the complete product record for one ASIN on one marketplace: title, price, star rating, rating count, images, description, feature bullets, variations and category. Price: $0.01 per call. 404 means the ASIN is absent from that marketplace and IS billed. 503 means our fetch failed and is NOT billed - retry. Bullet points and specs are what Amazon shows for the listing; on multi-variant listings they can describe the product family rather than the exact variant. A null field means Amazon did not show it.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | yes | Single Amazon ASIN, 10 uppercase alphanumeric characters. Exactly one - comma-separated lists are rejected; use product_details_batch for many. |
| compact | boolean | – | Return the compact record (about 4 KB: identity, price, rating, availability, bullets, category, offer, buy box). false returns the full record (about 75 KB, includes from_manufacturer, tech_specs, p… |
| fields | – | – | Comma-separated top-level fields to return instead of the compact set, e.g. "tech_specs,product_information". Any response lists what it left out under _omitted_fields. |
| geo | string | – | Marketplace country code. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| request_id | – | – | – |
| success | – | – | – |
No examples provided.
product_details_batch Product detail for up to 20 ASINs in one call ~266
Batch variant of product_details. Accepts a comma-separated ASIN list, deduplicates it, and fetches all of them concurrently. Far cheaper and faster than N single calls. Price: $0.008 per item (max 20). Billed per ASIN processed, including ones that come back not-found. More than 20 ASINs returns 413. Bullet points and specs are what Amazon shows for the listing; on multi-variant listings they can describe the product family rather than the exact variant. A null field means Amazon did not show it.
| Name | Type | Req | Description |
|---|---|---|---|
| asins | string | yes | Comma-separated ASIN list, maximum 20 after de-duplication. Each must be 10 uppercase alphanumeric characters. |
| compact | boolean | – | Return the compact record (about 4 KB: identity, price, rating, availability, bullets, category, offer, buy box). false returns the full record (about 75 KB, includes from_manufacturer, tech_specs, p… |
| fields | – | – | Comma-separated top-level fields to return instead of the compact set, e.g. "tech_specs,product_information". Any response lists what it left out under _omitted_fields. |
| geo | string | – | Marketplace country code. |
| Name | Type | Req | Description |
|---|---|---|---|
| amazon_request_count | – | – | – |
| billable_requests_count | – | – | – |
| country_code | – | – | – |
| request_id | – | – | – |
| response_time | – | – | – |
| results | – | – | – |
No examples provided.
product_reviews Customer reviews for a single ASIN ~198
Returns the review block for one ASIN: overall star rating, total rating count, Amazon's 'customers say' AI summary, and the individual review list. Price: $0.01 per call. Same 404-billed / 503-not-billed semantics as product_details. Takes no filters: it returns the rating, rating count, the 'customers say' summary and the reviews Amazon shows on the product page itself. There is no paging, star filter or sort -- Amazon's review pages require a signed-in customer, and the API does not sign in. For per-star counts read the rating histogram on product_details.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | yes | Single Amazon ASIN, 10 uppercase alphanumeric characters. |
| geo | string | – | Marketplace country code. |
| max_reviews | integer | – | Cap on individual reviews returned (0 = all). The rating summary and customers_say are always returned; _reviews_total says how many exist. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| request_id | – | – | – |
| success | – | – | – |
No examples provided.
search Search Amazon products by keyword ~892
Search Amazon products by keyword. Filters: page, sort_by, category_id (browse node), min_price / max_price (decimals), product_condition (NEW / USED / RENEWED), brand, seller_id, today_deals and deal_type (coupons, all_discounts, buy_more_save_more). Every answer carries filters_applied, filters_ignored (with the reason) and available_filters for that marketplace. Price: $0.01 per call. Blank values and the literal string 'null' are treated as unset. Invalid page, sort_by, price, product_condition or deal_type is a free 400 naming the parameter and the allowed values. Condition and deal refinements use per-marketplace node ids captured from Amazon's own search pages; a marketplace that lacks one gets the unfiltered feed plus an entry under filters_ignored, never a silent empty page. `product_num_ratings` and `offers_count` are integers; `product_star_rating`, `product_price` and `product_original_price` are decimal strings; a null field means Amazon did not show it. `is_prime` is true when the result carries a Prime badge or its delivery line offers Prime delivery. `metadata.total_pages` says how far `page` can go. A full page is up to 48 results and about 54 KB; the tool returns the first 10 as light rows by default and the answer carries `_truncated`, `_omitted_fields`, `_projection` and `_notes`. filters_applied echoes the effective sort_by (RELEVANCE when none was sent). A BEST_SELLERS ordering is Amazon's query-scoped popularity, not a category rank: a row's `badges` / `is_best_seller` are what the result card showed for this query, and an ASIN that is #1 in its subcategory can carry no badge here while product_details reports best_seller=true with the rank. For a rank claim, use product_details or best_sellers.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | Brand name as Amazon spells it (case-insensitive), e.g. Samsung. |
| category_id | – | – | Amazon browse node id to restrict to, e.g. 172282 (Electronics on US). Take one from a best_sellers answer's available_subcategories, a product's category_path, or node= in an Amazon URL. Ids differ… |
| compact | boolean | – | Return light rows: identity, price, rating, badges and one delivery_date, dropping the long delivery prose that repeats itself across three fields. false returns every field the REST API sends (rough… |
| deal_type | – | – | A specific promotion refinement: today_deals, all_discounts, coupons or buy_more_save_more. available_filters.deal_type lists the ones this marketplace has. |
| fields | – | – | Comma-separated row fields to return instead of the light set, e.g. "asin,product_title,product_price". Rows list what they left out under _omitted_fields. |
| geo | string | – | Marketplace country code. |
| limit | integer | – | How many search results to return from this page (0 = all of them). A full page is up to 48 rows and about 54 KB, which most clients spill to a file instead of showing inline. The answer carries _tru… |
| max_price | – | – | Highest price, in the marketplace currency. |
| min_price | – | – | Lowest price, in the marketplace currency; decimals such as 19.99 are fine. |
| page | integer | – | Result page, 1-based. metadata.total_pages says how far it goes. |
| product_condition | – | – | NEW, USED or RENEWED (case-insensitive). Applied with the marketplace's own condition node; where a marketplace does not offer one, the answer's filters_ignored says so and available_filters lists wh… |
| query | string | yes | Search keywords. Required and must be non-empty. |
| seller_id | – | – | Restrict results to one seller's offers (Amazon seller id). |
| sort_by | string | – | Result ordering. |
| today_deals | boolean | – | Only items in Today's Deals, using that marketplace's own refinement. Where a marketplace has none (amazon.fr on 2026-09-08) it is reported under filters_ignored. |
| Name | Type | Req | Description |
|---|---|---|---|
| amazon_request_count | – | – | – |
| available_filters | – | – | – |
| filters_applied | – | – | – |
| filters_ignored | – | – | – |
| metadata | – | – | – |
| products | – | – | – |
| request_id | – | – | – |
| success | – | – | – |
No examples provided.
seller_products Products listed by a seller ~612
Products listed by a seller: a storefront search. Takes the same filters as search -- query, page, sort_by, category_id, min_price / max_price, product_condition, brand, today_deals, deal_type -- and answers with filters_applied, filters_ignored and available_filters like search does. Price: $0.01 per call. Unlike seller_profile_batch, seller_id format is not pattern-validated here. metadata.total_pages says how far page goes (48 rows a page). Invalid sort_by, price, product_condition or deal_type is a free 400 that lists the allowed values.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | Brand name as Amazon spells it (case-insensitive), e.g. Samsung. |
| category_id | – | – | Amazon browse node id to restrict to, e.g. 172282 (Electronics on US). Take one from a best_sellers answer's available_subcategories, a product's category_path, or node= in an Amazon URL. Ids differ… |
| compact | boolean | – | Return light rows: identity, price, rating, badges and one delivery_date, dropping the long delivery prose that repeats itself across three fields. false returns every field the REST API sends (rough… |
| deal_type | – | – | A specific promotion refinement: today_deals, all_discounts, coupons or buy_more_save_more. available_filters.deal_type lists the ones this marketplace has. |
| fields | – | – | Comma-separated row fields to return instead of the light set, e.g. "asin,product_title,product_price". Rows list what they left out under _omitted_fields. |
| geo | string | – | Marketplace country code. |
| limit | integer | – | How many the seller's products to return from this page (0 = all of them). A full page is up to 48 rows and about 54 KB, which most clients spill to a file instead of showing inline. The answer carri… |
| max_price | – | – | Highest price, in the marketplace currency. |
| min_price | – | – | Lowest price, in the marketplace currency; decimals such as 19.99 are fine. |
| page | integer | – | Result page, 1-based. metadata.total_pages says how far it goes. |
| product_condition | – | – | NEW, USED or RENEWED (case-insensitive). Applied with the marketplace's own condition node; where a marketplace does not offer one, the answer's filters_ignored says so and available_filters lists wh… |
| query | – | – | Optional keywords to search within this seller's storefront. |
| seller_id | string | yes | Restrict results to one seller's offers (Amazon seller id). |
| sort_by | string | – | Result ordering. |
| today_deals | boolean | – | Only items in Today's Deals, using that marketplace's own refinement. Where a marketplace has none (amazon.fr on 2026-09-08) it is reported under filters_ignored. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| request_id | – | – | – |
| success | – | – | – |
No examples provided.
seller_profile_batch Seller profiles for up to 10 seller IDs ~109
Returns the storefront profile for each seller id: business name, rating, feedback counts, address and marketplace presence. Price: $0.012 per item (max 10). Seller ID validation is all-or-nothing: one malformed id rejects the entire request with 400.
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | Marketplace country code. |
| seller_ids | string | yes | Comma-separated seller IDs, maximum 10. Each must be 13-15 alphanumeric characters or the whole call 400s. |
| Name | Type | Req | Description |
|---|---|---|---|
| amazon_request_count | – | – | – |
| billable_requests_count | – | – | – |
| country_code | – | – | – |
| request_id | – | – | – |
| response_time | – | – | – |
| results | – | – | – |
No examples provided.
seller_reviews Feedback reviews for a seller ~323
Returns paginated seller feedback, optionally filtered to a star-rating window. Price: $0.01 per call. from_rating and to_rating are optional; omit both for unfiltered feedback. A page holds 5 reviews and the answer carries current_page and has_next_page; Amazon exposes no total, so page until has_next_page is false (up to page 100).
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | Return light rows: identity, price, rating, badges and one delivery_date, dropping the long delivery prose that repeats itself across three fields. false returns every field the REST API sends (rough… |
| fields | – | – | Comma-separated row fields to return instead of the light set, e.g. "asin,product_title,product_price". Rows list what they left out under _omitted_fields. |
| from_rating | – | – | Lowest star rating to include, 1-5. |
| geo | string | – | Marketplace country code. |
| limit | integer | – | How many seller reviews to return from this page (0 = all of them). A full page is up to 48 rows and about 54 KB, which most clients spill to a file instead of showing inline. The answer carries _tru… |
| page | integer | – | Result page, 1-based, 5 reviews a page; has_next_page in the answer says whether another exists. |
| seller_id | string | yes | Amazon seller ID. Required. |
| to_rating | – | – | Highest star rating to include, 1-5. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| request_id | – | – | – |
| success | – | – | – |
No examples provided.
send_feedback Report a bug or request a feature (free) ~268
Report a bug, ask for a field, or say what would make this API more useful. Free: never billed, no API key needed. Prefer GitHub if you have an account -- an issue at https://github.com/apiguru-app/agent-kit/issues gets a reply on the thread, this wall does not. Use this tool when you have no GitHub account or nothing to attach one to. message: what happened or what you want. Be specific: the tool, the parameters, the field, what you expected, what you got, and the request_id from the answer. One issue per entry -- a five-point list cannot be closed point by point. category: bug | wish | praise | question | other endpoint: which tool or path it is about, e.g. "search". agent: what you are, e.g. "acme-pricing-bot/2.1". Optional. contact: a GitHub handle or email if you want a reply. Shown publicly on the wall. Optional.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | – |
| category | string | – | – |
| contact | string | – | – |
| endpoint | string | – | – |
| message | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Apiguru Amazon Data MCP server?
Apiguru Amazon Data is an MCP server listed in the public MCP registry as app.apiguru/amazon-data. Live Amazon product, review, search, deal, offer/stock and seller data across 20 marketplaces. This page covers its PyPI package (apiguru-mcp).
Is the Apiguru Amazon Data MCP server safe to use?
Apiguru Amazon Data scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 Apiguru Amazon Data MCP server expose?
Apiguru Amazon Data exposes 12 tools: product_details, product_reviews, search, product_details_batch, offers_stock, and 7 more. Their descriptions and schemas cost roughly 4,986 tokens of context every time the server is loaded.
Is the Apiguru Amazon Data MCP server still maintained?
Apiguru Amazon Data is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Apiguru Amazon Data MCP server under?
Apiguru Amazon Data declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.