# Easyparser — Amazon Product & Seller Data (npm · easyparser-mcp)

Real-time Amazon product, seller, and search data for AI agents across 21 marketplaces.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.easyparser.com`: 80/100, [markdown](https://verifymcp.io/servers/com-easyparser-easyparser/mcp.md), [page](https://verifymcp.io/servers/com-easyparser-easyparser/mcp)
- npm · `easyparser-mcp`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-easyparser-easyparser/easyparser-mcp.md), [page](https://verifymcp.io/servers/com-easyparser-easyparser/easyparser-mcp)

## Channel facts

- Registry: `npm`
- Package: `easyparser-mcp`
- Version: `1.3.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 5152 tokens (~322/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Easyparser — Amazon Product & Seller Data MCP server?

Easyparser — Amazon Product & Seller Data runs locally as an npm package, launched with npx -y easyparser-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-easyparser-easyparser -- npx -y easyparser-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-easyparser-easyparser": {
      "command": "npx",
      "args": [
        "-y",
        "easyparser-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-easyparser-easyparser": {
      "command": "npx",
      "args": [
        "-y",
        "easyparser-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-easyparser-easyparser -- npx -y easyparser-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-easyparser-easyparser": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "easyparser-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-easyparser-easyparser --command npx --arg -y --arg easyparser-mcp
```

### Hermes

```yaml
mcp_servers:
  com-easyparser-easyparser:
    command: "npx"
    args: ["-y", "easyparser-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-easyparser-easyparser": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "easyparser-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-easyparser-easyparser -t stdio -c npx -a -y easyparser-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-easyparser-easyparser": {
      "command": "npx",
      "args": [
        "-y",
        "easyparser-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 75, +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.

### 2026-09-14 (score 74, +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.

### 2026-09-12 (score 73, +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.

### 2026-09-10 (score 72, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-05 (score 68, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-09-04 (score 68, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-09-03 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (16)

### `get_product_detail` (~456 tokens)

Fetch complete, structured information about a single Amazon product: title, brand, images, feature bullets, description, Buy Box price and availability, Prime eligibility, rating and review count, Best Sellers Rank, category path, variants, specifications, and top reviews. This is the primary tool for product analysis, listing enrichment, and price monitoring.

Use this tool when you need a full product profile. If you only need competing seller prices, use get_product_offers instead (cheaper context). If you only need the sales rank, use get_bestseller_rank. If you only need shipping dimensions or the FBA fee category, use get_package_dimensions.

Provide EITHER the identifier field OR url — never both. Costs 1 credit; set a_plus_content to true only when the user explicitly asks about enhanced brand content, as it costs 1 extra credit.

Input parameters:

- `a_plus_content` (boolean): Set true to include the 'From the manufacturer' A+ enhanced brand content. Costs 1 additional credit. Default false.
- `asin` (string): Amazon Standard Identification Number — a 10-character alphanumeric product identifier (e.g. B0CJB6V2L5). Found in the product URL after /dp/ or /gp/product/.
- `currency` (string): ISO currency code for price display (e.g. usd, eur, try). Prices are converted by Amazon's own display logic.
- `domain` (string): Amazon marketplace domain extension. Determines the regional Amazon site the data is fetched from. Use the domain that matches the user's market — prices, availability and rankings differ across mark…
- `language` (string): Language code for the Amazon page, in locale format (e.g. en_US, de_DE, tr_TR). Affects the language of titles, descriptions and reviews in the response.
- `seller_id` (string): Fetch the product as offered by a specific seller (their Seller ID). Only use when the user asks about a specific merchant's offer.
- `url` (string): Full Amazon product URL (e.g. https://www.amazon.com/dp/B0CJB6V2L5). Use this when the user pastes a link instead of an ASIN.

### `get_product_offers` (~344 tokens)

Fetch the list of seller offers for an Amazon product: every merchant selling the item with their price, shipping cost, condition (new/used), fulfillment type (FBA/FBM), and seller rating. Also returns the Buy Box winner. This is the tool for competitive price analysis, reseller monitoring, and availability tracking.

Use this tool when the question is about WHO sells the product and at WHAT price. If you need the product's own details (title, images, rating), use get_product_detail instead.

Each requested page costs 1 credit. Start with a single page (default) and only increase max_page if the user needs the full offer list. Use the condition and shipping filters to narrow results instead of paginating — it is cheaper.

Input parameters:

- `asin` (string, required): Amazon Standard Identification Number — a 10-character alphanumeric product identifier (e.g. B0CJB6V2L5). Found in the product URL after /dp/ or /gp/product/.
- `condition` (string): Filter offers by item condition. Omit to include all conditions.
- `domain` (string): Amazon marketplace domain extension. Determines the regional Amazon site the data is fetched from. Use the domain that matches the user's market — prices, availability and rankings differ across mark…
- `free_shipping` (boolean): If true, return only offers with free shipping.
- `max_page` (integer): Ending page number. Each page costs 1 credit; max 5 pages per request. Default 1.
- `min_page` (integer): Starting page number. Default 1.
- `prime` (boolean): If true, return only Prime-eligible offers.

### `search_products` (~561 tokens)

Search Amazon by keyword or a full search/category URL and get structured product listings: ASIN, title, price, rating, review count, Prime status, and badges (Best Seller, Amazon's Choice) for each result. Also returns the available refinement filters (category, brand, price range) with their IDs.

Use this tool for market research, keyword analysis, and product discovery. If the user already has an ASIN or product URL, do NOT search — use get_product_detail directly.

Each page costs 1 credit. One page typically returns 20-40 products, which is enough for most questions. Use sort_by and exclude_sponsored to improve result quality instead of fetching more pages. To filter by category or brand, first run one search and read the refinements field in the response to discover valid filter IDs, then pass them in refinements.

Input parameters:

- `currency` (string): ISO currency code for price display (e.g. usd, eur, try). Prices are converted by Amazon's own display logic.
- `domain` (string): Amazon marketplace domain extension. Determines the regional Amazon site the data is fetched from. Use the domain that matches the user's market — prices, availability and rankings differ across mark…
- `exclude_sponsored` (boolean): If true, removes sponsored (paid ad) products from results. Recommended true for organic market analysis.
- `keyword` (string): Search query as a user would type it into Amazon (e.g. 'stainless steel water bottle 40oz'). Mutually exclusive with url.
- `language` (string): Language code for the Amazon page, in locale format (e.g. en_US, de_DE, tr_TR). Affects the language of titles, descriptions and reviews in the response.
- `max_page` (integer): Ending page number. Each page costs 1 credit; max 5 pages per request. Default 1.
- `min_page` (integer): Starting page number. Default 1.
- `refinements` (string): Category/attribute filters in Amazon's format: 'n:<category_id>,p_<filter_group>:<filter_id>'. Discover valid IDs from the refinements field of a previous search response. Example: 'n:7141123011,p_12…
- `sort_by` (string): Result ordering. 'featured' is Amazon's default; 'price-asc-rank' cheapest first; 'price-desc-rank' most expensive; 'review-rank' most reviewed; 'date-desc-rank' newest listings; 'exact-aware-popular…
- `url` (string): Full Amazon search or category URL. Use when the user pastes an Amazon link containing filters. Mutually exclusive with keyword.

### `lookup_product` (~309 tokens)

Convert an external product identifier (UPC, EAN, GTIN, ISBN, JAN, MINSAN) into the corresponding Amazon ASIN, with an essential product snapshot. This is the bridge between manufacturer/retail barcodes and the Amazon ecosystem.

Use this tool when the user has a barcode or standard product code and wants to find the matching Amazon listing. Typical workflows: catalog matching, inventory synchronization, converting supplier data into Amazon ASINs. Also accepts ASIN as input type if you need to validate one.

You MUST set identifier_type to match the code you have — guessing the wrong type returns no results. UPC is 12 digits, EAN/GTIN is 13, ISBN is 10 or 13 (books). If the user gives a keyword instead of a code, use search_products instead. Costs 1 credit.

Input parameters:

- `domain` (string): Amazon marketplace domain extension. Determines the regional Amazon site the data is fetched from. Use the domain that matches the user's market — prices, availability and rankings differ across mark…
- `identifier` (string, required): The product code value (e.g. '724382975021' for a UPC). Digits only for barcode types.
- `identifier_type` (string, required): The type of code provided. UPC: 12-digit US barcode. EAN/GTIN: 13-digit international barcode. ISBN: book identifier. JAN: Japanese barcode. MINSAN: Italian pharma code. ASIN: Amazon's own identifier.

### `get_sales_history` (~317 tokens)

Retrieve a product's historical performance over up to 12 months: weekly aggregated trends for estimated views/traffic, sales, price, and Best Sellers Rank. This is Easyparser's 'time machine' — the deepest competitive-intelligence tool in this server.

Use this tool for trend forecasting, seasonality analysis, conversion-rate estimation, and investment/sourcing due diligence. Do NOT use it for a simple current price check — get_product_detail is 5x cheaper for that.

IMPORTANT cost rule: the base cost is 5 credits, and each month of history adds 1 credit (3 months = 8 credits, 12 months = 17 credits). Always ask the user how far back they need, or default to 3 months for a quick trend read. The history array in the response is aggregated by WEEK, not by day.

Input parameters:

- `asin` (string, required): Amazon Standard Identification Number — a 10-character alphanumeric product identifier (e.g. B0CJB6V2L5). Found in the product URL after /dp/ or /gp/product/.
- `domain` (string): Amazon marketplace domain extension. Determines the regional Amazon site the data is fetched from. Use the domain that matches the user's market — prices, availability and rankings differ across mark…
- `history_range` (string): Depth of historical data in months. '0' returns only the current snapshot (5 credits). '3', '6', '9', '12' add weekly history at +1 credit per month. Default '0'.

### `get_bestseller_rank` (~207 tokens)

Get a product's current Best Sellers Rank (BSR): its numerical rank in main categories and sub-category node identifiers. A lightweight, single-purpose tool for popularity and demand tracking.

Use this tool when you only need the rank — e.g. 'Is this product selling well?' or daily rank monitoring. Lower rank number means higher sales velocity. If you also need price, rating or content, use get_product_detail instead (it includes BSR along with everything else). For historical rank trends, use get_sales_history. Costs 1 credit.

Input parameters:

- `asin` (string, required): Amazon Standard Identification Number — a 10-character alphanumeric product identifier (e.g. B0CJB6V2L5). Found in the product URL after /dp/ or /gp/product/.
- `domain` (string): Amazon marketplace domain extension. Determines the regional Amazon site the data is fetched from. Use the domain that matches the user's market — prices, availability and rankings differ across mark…

### `get_package_dimensions` (~202 tokens)

Get a product's precise physical and logistical attributes: package height, width, length, weight, and its Amazon fee category (e.g. Computers, Apparel). This is the FBA fee-estimation and shipping-cost tool.

Use this tool when the question is about shipping, storage, FBA fees, or warehouse planning. Do NOT use it for general product info — get_product_detail includes a human-readable dimensions string, but only THIS tool returns the structured fee category and exact measurements needed for fee calculation. Costs 1 credit.

Input parameters:

- `asin` (string, required): Amazon Standard Identification Number — a 10-character alphanumeric product identifier (e.g. B0CJB6V2L5). Found in the product URL after /dp/ or /gp/product/.
- `domain` (string): Amazon marketplace domain extension. Determines the regional Amazon site the data is fetched from. Use the domain that matches the user's market — prices, availability and rankings differ across mark…

### `get_seller_profile` (~308 tokens)

Unmask the legal identity and reputation of any Amazon merchant: legal business name, registered business address, and granular feedback trends over 30/90/365 days and lifetime. This is the supplier-verification and brand-protection tool.

Use this tool when the user asks 'who is this seller?', 'is this merchant legitimate?', or needs a supplier's legal entity for compliance or invoicing. To see WHAT the seller sells, use get_seller_products. To read individual buyer reviews about the seller, use get_seller_feedback.

Provide EITHER seller_id OR url — never both. You can discover a product's seller by calling get_product_offers first. Costs 1 credit.

Input parameters:

- `domain` (string): Amazon marketplace domain extension. Determines the regional Amazon site the data is fetched from. Use the domain that matches the user's market — prices, availability and rankings differ across mark…
- `language` (string): Language code for the Amazon page, in locale format (e.g. en_US, de_DE, tr_TR). Affects the language of titles, descriptions and reviews in the response.
- `seller_id` (string): Amazon's unique seller identifier (e.g. A1MCYUGJD2ILFU). Found in seller profile URLs as the 'seller=' or 'me=' parameter.
- `url` (string): Full Amazon seller profile or storefront URL (e.g. https://www.amazon.com/sp?seller=A1MCYUGJD2ILFU).

### `get_seller_products` (~439 tokens)

Extract a seller's full product catalog: every ASIN they sell with brand, category, price, Prime status, variant counts, and rating data. Also returns dynamic refinement filters (department, shipping, sustainability) for drilling into the catalog.

Use this tool for competitor inventory analysis, stock monitoring, and pricing-strategy research. If you need the seller's legal identity or reputation instead of their products, use get_seller_profile.

Each page costs 1 credit. Start with one page and use sort_by (e.g. 'exact-aware-popularity-rank' for best sellers first) to surface the most relevant products early. Provide EITHER seller_id OR url — never both.

Input parameters:

- `domain` (string): Amazon marketplace domain extension. Determines the regional Amazon site the data is fetched from. Use the domain that matches the user's market — prices, availability and rankings differ across mark…
- `exclude_refinements` (boolean): If true, omits the refinement filter list from the response, reducing payload size. Default false.
- `language` (string): Language code for the Amazon page, in locale format (e.g. en_US, de_DE, tr_TR). Affects the language of titles, descriptions and reviews in the response.
- `max_page` (integer): Ending page number. Each page costs 1 credit; max 5 pages per request. Default 1.
- `min_page` (integer): Starting page number. Default 1.
- `seller_id` (string): Amazon's unique seller identifier (e.g. A1MCYUGJD2ILFU). Found in seller profile URLs as the 'seller=' or 'me=' parameter.
- `sort_by` (string): Catalog ordering. 'featured-rank' is default; 'exact-aware-popularity-rank' sorts by popularity (best sellers first); 'price-asc-rank'/'price-desc-rank' by price; 'date-desc-rank' by newest.
- `url` (string): Full Amazon seller profile or storefront URL (e.g. https://www.amazon.com/sp?seller=A1MCYUGJD2ILFU).

### `get_seller_feedback` (~337 tokens)

Read individual buyer feedback entries for an Amazon seller: star ratings, comment text, and dates — filterable by rating range and time period. This is the reputation deep-dive tool.

Use this tool when the user wants to read actual buyer comments about a seller, analyze complaint patterns, or audit service quality. For aggregate reputation scores (30/90/365-day percentages) without individual comments, get_seller_profile is sufficient and cheaper in context.

Each page costs 1 credit. To find dissatisfied customers, set max_rating to 3 instead of paging through everything.

Input parameters:

- `domain` (string): Amazon marketplace domain extension. Determines the regional Amazon site the data is fetched from. Use the domain that matches the user's market — prices, availability and rankings differ across mark…
- `history_range` (string): Time period filter: '1' or '3' or '12' for months, 'all' for everything. Default 'all'.
- `max_page` (integer): Ending page number. Each page costs 1 credit; max 5 pages per request. Default 1.
- `max_rating` (integer): Maximum star rating to include (1-5). Set to 3 to focus on negative feedback. Default 5.
- `min_page` (integer): Starting page number. Default 1.
- `min_rating` (integer): Minimum star rating to include (1-5). Default 1.
- `seller_id` (string, required): Amazon's unique seller identifier (e.g. A1MCYUGJD2ILFU). Found in seller profile URLs as the 'seller=' or 'me=' parameter.

### `list_operations` (~90 tokens)

List all Easyparser operations available in this server, with their parameters, credit costs, and example use cases. Works WITHOUT an API key — call this first to understand what the server can do, or when you are unsure which tool fits the user's question. Also returns the list of supported Amazon marketplace domains.

Input parameters:

- `operation` (string): Optional. Get the usage guide for one operation instead of the whole catalog.

### `list_bulk_jobs` (~338 tokens)

List the user's bulk extraction jobs with their progress: operation, domain, status, total/completed/failed/invalid item counts, and timestamps. This reads the SAME data as the Bulk Requests page in the Easyparser web app — so it can see and track jobs the user started from the app UI, not just jobs submitted through this MCP server.

Use this tool when the user asks about their bulk jobs: "is my job done?", "what bulk jobs are running?", "did the DETAIL batch finish?". Each row includes a group_id — pass it to get_bulk_job_items to drill into individual items, or to get_bulk_webhook_logs to check webhook deliveries.

Statuses: pending (queued), processing (running), completed (all items succeeded), partial_success (some items failed or were dropped — check failed_items/invalid_items counts), failed. This tool is free of per-call credits (monitoring endpoints do not consume credits).

Input parameters:

- `bulk_request_id` (string): Look up a specific job by its bulk_request_id (returned when the job was submitted).
- `domain` (string): Filter by marketplace domain.
- `limit` (integer): Items per page (max 50). Default 25 — keep it small to save context.
- `operation` (string): Filter by operation type, e.g. DETAIL or SEARCH.
- `page` (integer): Page number. Default 1.
- `sort_direction` (string): Sort by creation time. 'desc' (newest first) is default.
- `status` (string): Filter by job status: pending, processing, completed, partial_success (some items failed), failed.

### `get_bulk_job_items` (~348 tokens)

Inspect the individual items inside a bulk job: each item's input value (ASIN, keyword, seller ID...), its status (success/failed/invalid/pending/processing), error message if it failed, credit cost, and completion time.

Use this tool to debug a job after list_bulk_jobs shows failed_items or invalid_items > 0 — filter with status='failed' or status='invalid' to see exactly which inputs failed and why. Use search_key to locate one specific ASIN inside a large job. The item's item_id can be used with the Data Service (GET /v1/queries/{id}) to fetch its parsed result.

This tool is free of per-call credits (monitoring endpoints do not consume credits).

Input parameters:

- `date_from` (string): ISO date lower bound, e.g. 2026-08-01.
- `date_to` (string): ISO date upper bound.
- `group_id` (string, required): The job's group_id — get it from list_bulk_jobs (each job row has one). Identifies which job's items to inspect.
- `limit` (integer): Items per page (max 50). Default 25 — keep it small to save context.
- `page` (integer): Page number. Default 1.
- `search_key` (string): Search within item values (e.g. a specific ASIN) to find one item in a large job.
- `sort_direction` (string): Sort by creation time. 'desc' (newest first) is default.
- `status` (string): Filter items by outcome. Use 'failed' or 'invalid' to debug a partial_success job; omit to see everything.

### `get_bulk_item_result` (~226 tokens)

Fetch the parsed result data of a single bulk job item — the actual Amazon data that item produced (product detail, search results, seller profile, etc., depending on the job's operation). This is the same data shown in the item result modal on the Bulk Requests page of the web app.

Use this tool after get_bulk_job_items, when the user wants to see the DATA behind a specific item, not just its status. Typical flow: list_bulk_jobs → get_bulk_job_items → get_bulk_item_result.

IMPORTANT: bulk results are retained for 24 HOURS after the job completes, then they expire. If the item's data has expired, the tool returns a clear message — suggest re-running that item through the matching real-time tool (e.g. get_product_detail for a DETAIL item) to regenerate the data. This tool is free of per-call credits.

Input parameters:

- `item_id` (string, required): The item_id of a bulk job item — get it from get_bulk_job_items (each item row has one). This is the same ID the Data Service calls a query ID.

### `get_bulk_webhook_logs` (~264 tokens)

Check webhook delivery logs for bulk jobs: whether the completion notification was delivered to the user's callback_url, delivery status, and timestamps. Use this when a job shows as completed but the user's system never received the webhook — the classic "job finished but my integration didn't fire" debugging case.

Scope to one job with group_id (from list_bulk_jobs), or omit it to scan recent deliveries across all jobs. This tool is free of per-call credits.

Input parameters:

- `bulk_request_id` (string): Filter by the job's bulk_request_id.
- `date_from` (string): ISO date lower bound.
- `date_to` (string): ISO date upper bound.
- `group_id` (string): Scope logs to one job's group_id. Omit to see recent webhook deliveries across all jobs.
- `limit` (integer): Items per page (max 50). Default 25 — keep it small to save context.
- `page` (integer): Page number. Default 1.
- `request_id` (string): Filter by an individual request ID.
- `sort_direction` (string): Sort by creation time. 'desc' (newest first) is default.
- `status` (string): Filter by delivery status (e.g. 'success', 'failed').

### `check_credits` (~106 tokens)

Check the Easyparser account: current plan, credit balance (used/remaining/limit), credit reset date, per-minute rate limits, and this month's daily usage breakdown by operation. FREE — this calls the Account API and consumes no credits.

Use this before running expensive multi-page or 12-month-history jobs, when the user asks about their quota or plan, or to analyze usage patterns (e.g. 'which operation consumed the most credits this month?'). Requires an API key.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-easyparser-easyparser/easyparser-mcp#diagnostics

## Score history

- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 75
- 2026-09-15: 74
- 2026-09-14: 74
- 2026-09-13: 73
- 2026-09-12: 73
- 2026-09-11: 72
- 2026-09-10: 72
- 2026-09-09: 68
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 68
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 68
- 2026-09-02: 53

## Common questions

### What is the Easyparser — Amazon Product & Seller Data MCP server?

Easyparser — Amazon Product & Seller Data is an MCP server listed in the public MCP registry as com.easyparser/easyparser. Real-time Amazon product, seller, and search data for AI agents across 21 marketplaces. This page covers its npm package (easyparser-mcp).

### Is the Easyparser — Amazon Product & Seller Data MCP server safe to use?

Easyparser — Amazon Product & Seller Data scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Easyparser — Amazon Product & Seller Data MCP server expose?

Easyparser — Amazon Product & Seller Data exposes 16 tools: get_product_detail, get_product_offers, search_products, lookup_product, get_sales_history, and 11 more. Their descriptions and schemas cost roughly 4,852 tokens of context every time the server is loaded.

### Is the Easyparser — Amazon Product & Seller Data MCP server still maintained?

Easyparser — Amazon Product & Seller 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 Easyparser — Amazon Product & Seller Data MCP server under?

Easyparser — Amazon Product & Seller 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.

## Links

- npm package: https://www.npmjs.com/package/easyparser-mcp
- Socket report: https://socket.dev/npm/package/easyparser-mcp
- Repository: https://github.com/easyparser-com/mcp-easyparser
- Website: https://easyparser.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-easyparser-easyparser/easyparser-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-easyparser-easyparser/easyparser-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-easyparser-easyparser/easyparser-mcp