AMZScout Skill + MCP
REMOTE · CHATBOT.AMZSCOUT.NET · SCANNED AUG 12
Amazon research from AMZScout data: analyze products & niches, keywords/PPC, and brand catalogs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2207 tokens (~183/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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · chatbot.amzscout.net
claude mcp add --transport http amzscout-corp-amzscout-skill-mcp https://chatbot.amzscout.net/mcp
[mcp_servers.amzscout-corp-amzscout-skill-mcp] url = "https://chatbot.amzscout.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"amzscout-corp-amzscout-skill-mcp": {
"type": "remote",
"url": "https://chatbot.amzscout.net/mcp",
"enabled": true
}
}
} openclaw mcp add amzscout-corp-amzscout-skill-mcp --url https://chatbot.amzscout.net/mcp --transport streamable-http
mcp_servers:
amzscout-corp-amzscout-skill-mcp:
url: "https://chatbot.amzscout.net/mcp" {
"mcpServers": {
"amzscout-corp-amzscout-skill-mcp": {
"type": "http",
"url": "https://chatbot.amzscout.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 11 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 4 Aug 26 77
First indexed and scored.
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 12 Aug 2026 · Probed https://chatbot.amzscout.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chatbot.amzscout.net | CN=YE1,O=Let's Encrypt,C=US | 25 Jul 2026 | 23 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6166ec4ef570a66653d3c63a5a67b0270dd |
| SANs: chatbot.amzscout.net | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC secure
Validation of chatbot.amzscout.net. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| amzscout.net. | present | 17626, 55058 | 13, 13 | Verified |
| chatbot.amzscout.net. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://chatbot.amzscout.net/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://chatbot.amzscout.net/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Protected resource metadata
| Document | https://chatbot.amzscout.net/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://chatbot.amzscout.net/mcp |
| Authorisation server | https://amzscout.net/auth |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://chatbot.amzscout.net/mcp | Verified | 200 | |
| http (plaintext) | http://chatbot.amzscout.net/mcp | HTTPS enforced | 301 | https://chatbot.amzscout.net/mcp |
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.
amzscout_analyze_niche ~199
Market snapshot for an Amazon niche/keyword — top products by revenue plus computed aggregates (price/sales/revenue/review distributions, revenue concentration, brand spread). Pure data fetch (no AI analysis) — reason over the returned data yourself. How to use: judge niche attractiveness — demand concentration (revenueTop5SharePercent: high = winner-takes-all, low = fragmented/open), price bands and where the money sits, review counts as entry moats, brand dominance vs no-name spread, and standout products (high sales + weak rating/reviews = displacement opportunity).
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many top products to pull from Amazon (5–100). |
| filters | object | – | Filter products by price / sales / revenue / reviews / rating |
| keyword | string | yes | Niche, category, or product search keyword |
| marketplace | string | – | Amazon marketplace code. Default COM (United States). |
No output schema declared.
No examples provided.
amzscout_analyze_product ~160
Full raw data for a single Amazon product by ASIN — price, estimated sales/revenue, reviews, rating, listing quality, sellers, plus sales/price/revenue history when available. Pure data fetch (no AI analysis) — reason over the returned data yourself. How to use: audit the product like a sourcing analyst — demand trend & seasonality from sales history, pricing direction & margin risk from price history and FBA fees, competition from sellers/reviews, listing quality from LQS, then conclude whether a new seller should enter (GO / NO-GO and what it would take).
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | yes | Amazon Standard Identification Number |
| marketplace | string | – | Amazon marketplace code. Default COM (United States). |
No output schema declared.
No examples provided.
amzscout_analyze_product_set ~172
Raw data across an explicit set of 2–100 ASINs — product rows plus computed aggregates (price/sales/revenue/review distributions, revenue concentration, brand spread). Pure data fetch (no AI analysis) — reason over the returned data yourself. To discover products from a keyword instead, analyzeNiche is the equivalent. How to use: treat the set as a mini-market — segment products into groups, spot where demand concentrates, flag outliers (price, sales, review anomalies), and summarize group-level signals.
| Name | Type | Req | Description |
|---|---|---|---|
| asins | array | yes | 2–100 ASINs to fetch as a set (B0XXXXXXXX). 0/O-swapped prefixes are auto-corrected. |
| marketplace | string | – | Amazon marketplace code. Default COM (United States). |
No output schema declared.
No examples provided.
amzscout_compare_niches ~190
Raw head-to-head data for 2–5 Amazon niches / category keywords — per-niche product sets plus computed aggregates (price/sales/revenue distributions, revenue concentration, brand spread). Pure data fetch (no AI analysis) — do the comparison yourself. For ASINs, compareProducts is the equivalent. How to use: weigh demand (total est. revenue/sales) against competition (review levels, brand concentration) and price levels per niche, then give a verdict on which niche is the better opportunity for a new seller and under what conditions.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Products fetched per niche (default 10). |
| keywords | array | yes | 2–5 niches / category keywords to compare head-to-head, e.g. ["yoga mat", "resistance bands"]. |
| marketplace | string | – | Amazon marketplace code. Default COM (United States). |
No output schema declared.
No examples provided.
amzscout_compare_products ~176
Side-by-side raw data for 2–5 Amazon products by ASIN — price, sales/revenue estimates, reviews, listing quality, plus history when available. Pure data fetch (no AI analysis) — do the comparison yourself. For a single ASIN, analyzeProduct is the equivalent. How to use: compare demand (est. sales), revenue, review moat and rating, price positioning, listing quality, and history trends (growing vs declining), then give a verdict on which product is the stronger opportunity and why.
| Name | Type | Req | Description |
|---|---|---|---|
| asins | array | yes | 2–5 ASINs to compare. Each must be a real Amazon ASIN (B0XXXXXXXX). 0/O-swapped prefixes are auto-corrected. |
| marketplace | string | – | Amazon marketplace code. Default COM (United States). |
No output schema declared.
No examples provided.
amzscout_find_by_brand ~169
List products under a specific Amazon brand. Pre-validates the brand name via cached AI check, then filters keyword-search results to rows whose `brand` field actually matches. On no-match, returns the brands that did appear in the keyword pool so callers can suggest alternatives. How to use: assess the brand's Amazon footprint — lineup breadth, price range, which products carry the revenue, and how strong its review moat is.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Amazon brand name to search by |
| count | integer | – | How many products to return (1–100) |
| filters | object | – | Filter products by price / sales / revenue / reviews / rating |
| marketplace | string | – | Amazon marketplace code. Default COM (United States). |
| sort | string | – | – |
No output schema declared.
No examples provided.
amzscout_get_keywords ~174
Amazon keyword / SEO / PPC data for either a single product (ASIN-scope — terms the product ranks for) or a niche/category (keyword-scope — search data around the term). Returns keyword rows with search volume, CPC, and competition where available. Pure data fetch (no AI analysis). How to use: pick high-volume / low-competition terms for SEO and PPC targeting, use CPC as ad-cost pressure, sum search volumes to gauge niche demand, and for ASIN-scope check organic vs sponsored ranks to spot listing-optimization gaps.
| Name | Type | Req | Description |
|---|---|---|---|
| asin | string | – | ASIN-scope: keywords this product ranks for. |
| keyword | string | – | Keyword-scope: search data around this niche term. |
| marketplace | string | – | Amazon marketplace code. Default COM (United States). |
No output schema declared.
No examples provided.
amzscout_recommend_tool ~99
Given a user use-case, returns the AMZScout tools & Sellerhook services catalog (with tracking links) so you can recommend the right AMZScout product/feature. Use for "which AMZScout tool should I use for X" questions.
| Name | Type | Req | Description |
|---|---|---|---|
| useCase | string | yes | What the user is trying to do (e.g. "find low-competition products", "validate a supplier", "track BSR"). |
No output schema declared.
No examples provided.
amzscout_search_knowledge ~91
TF-IDF search across the AMZScout knowledge base (Amazon-seller tutorials, brand reference, glossary). Returns the top-K relevant chunks with title, source URL and text. Use this to ground answers in factual material.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search phrase. 2-300 chars. |
| topK | integer | – | How many knowledge chunks to return (1–20) |
No output schema declared.
No examples provided.
amzscout_search_products ~190
Keyword search against Amazon — returns the top N products with price, sales, revenue, reviews, rating. Pure data fetch (no AI analysis). Best when you need raw product rows (specific sort order or filters); analyzeNiche additionally returns computed market aggregates on top of the rows. How to use: scan the rows for demand leaders, price clusters, and low-review listings that still sell — those are the entry-opportunity signals.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many products to return (1–100) |
| filters | object | – | Filter products by price / sales / revenue / reviews / rating |
| marketplace | string | – | Amazon marketplace code. Default COM (United States). |
| query | string | yes | Search keyword / phrase. |
| sort | string | – | Result sort order. revenue/sales/rating/reviews descending; price-low ascending; newest by first-listed date. |
No output schema declared.
No examples provided.
amzscout_usage ~78
The caller's AMZScout AI-agents token balance — remaining, used, and limit. Free — no tokens are charged for this call. How to use: answer "how many tokens do I have left", "what's my usage / balance / limit", or when a call fails on quota. Report the remaining figure first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
amzscout-agent ~148
AMZScout all-in-one Amazon research assistant. Ask anything in natural language ("Is B07GQF9D1Z worth selling?", "Analyze the yoga mat niche", "Find products for brand Anker") and it returns a finished analysis — it pulls live Amazon data and runs the right analyses internally, so no sub-tool selection is needed. Best for a hands-off answer; the granular amzscout_* tools are the alternative when step-by-step orchestration is preferred. Returns a complete, user-ready report.
| Name | Type | Req | Description |
|---|---|---|---|
| history | array | – | Optional prior turns for multi-turn context, oldest first. |
| message | string | yes | The question or request in natural language. |
No output schema declared.
No examples provided.