Amazon review mining for AI agents — complaint detection, sentiment trends, complaint topics.
About
Amazon review mining for AI agents — complaint detection, sentiment trends, complaint topics. A differentiated review-mining MCP server with 5 tools (get_product_reviews, mine_complaints, review_sentiment_summary, top_complaint_topics, review_mining_report) that turns Amazon product reviews into structured complaint and sentiment reports. Runs over stdio via npx; starts without an API key and only live data calls need a Pangolinfo API key. Free test quota, then pay-as-you-go credits.
Security Report
This is a review-mining MCP server that bridges to Pangolinfo's hosted Amazon review API using a Bearer key read from the environment, with local keyword-based complaint analysis and no evident exfiltration, shell execution, or hardcoded secrets. Findings are limited to minor items: the test file is truncated so its full contents were not verified, the API key is sent to a configurable PANGOLINFO_MCP_URL endpoint, and the keyword complaint heuristic is simplistic. Permissions (network_http and env_vars) match the server's stated purpose. Package verification found 1 issue.
9 files analyzed · 4 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
Environment variable: PANGOLINFO_API_KEY
Sign up freeHow to Install
Install command not verified. See the repository for install instructions.
View repositoryGetting Started
Once installed, try these example prompts and explore these capabilities:
- 1Tool: get_product_reviews: Fetch Amazon product reviews for analysis
- 2Tool: mine_complaints: Extract complaints from Amazon product reviews
- 3Tool: review_sentiment_summary: Summarize sentiment trends across reviews
- 4Tool: top_complaint_topics: Find the most common complaint topics
- 5Tool: review_mining_report: Generate a structured complaint and sentiment report
Documentation
View on GitHubFrom the project's GitHub README.
Pangolinfo Review Mining MCP
A differentiated, review-mining-only MCP server for Amazon product reviews. It mines what buyers complain about, how sentiment trends, and which complaint themes dominate — it does not duplicate the general Pangolinfo Amazon Data MCP.
Pangolinfo Amazon Review API provides the Amazon review data used by this MCP.
How it differs from the general Amazon Data MCP
| General Amazon Data MCP | This Review Mining MCP | |
|---|---|---|
| Scope | 19+ tools: product search, product detail, best sellers, new releases, sellers, categories, niches, WIPO, SERP, Alexa | 5 tools, reviews only |
| Intent | General Amazon commerce intelligence | Review mining: complaints, sentiment, complaint topics |
| Analysis | Returns raw data | Local analysis on top of fetched reviews (keyword-theme tagging, distribution, monthly trend, combined report) |
| Upstream | Hosted Pangolinfo MCP server | Same hosted server's get_amazon_reviews tool, as an MCP client |
If you need product search or anything beyond reviews, use the general MCP. If you need to know what buyers complain about and how that changes over time, use this one.
Architecture
MCP client (Claude Code, Cursor, Codex, ...)
└─ stdio ─► this server (src/index.ts)
└─ Streamable HTTP MCP client ─► https://mcp.pangolinfo.com/mcp
└─ upstream tool: get_amazon_reviews
└─ local analysis (src/analysis.ts): tagging, sentiment, topics
The server is a bridge plus analysis. It stores no API key and no
review data; the key is sent only as an Authorization: Bearer header
to the hosted server, taken from the environment.
Why a bridge instead of direct REST calls: the Pangolinfo docs page for
the Review API lists parameters and response fields, but its request-URL
and example blocks did not survive text extraction, so the direct REST
endpoint is unconfirmed and deliberately not hardcoded here. The
bridge path uses only confirmed facts: the hosted endpoint
(https://mcp.pangolinfo.com/mcp, from the official amazon-data-mcp
README) and the upstream get_amazon_reviews tool name + input schema
(confirmed live via tools/list on 2026-10-26, a free metadata call).
See TODOs below for the direct-REST follow-up.
Setup
Requirements: Node.js 18 or newer (developed/tested on Node 24).
npm install
npm run build
Run (live mode):
export PANGOLINFO_API_KEY="your-key-here" # never commit a real key
node dist/src/index.js
Without a key the server still starts and answers initialize and tools/list; live tool calls fail with a clear message until PANGOLINFO_API_KEY is set.
Run (mock mode, no network, no key — for tests and demos):
PANGOLINFO_REVIEW_MINING_MOCK=1 node dist/src/index.js
MCP client configuration (example, Claude Code style):
{
"mcpServers": {
"pangolinfo-review-mining": {
"command": "node",
"args": ["/absolute/path/to/pangolinfo-review-mining-mcp/dist/src/index.js"],
"env": { "PANGOLINFO_API_KEY": "your-key-here" }
}
}
}
Environment variables:
| Variable | Required | Purpose |
|---|---|---|
PANGOLINFO_API_KEY | Yes (live mode) | Bearer token for the hosted Pangolinfo MCP server |
PANGOLINFO_MCP_URL | No | Upstream MCP endpoint; default https://mcp.pangolinfo.com/mcp |
PANGOLINFO_REVIEW_MINING_MOCK | No | =1 enables mock mode (mocked reviews, no network) |
Tools (5, all review-mining only)
| Tool | What it does | Key inputs |
|---|---|---|
get_product_reviews | Paginated review fetch for one ASIN, with billing (pointCost) reported verbatim | asin (required), site, pageCount (1–10), filterByStar, sortBy, mediaType |
mine_complaints | Complaint signals from negative (critical, 1–3 star) reviews, each tagged with themes + firing keyword; optional minHelpful filter | asin, site, pageCount, minHelpful |
review_sentiment_summary | Rating distribution, average star, negative/critical/positive shares, monthly trend | asin, site, pageCount |
top_complaint_topics | Ranked complaint themes with counts, shares, example titles | asin, site, pageCount, topN |
review_mining_report | Combined per-ASIN summary: totals, sentiment, top topics, most-endorsed complaints, billing; cites the Oct 12 baseline for B0FQFB8FMG as historical reference only | asin, site, pageCount |
Complaint themes (English keyword heuristic, v1 — transparent, not a
classifier): quality_defect, battery_power, connectivity,
comfort_fit, sound_quality, shipping_delivery, returns_refunds,
value_price, authenticity, app_software. Every match reports the
keyword that fired.
Marketplaces (site): amz_us (default), amz_de, amz_uk, amz_jp,
amz_fr, amz_it, amz_es, amz_br, amz_au, amz_mx, amz_in,
amz_eg, amz_ae, amz_ca.
Billing
- The Review API is documented at 5 credits/page (docs "积点消耗:
5个/次" and per-page billing in
bizContext.pageCount), and a measured Oct 2026get_amazon_reviewscall returnedpointCost: 5for one page. - Discrepancy flagged: the upstream MCP tool description currently
states 10 credits/page. This server does not resolve that
discrepancy by assertion — every tool reports
pointCostexactly as returned by the upstream response, and the billing note in each response names both figures. - Free tier: 60 credits/month, recurring. At the measured 5/page rate
that covers ~12 review pages/month; budget
pageCountaccordingly.review_mining_reportmakes two upstream fetches (all_stars + critical), so it costs twice one fetch. - The stored Pangolinfo API key expired (measured 2026-10-24). Live end-to-end testing is pending on the key being reconnected; see TEST_REPORT.md.
Tests
npm test # builds, then runs node --test on dist/test/
17 tests, all passing at build time (see TEST_REPORT.md): analysis
unit tests, tool-handler tests against the mocked upstream, the Oct 12
baseline fixture test, and a stdio smoke test that spawns the real
server in mock mode and speaks MCP JSON-RPC to it. All test review
data is mocked (synthetic authors "Mock Reviewer A" …); the only real
measured numbers in the repo are the aggregate baseline in
fixtures/airpods-pro-3-baseline.json (4,268 total / 1,392 negative
reviews for ASIN B0FQFB8FMG, measured 2026-10-12, reference only).
Limitations (read before presenting results as fact)
- Complaint tagging is an English keyword heuristic, not sentiment ML. Non-English reviews will under-match until lexicons for their languages are added.
- Star values come from strings like "5.0 out of 5 stars"; unparseable
stars fall into
unknownand are excluded from averages. - Dates come from strings like "October 14, 2026"; unparseable dates
fall into the
unknownmonthly bucket. totalReviewsis returned by upstream as a string and may be empty when unavailable; it is passed through, not computed.review_mining_reportfetches all_stars + critical, so its review counts are per-fetch, not a single de-duplicated sample.
Publication status (2026-10-26)
mcprush accepts MCP servers or agent skills only (verified 2026-10-26:
its server wizard requires a repo / npm / PyPI / container / hosted MCP
endpoint and passes initialize + tools/list verification).
- GitHub repo: live at https://github.com/Pangolin-spg/pangolinfo-review-mining-mcp
- npm package:
pangolinfo-review-mining-mcp0.1.1, published 2026-10-26 (0.1.0 was the first publish the same day; 0.1.1 adds themcpNamefield required by the MCP Registry) - mcprush listing: submitted 2026-10-26, in review (expected URL: https://mcprush.com/pangolin-spg/pangolinfo-review-mining-mcp)
- Server-card info needed: name, one-line description, and a paragraph of at least 120 characters on what it does and who it is for.
- Pricing: free plan (or priced plans with name, monthly price, call allowance); review takes up to two working days.
- No video/intro URL field was visible in the submission form's expanded steps during the read-only check; if one appears, the project's intro videos are the Pangolinfo EN/ZH videos on file.
- Backlink rule (standing): any link back to pangolinfo.com content in
a listing must carry
?utm_source=<platform>&utm_medium=referral(plusutm_content=<product>when one platform carries several products) for GA4 referral attribution.
TODOs / unconfirmed items
- Direct REST endpoint (unconfirmed): the docs page's request-URL and example blocks did not extract, and no workspace file records the Review API's REST URL. The bridge design avoids needing it, but a direct-REST mode should not be added until the URL is confirmed from docs or a measured call.
- Live end-to-end test (done 2026-10-26): verified with a temporary
7-day key:
get_product_reviews+mine_complaintson ASIN B0FQFB8FMG, 5 credits/page each, 4,446 total reviews / 1,457 critical at time of test. - Billing discrepancy (resolved 2026-10-26): live
pointCost= 5/page; the upstream tool description's 10/page is stale. - Publish (done 2026-10-26): GitHub repo live, npm 0.1.0 published, mcprush listing submitted (in review).
Reviews
No reviews yet
Be the first to review this server!
Version History
More Data & Analytics MCP Servers
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Lharries · Communication
Read, search, and send WhatsApp messages through your AI assistant
FinAgent
Freeby mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.
Memory
Freeby Modelcontextprotocol · Productivity
Knowledge graph-based persistent memory across sessions