Amazon Public Fetch MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PROXY | No | Optional HTTP or HTTPS proxy URL for Amazon fetches. Used if AMAZON_FETCH_PROXY and HTTPS_PROXY are not set. | |
| HTTPS_PROXY | No | Optional HTTP or HTTPS proxy URL for Amazon fetches. Used if AMAZON_FETCH_PROXY is not set. | |
| AMAZON_FETCH_PROXY | No | Optional HTTP or HTTPS proxy URL for Amazon fetches. Takes precedence over HTTPS_PROXY and HTTP_PROXY. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthB | What this connector can do right now: which fetch engines are installed, and the honest limits (public pages only; must run on a home/residential machine). |
| amazon_fetchA | Fetch a public Amazon URL (or a 10-char ASIN) through a local fetch ladder: httpx → curl_cffi → rnet → playwright. Uses fresh sessions. Stops on rate limits. Returns status, engine used, ASIN, titles, and size. Set include_html=true only when you need the raw page (large). max_engine caps the ladder (httpx|curl_cffi|rnet|playwright). |
| amazon_productB | Fetch a public Amazon product page and return a small summary: ASIN, title, visible price text, and feature bullets. Same ladder as amazon_fetch. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
health is clearly a diagnostic tool separate from fetching. amazon_fetch and amazon_product overlap because both can fetch Amazon product pages, but the descriptions clarify that amazon_product returns a focused product summary while amazon_fetch is the generic fetch ladder with optional raw HTML.
The names use mixed conventions: health is a bare noun, amazon_fetch follows a prefix_verb pattern, and amazon_product follows a prefix_noun pattern. They are still readable and grouped by the amazon_ prefix, but the verb/noun inconsistency prevents a higher score.
Three tools are well-scoped for a narrow public-Amazon fetch connector: one diagnostic, one generic fetcher, and one product-specific summarizer. Each tool has a clear role and there is no obvious bloat.
The surface covers health checking, generic URL/ASIN fetching, and product-page summarization, which are the core operations for this domain. A minor gap is that non-product Amazon pages only get the generic fetch output rather than richer summaries, but include_html and the generic fetcher provide a workaround.