Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AMZScout Skill + MCP

REMOTE · CHATBOT.AMZSCOUT.NET

Amazon research from AMZScout data: analyze products & niches, keywords/PPC, and brand catalogs.

0 this week 36 Trust /100

Last scanned (21 hours ago)

Scores higher than 19% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security91
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Oct 26 36
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
  • 21 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “amzscout_analyze_product” rewrote its description, which is the text the model reads security
    • New tool “amzscout_advanced_product_data” functional
  • 17 Oct 26 0
    • Stability: fail → pass ▲ security
  • 13 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 0
    • Tool “amzscout_reseller_amazon” rewrote its description, which is the text the model reads security
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 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=YE2,O=Let's Encrypt,C=US 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA384 634dbebaaa82b4e6b83c0b52fa0c761d629
SANs: chatbot.amzscout.net
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of chatbot.amzscout.net. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
net. DS published 37331 13 Verified
amzscout.net. DS published 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 connection
HTTP status 401

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
www-authenticate Bearer resource_metadata="https://chatbot.amzscout.net/.well-known/oauth-protected-resource"

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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://chatbot.amzscout.net/mcp Auth required 401
http (plaintext) http://chatbot.amzscout.net/mcp HTTPS enforced 301 https://chatbot.amzscout.net/mcp
MCP tools · 14 exposed · ~3,997 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
amzscout_advanced_product_data ~525

Extra catalog facts about one Amazon ASIN that amzscout_analyze_product does not include: bullet features, materials, included components, ingredients, hazmat info, UPCs and manufacturer; on request also frequently-bought-together / bundle ASINs, listing videos, return rate, brand store link and buy box seller history. No sales, price or review numbers — those come from amzscout_analyze_product. Pure data fetch (no AI analysis). When to call: together with amzscout_analyze_product whenever the user asks about one specific product (same ASIN and marketplace), so the answer carries the listing facts as well as the numbers. Call WITHOUT `sections` by default (returns catalog + identifiers); add relations / media / buybox only when the question is about them. How to use: describe what the product actually is and how it is positioned — key features, materials, what is in the box, compliance flags (hazmat, ingredients) — and point out what a competing listing would need to match or beat. Present facts as written on the listing; do not invent missing ones. Marketplace: if the user has not named a country / Amazon domain in this conversation, ask them once which marketplace they work on and reuse that code for every later call in the chat; do not assume the US. Called without `marketplace`, this tool fetches nothing and answers "MARKETPLACE NEEDED". Money is in that marketplace's local currency.

NameTypeReqDescription
asinstringyesAmazon Standard Identification Number
marketplacestring–Amazon marketplace code — the one the user named, or the one they chose earlier in this conversation (ask once, then reuse it for every call). Never assume the US for an ASIN: without it, ASIN tools…
sectionsarray–Which data to return. Omit for the default (catalog + identifiers). Request others only when the question needs them — relations, media and buybox are slower. Options: "catalog" (bullet features, mat…

No output schema declared.

No examples provided.

amzscout_analyze_niche ~255

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).

NameTypeReqDescription
countinteger–How many top products to pull from Amazon (5–100).
filtersobject–Filter products by price / sales / revenue / reviews / rating
keywordstringyesNiche, category, or product search keyword
marketplacestring–Amazon marketplace code — the one the user named, or the one they chose earlier in this conversation (ask once, then reuse it for every call). Never assume the US for an ASIN: without it, ASIN tools…

No output schema declared.

No examples provided.

amzscout_analyze_product ~325

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). Listing facts (features, materials, ingredients, UPC, videos) are NOT here — they come from amzscout_advanced_product_data (call both for the same ASIN). Marketplace: if the user has not named a country / Amazon domain in this conversation, ask them once which marketplace they work on and reuse that code for every later call in the chat; do not assume the US. Called without `marketplace`, this tool fetches nothing and answers "MARKETPLACE NEEDED". Money is in that marketplace's local currency.

NameTypeReqDescription
asinstringyesAmazon Standard Identification Number
marketplacestring–Amazon marketplace code — the one the user named, or the one they chose earlier in this conversation (ask once, then reuse it for every call). Never assume the US for an ASIN: without it, ASIN tools…

No output schema declared.

No examples provided.

