Amazon review intelligence via Shulex OpenAPI. 10 marketplaces, verified-purchase & Vine signals.
Agent-native voice-of-customer for e-commerce. Drop in an ASIN or a CSV — get sentiment, pain points, copy-ready listing improvements, and a black-gold HTML dashboard. 6 MCP tools. Backed by the most stable Amazon review data layer. ↑ Sample dashboard: B08N5WRWNW · 100 reviews · sentiment + pain points + listing improvements, generated by renderdashboard. Two inputs, six tools, three outputs.…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Agent-native voice-of-customer for e-commerce. Drop in an ASIN or a CSV — get sentiment, pain points, copy-ready listing improvements, and a black-gold HTML dashboard. 6 MCP tools. Backed by the most stable Amazon review data layer. ↑ Sample dashboard: B08N5WRWNW · 100 reviews · sentiment + pain points + listing improvements, generated by render_dashboard. Two inputs, six tools, three outputs. Inputs — Amazon ASIN (auto-fetched via Shulex VOC OpenAPI, 10 markets) or any review CSV / Excel…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.