DataDive vs HasData Amazon
A side-by-side look at the DataDive and HasData Amazon MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
HasData AmazonE-Commerce · Local subprocess (stdio)Amazon keyword search, product details, seller profiles and seller catalogues, as structured JSON.64GoodAuth: not declaredVerdict: choose DataDive for e-commerce work as a local process; choose HasData Amazon for e-commerce as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose DataDive when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DATADIVE_API_KEY. - You want tools like
list_niches, get_niche_keywords, list_keyword_exclusions.
Choose HasData Amazon when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HASDATA_API_KEY. - You want tools like
hasdata_amazon_product_getProductDetails, hasdata_amazon_reviews_getProductReviews, hasdata_amazon_search_getSearchResults.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | HasData Amazon | |
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 63/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | DATADIVE_API_KEY | HASDATA_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 10 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 43 | 5 |
| Full listing | View DataDive | View HasData Amazon |
Tools & capabilities
DataDive tools 43
list_nichesUse this first when the user asks about their niches, or to find a `nicheId` for use with `get_niche_keywords`, `get_niche_competitors`, or `get_ranking_juice`. Retrieves a paginated list of Niches, newest dive first. Each Niche represents a market segment or product category being tracked. Returns nicheId, heroKeyword, nicheLabel, marketplace (com/uk/de/...), and latestResearchDate per niche, plus pagination metadata (currentPage, pageSize, total, lastPage, hasNext, hasPrev). Narrow with `searchText` (label/keyword) or `searchAsin` (a competitor ASIN) instead of scanning pages; a page holds at most 50 niches, so the full list of a large account needs several calls.get_niche_keywordsUse this when the user asks about keywords, search terms, or search volume for a niche. Retrieves the master keyword list for the specified Niche — the relevant search terms monitored for ranking and performance metrics. For each keyword, returns search volume, relevancy (numeric score or "Outlier"), and competitor ASIN organic ranks (asinRanks: { ASIN -> rank | null }), plus `origin`: `mkl` (found by the dive), `manual` (added by hand with `add_niche_keywords`), `outlier` / `residue` (moved in from those lists). Only `manual`, `outlier` and `residue` keywords can be taken out with `remove_niche_keywords`. Keywords hidden by the niche's keyword exclusions are not listed; see `list_keyword_exclusions`. Also returns the latestResearchDate.list_keyword_exclusionsUse this to see which keywords are hidden from a niche's Master Keyword List, e.g. when a keyword the user expects is missing from `get_niche_keywords`. Returns the same lists the DataDive web app shows, oldest first: `exact` — each entry hides the one keyword that matches it exactly, with that keyword's `searchVolume` (0 when the niche has no such keyword); `phrase` — each entry hides every keyword that contains the phrase, with `excludedKeywordsCount` and the total `searchVolume` of the keywords it hides (not counting ones already excluded exactly). Exclusions hide keywords wherever they come from: the dive, the Outliers and Residue lists, and hand-added ones. Change them with `add_keyword_exclusions` and `remove_keyword_exclusions`.get_niche_rootsUse this when the user wants to find the highest-impact words across a niche's keywords, asks about 'keyword roots', or wants to prioritize terms for a listing. Retrieves the keyword lexical roots for the Niche — individual words or word-combinations extracted from the Master Keyword List (e.g. 'bluetooth headphones' yields roots 'bluetooth', 'headphones', 'bluetooth headphones'). Returns `roots` and `normalizedRoots` tables, each item with root, frequency (how many keywords contain it), broadSearchVolume (summed search volume of those keywords), and broadSearchVolumeRatio (0-1, relative to the top root), plus the per-keyword breakdowns and latestResearchDate.get_niche_competitorsUse this for competitor ASINs, product titles, BSR, sales/revenue benchmarks, or niche opportunity scoring. Retrieves the list of Competitors within the specified Niche along with Niche statistics. For the Niche: keyword statistics, opportunity evaluation, benchmark median values, and overall competitor strength assessment. For each Competitor: ASIN, product title, BSR, category and full category tree, sales, revenue, ratings, reviews, price, number of variations, image URL, total Ranking Juice, and ranking data. BSR supports ranking Competitors by sales position within mentioned category. For the Ranking Juice breakdown by title, bullets and description, use `get_ranking_juice`.get_ranking_juiceUse this when the user asks 'how do I rank higher', 'what's my ranking juice', or wants listing-optimization guidance. Retrieves the Ranking Juices for each Competitor within the specified Niche. Ranking Juice is DataDive's proprietary metric identifying the key factors driving search-ranking success for each Competitor's listing. Returns currentListing and optimizedListing breakdowns (rankingJuice + per-property contributions: title, bullets, description) plus per-competitor listing scores and the latestResearchDate.list_rank_radarsUse this to find a `rankRadarId` before calling `get_rank_radar_data`. Filter by `nicheId` if the user has already identified a niche. Retrieves a paginated list of Rank Radars — keyword-rank trackers monitoring organic and sponsored positions for specific ASINs over time. Each item includes id, status (ACTIVE, PAUSED or ARCHIVED), asin, marketplace, keywordCount, title, imageUrl, and summary metrics: top10KW, top10SV, top50KW, top50SV. Supports pagination metadata (currentPage, pageSize, total, lastPage, hasNext, hasPrev); a page holds at most 50 Rank Radars, so a large account needs several calls.get_rank_radar_dataUse this to analyze keyword ranking trends over time. Requires startDate and endDate (yyyy-mm-dd), at most 90 days apart. Retrieves historical keyword ranking data for the specified Rank Radar within the date range. Without `currentPage` and `pageSize` it returns every active keyword in one result. To read one page instead — faster for large Rank Radars — pass `currentPage` and/or `pageSize` (max 100) and continue with `currentPage` + 1 while `hasNext` is true. The response carries currentPage, pageSize, total, lastPage, hasNext and hasPrev; `total` is the Rank Radar's active keyword count. Paused keywords are not included. Each keyword has id, keyword, searchVolume, relevancy, ranks (per-day { date, organicRank, sponsoredRank, impressionRank }), and `highlights` — the user tags on this keyword. Each `highlights` entry is the same object `list_rank_radar_tags` returns (id, title, color, description, startAt, endAt, type, krtId, krtKeywordId); its `id` is the `tagId` the tag-management tools take. A rank of 101 means the product was not in the top 100 results that day. For PPC metrics use `get_rank_radar_ppc_data`; for Search Query Performance use `get_rank_radar_sqp_data`. Use after `list_rank_radars` to discover a `rankRadarId`.get_rank_radar_sqp_dataUse this when the user asks how shoppers search, click, add to cart and buy for the keywords of a Rank Radar — Amazon's Search Query Performance (SQP) data, from Brand Analytics. Requires startDate and endDate (yyyy-mm-dd), at most 90 days apart; 30 days or less keeps it fast. Each keyword's metrics are aggregated over the range: searchQueryVolume and searchQueryScore; impressions, clicks, cart adds and purchases, each as the total across all sellers (`*TotalCount`), this ASIN family's count (`*AsinCount`) and its share (`*AsinShare`); click, cart-add and purchase rates; and ctr/cvr for the market (`*Total`) and for this ASIN family (`*Asin`). `numberOfDaysWithData` says how many days of the range had SQP data; metrics are null when there is none, which is normal for low-volume keywords, recent dates (Amazon publishes SQP with a delay) and sellers without Brand Analytics. Results are paged by keyword: `data` holds one page, and the response carries currentPage, pageSize, total, lastPage, hasNext and hasPrev. `total` is the Rank Radar's active keyword count; to read every keyword, call again with `currentPage` + 1 while `hasNext` is true, using `pageSize` 100 for large Rank Radars. Paused keywords are not included. Each call counts toward API usage and is rate limited (about 60 requests/minute). Use after `list_rank_radars` to discover a `rankRadarId`.get_rank_radar_ppc_dataUse this when the user asks about advertising (Sponsored Products) performance for the keywords of a Rank Radar. Requires startDate and endDate (yyyy-mm-dd), at most 90 days apart; 30 days or less keeps it fast. Each keyword's metrics are aggregated over the range: sponsoredRank (median; 101 means not in the top 100 sponsored results), impressionRank and impressionRankShare; how many exact, phrase, broad and auto campaigns target it; organicSales, ppcSales, ppcSpend, costPerClicks, clickThroughRate, conversionRate, totalClicks, totalImpressions, totalOrders and acos. Metrics are null or 0 when the seller runs no ads on a keyword. Set `includeCampaigns` for the per-campaign breakdown. Results are paged by keyword: `data` holds one page, and the response carries currentPage, pageSize, total, lastPage, hasNext and hasPrev. `total` is the Rank Radar's active keyword count; to read every keyword, call again with `currentPage` + 1 while `hasNext` is true, using `pageSize` 100 for large Rank Radars. Paused keywords are not included. Each call counts toward API usage and is rate limited (about 60 requests/minute). For the seller's campaigns as a whole, use `list_ppc_campaigns`. Use after `list_rank_radars` to discover a `rankRadarId`.list_rank_radar_tagsUse this to find a `tagId` before calling `update_rank_radar_tag`, `delete_rank_radar_tag`, `add_rank_radar_tag_search_terms` or `remove_rank_radar_tag_search_terms`. Returns the user tags ("highlights") on the specified Rank Radar, ordered by title (case-insensitive, ascending). Each row carries `id`, `title`, `color`, `description`, `startAt`, `endAt`, `createdAt`, and `keywordCount` — the number of Rank Radar keywords this tag is applied to. The system "paused" tag (the one the quota pauser writes with a reserved colour) is not listed and cannot be addressed from these tools. Supports pagination metadata (currentPage, pageSize, total, lastPage, hasNext, hasPrev); a page holds at most 50 tags.create_rank_radarUse this to start tracking organic and sponsored keyword rankings for an ASIN within a niche. ⚠️ Spends Search Term tokens (cost scales with `numberOfKeywords`) and cannot be undone — set `confirm: true` only after the user approves the cost. Not safe to retry: each call spends tokens again and creates a separate Rank Radar — if a call errors or times out, check `list_rank_radars` instead of re-calling. The first call previews the creation and may return `warnings` alongside the cost note — for example that this product family is already tracked by another Rank Radar. Show every warning `message` to the user verbatim, before asking them to confirm; do not summarise it or decide on their behalf. A warning never blocks creation. Returns the new `rankRadarId`; read its data later with `get_rank_radar_data`. Requires `asin`, `numberOfKeywords` (min 1), and a `nicheId` from `list_niches`.- +31 more on the listing page
HasData Amazon tools 5
hasdata_amazon_product_getProductDetailsGet 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.hasdata_amazon_reviews_getProductReviewsGet 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.hasdata_amazon_search_getSearchResultsGet 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.hasdata_amazon_seller_getSellerDetailsGet 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.hasdata_amazon_seller_products_getSellerProductsGet 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.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
DataDive
{
"mcpServers": {
"datadive": {
"command": "npx",
"args": [
"-y",
"@datadive-tools/mcp"
],
"env": {
"DATADIVE_API_KEY": "YOUR_DATADIVE_API_KEY_HERE"
}
}
}
}
HasData Amazon
{
"mcpServers": {
"hasdata-amazon": {
"command": "npx",
"args": [
"-y",
"@hasdata/amazon-mcp"
],
"env": {
"HASDATA_API_KEY": "YOUR_HASDATA_API_KEY_HERE"
}
}
}
}
Frequently asked questions
DataDive is categorized under E-Commerce and uses a local stdio subprocess. HasData Amazon belongs to E-Commerce and uses a local stdio subprocess. Pick DataDive for e-commerce work and HasData Amazon for e-commerce.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
DataDive has no declared pricing — check the project's own site. HasData Amazon has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add datadive and hasdata-amazon as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, DataDive has a quality signal of 63/100 (Good) with 1 views, 0 installs and 1 GitHub stars. HasData Amazon has 64/100 (Good) with 1 views, 0 installs and 10 GitHub stars.