amzscout_analyze_product_set ~300

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. Marketplace: if the user has not named a country / Amazon domain in this conversation, ask them once which marketplace they work on and reuse that code for every later call in the chat; do not assume the US. Called without `marketplace`, this tool fetches nothing and answers "MARKETPLACE NEEDED". Money is in that marketplace's local currency.

NameTypeReqDescription
asinsarrayyes2–100 ASINs to fetch as a set (B0XXXXXXXX). 0/O-swapped prefixes are auto-corrected.
marketplacestring–Amazon marketplace code — the one the user named, or the one they chose earlier in this conversation (ask once, then reuse it for every call). Never assume the US for an ASIN: without it, ASIN tools…

No output schema declared.

No examples provided.

amzscout_compare_niches ~246

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.

NameTypeReqDescription
countinteger–Products fetched per niche (default 10).
keywordsarrayyes2–5 niches / category keywords to compare head-to-head, e.g. ["yoga mat", "resistance bands"].
marketplacestring–Amazon marketplace code — the one the user named, or the one they chose earlier in this conversation (ask once, then reuse it for every call). Never assume the US for an ASIN: without it, ASIN tools…

No output schema declared.

No examples provided.

amzscout_compare_products ~304

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. Marketplace: if the user has not named a country / Amazon domain in this conversation, ask them once which marketplace they work on and reuse that code for every later call in the chat; do not assume the US. Called without `marketplace`, this tool fetches nothing and answers "MARKETPLACE NEEDED". Money is in that marketplace's local currency.

NameTypeReqDescription
asinsarrayyes2–5 ASINs to compare. Each must be a real Amazon ASIN (B0XXXXXXXX). 0/O-swapped prefixes are auto-corrected.
marketplacestring–Amazon marketplace code — the one the user named, or the one they chose earlier in this conversation (ask once, then reuse it for every call). Never assume the US for an ASIN: without it, ASIN tools…

No output schema declared.

No examples provided.

amzscout_find_by_brand ~225

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.

NameTypeReqDescription
brandstringyesAmazon brand name to search by
countinteger–How many products to return (1–100)
filtersobject–Filter products by price / sales / revenue / reviews / rating
marketplacestring–Amazon marketplace code — the one the user named, or the one they chose earlier in this conversation (ask once, then reuse it for every call). Never assume the US for an ASIN: without it, ASIN tools…
sortstring––

No output schema declared.

No examples provided.

amzscout_get_keywords ~456

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). Pass BOTH `asin` and `keyword` to get the product's position for exactly that keyword (e.g. "organic rank of B0... for standing lamp") — the reply gives the exact-match row as the answer and lists look-alike keywords with extra symbols separately; never report a look-alike's rank for the requested keyword. Every keyword row carries search volume, average sales, CPC and trend; ASIN-scope rows ALSO carry this product's own placement for that term — organic rank + page, sponsored page, and relevance score (rows the product does not rank for are marked "not ranking"). 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. Marketplace: if the user has not named a country / Amazon domain in this conversation, ask them once which marketplace they work on and reuse that code for every later call in the chat; do not assume the US. Called without `marketplace`, this tool fetches nothing and answers "MARKETPLACE NEEDED". Money is in that marketplace's local currency.

NameTypeReqDescription
asinstring–ASIN-scope: keywords this product ranks for. Together with `keyword`: this product's position for exactly that keyword.
keywordstring–Keyword-scope: search data around this niche term. Together with `asin`: the exact keyword to look up for the product (pass it exactly as the user wrote it — no added symbols or words).
marketplacestring–Amazon marketplace code — the one the user named, or the one they chose earlier in this conversation (ask once, then reuse it for every call). Never assume the US for an ASIN: without it, ASIN tools…

No output schema declared.

No examples provided.

amzscout_locate_asin ~263

Find which Amazon marketplaces list an ASIN, and get its product link on every marketplace (amazon.com, .co.uk, .de, .fr, .it, .es, .ca, .com.mx, .com.br, .in, .co.jp, .com.au, .ae, .sa). For each marketplace where it is listed: title, price in that marketplace's local currency, estimated monthly sales. Paid: 1 000 tokens per marketplace checked, per ASIN (14 000 per ASIN). How to use: call it ONLY when the user asks where / on which Amazon marketplaces a product is sold, or wants its links on other marketplaces. Do NOT call it just to choose a marketplace for analysis — for that, ask the user once which marketplace they work on and reuse it for the whole conversation. Present the result as a list (country, link, local price, sales); if the user then wants analysis, pass the marketplace they pick to amzscout_analyze_product / amzscout_get_keywords.

NameTypeReqDescription
asinsarrayyes1–5 ASINs to locate (B0 + 8 characters). Pass several only when they will be analyzed together.

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.

NameTypeReqDescription
useCasestringyesWhat 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_reseller_amazon ~584

Buy box, competing offers and price/rank statistics for one Amazon ASIN — who owns the buy box and at what price, how ownership has split between sellers, FBA vs FBM offer counts, the live offer list with seller names and ratings, price levels over 30/90/180/365 days with all-time extremes, sales-rank drops, out-of-stock share, and buy box ownership history. Built for reseller / online-arbitrage questions, not private-label research — for demand and revenue estimates use analyzeProduct instead. Pure data fetch (no AI analysis). IMPORTANT: call it first WITHOUT `sections` — the summary alone answers most questions, and the reply lists which sections hold data for this ASIN. Only request sections when the summary is not enough; asking for all six returns several KB of detail you will rarely need. How to use: judge whether the listing is worth reselling — Amazon in the buy box or a single seller holding most of it means little room, many FBA offers means price competition, high out-of-stock share means supply gaps you could fill, and rank drops indicate how fast it sells. Marketplace: if the user has not named a country / Amazon domain in this conversation, ask them once which marketplace they work on and reuse that code for every later call in the chat; do not assume the US. Called without `marketplace`, this tool fetches nothing and answers "MARKETPLACE NEEDED". Money is in that marketplace's local currency.

NameTypeReqDescription
asinstringyesAmazon Standard Identification Number
marketplacestring–Amazon marketplace code — the one the user named, or the one they chose earlier in this conversation (ask once, then reuse it for every call). Never assume the US for an ASIN: without it, ASIN tools…
sectionsarray–Which parts of the data to return. Omit for a compact summary plus the list of sections available — request specific sections only when the summary does not answer the question. Options: "buybox" (wh…

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.

NameTypeReqDescription
querystringyesSearch phrase. 2-300 chars.
topKinteger–How many knowledge chunks to return (1–20)

No output schema declared.

No examples provided.

amzscout_search_products ~246

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.

NameTypeReqDescription
countinteger–How many products to return (1–100)
filtersobject–Filter products by price / sales / revenue / reviews / rating
marketplacestring–Amazon marketplace code — the one the user named, or the one they chose earlier in this conversation (ask once, then reuse it for every call). Never assume the US for an ASIN: without it, ASIN tools…
querystringyesSearch keyword / phrase.
sortstring–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.

Install

How do I install the AMZScout Skill + MCP server?

AMZScout Skill + MCP is a hosted endpoint at https://chatbot.amzscout.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · chatbot.amzscout.net

# add to Claude Code
claude mcp add --transport http amzscout-corp-amzscout-skill-mcp 'https://chatbot.amzscout.net/mcp'
Common questions

What is the AMZScout Skill + MCP server?

AMZScout Skill + MCP is listed in the public MCP registry as io.github.amzscout-corp/amzscout-skill-mcp. Amazon research from AMZScout data: analyze products & niches, keywords/PPC, and brand catalogs. This page covers its hosted endpoint (https://chatbot.amzscout.net/mcp).

Is the AMZScout Skill + MCP server safe to use?

AMZScout Skill + MCP scores 36 out of 100 on VerifyMCP. 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 AMZScout Skill + MCP server expose?

AMZScout Skill + MCP exposes 14 tools: amzscout_analyze_product, amzscout_analyze_niche, amzscout_compare_products, amzscout_compare_niches, amzscout_analyze_product_set, and 9 more. Their descriptions and schemas cost roughly 3,997 tokens of context every time the server is loaded.

Does the AMZScout Skill + MCP server require authentication?

Yes. AMZScout Skill + MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the AMZScout Skill + MCP server still maintained?

AMZScout Skill + MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the AMZScout Skill + MCP server?

VerifyMCP ran 5 checks on AMZScout Skill + MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about AMZScout Skill + MCP: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.