Amazon Trends API
REMOTE · AMAZON.API.TRENDSAPI.AI
Amazon product search volume and best-seller trends. Free key at trendsapi.ai
Available components
Last scanned (13 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3086 tokens (~514/item across 6 items; 6 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 Management72
- Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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 →
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.
- 7 Nov 26 −11
- Authorization: partial → unverified ▼ security
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “trends___get_top_posts” was removed ▼ security
- Tool “trends___get_context” rewrote its description, which is the text the model reads security
- Tool “trends___get_growth” rewrote its description, which is the text the model reads security
- Tool “trends___get_time_series” rewrote its description, which is the text the model reads security
- Tool “trends___get_top_trends” rewrote its description, which is the text the model reads security
- Schema quality: 412 → 514 ▼ functional
- New tool “trends___get_reviews” functional
- “trends___get_context” added an optional parameter “hashtag” cosmetic
- “trends___get_context” reworded the description of “source” cosmetic
- “trends___get_growth” reworded the description of “source” cosmetic
- “trends___get_time_series” reworded the description of “source” cosmetic
- “trends___get_top_trends” reworded the description of “limit” cosmetic
- “trends___get_top_trends” reworded the description of “type” cosmetic
- 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
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 1 Nov 26 −1
- Tool “trends___get_top_trends” rewrote its description, which is the text the model reads security
- “trends___get_top_trends” reworded the description of “category” cosmetic
- “trends___get_growth” reworded the description of “country” cosmetic
- “trends___get_growth” reworded the description of “keyword” cosmetic
- “trends___get_growth” reworded the description of “source” cosmetic
- “trends___get_time_series” reworded the description of “country” cosmetic
- “trends___get_time_series” reworded the description of “keyword” cosmetic
- “trends___get_time_series” reworded the description of “source” cosmetic
- “trends___get_top_trends” reworded the description of “country” cosmetic
- “trends___get_top_trends” reworded the description of “type” cosmetic
- 26 Oct 26 0
- Tool “trends___get_growth” rewrote its description, which is the text the model reads security
- Tool “trends___get_top_trends” rewrote its description, which is the text the model reads security
- Tool “trends___get_usage” rewrote its description, which is the text the model reads security
- Schema quality: 1868 → 2421 ▼ functional
- New tool “trends___get_context” functional
- “trends___get_growth” added an optional parameter “country” cosmetic
- “trends___get_growth” added an optional parameter “language” cosmetic
- “trends___get_growth” added an optional parameter “resolution” cosmetic
- “trends___get_time_series” added an optional parameter “country” cosmetic
- “trends___get_time_series” added an optional parameter “language” cosmetic
- “trends___get_time_series” added an optional parameter “resolution” cosmetic
- “trends___get_growth” reworded the description of “keyword” cosmetic
- “trends___get_growth” reworded the description of “source” cosmetic
- “trends___get_time_series” reworded the description of “keyword” cosmetic
- “trends___get_time_series” reworded the description of “source” cosmetic
- “trends___get_top_posts” reworded the description of “source” cosmetic
- “trends___get_top_trends” reworded the description of “country” cosmetic
- 24 Oct 26 0
- Schema quality: 450 → 373 ▲ functional
- New tool “trends___get_usage” functional
- 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
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://amazon.api.trendsapi.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.trendsmcp.ai | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 27 Oct 2026 | 12 May 2027 | RSA 2048 | SHA256-RSA | c78cab3d4b806b29b68c5554a7dd0a3 |
| SANs: api.trendsmcp.ai, api.trendsapi.ai, *.api.hyperaware.live, api.superdemands.com, *.api.trendsconnector.com, api.whatstrending.si, *.api.trendsagents.com, *.api.superdemands.com, api.trendsconnector.com, *.api.whatstrending.si, *.api.trendsmcp.ai, api.hyperaware.live and 2 more | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of amazon.api.trendsapi.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| trendsapi.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://amazon.api.trendsapi.ai/mcp | Verified | 200 | |
| http (plaintext) | http://amazon.api.trendsapi.ai/mcp | HTTPS enforced | 301 | https://amazon.api.trendsapi.ai/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. 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 →
trends___get_context ~442
What people are posting, reading and betting about a keyword right now, or with hashtag=true the top TikTok and Instagram posts on one hashtag. Returns recent posts, videos, news stories, discussions and prediction markets per source, with engagement (views, likes, score) and top comments. Use it to explain why something is trending or what the conversation says; get_time_series and get_growth measure how much. Costs 1 request per data type (source or board) in the call; boards cost 1 request per 10 rows. Only data types that answer are charged; the answer says requests_charged. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.
| Name | Type | Req | Description |
|---|---|---|---|
| comments | integer | – | Top comments for the first N items of each source, 0 to 5. Default 2. Only for 'YouTube', 'TikTok', 'Instagram', 'X', 'Reddit', 'Bluesky', and 'Hacker News'. |
| days | integer | – | Look back this many days, 1 to 30. Default 7. |
| hashtag | boolean | – | true: treat keyword as one exact hashtag (with or without #) and return the platform's own top posts for it, instead of a keyword search. Only for 'TikTok', and 'Instagram'; other sources search the… |
| keyword | string | yes | Any name or phrase, e.g. 'nintendo switch 2'. |
| limit | integer | – | Items per source, 1 to 20. Default 10. |
| source | string | yes | One source, several comma-separated, or 'all': 'all' = 10 ('News', 'YouTube', 'TikTok', 'Instagram', 'X', 'Reddit', 'Bluesky', 'Hacker News', 'Polymarket', and 'GitHub'), costing 10. Valid: 'News', '… |
No output schema declared.
No examples provided.
trends___get_growth ~837
Point-to-point growth for a keyword on one or more sources. Each window is a preset string (12M, 3M, YTD, and the other listed periods). Values are on a 0-100 scale, plus absolute volume when available. Designed for growth questions; for charting or custom math, get_time_series provides the full series. App Downloads and App Rankings are keyword sources (Android bundle ID). They are not the App Store / Google Play live boards on get_top_trends. Costs 1 request per data type (source or board) in the call; boards cost 1 request per 10 rows. Only data types that answer are charged; the answer says requests_charged. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional ISO 3166-1 alpha-2 code (US, GB, JP). Aliases like 'UK' or 'United Kingdom' resolve too. Only for Google Search, Google Images, Google News, Google Shopping, YouTube, TikTok, and Pinterest.… |
| keyword | string | yes | What to look up. The string format is required by source. Standard sources (Google Search, Google Images, Google News, Google Shopping, YouTube, Wikipedia, TikTok, Amazon, Pinterest): any name or phr… |
| language | string | – | Optional language edition code (en, de, ja, pt). Only for Wikipedia. Default en; other languages are fetched live. |
| percent_growth | array | – | Growth windows. Default if omitted: ['12M']. Each item must be a preset string: '7D', '1W', '14D', '2W', '30D', '1M', '2M', '3M', '6M', '9M', '12M', '1Y', '18M', '24M', '2Y', '36M', '3Y', '48M', '4Y'… |
| resolution | string | – | Optional. 'weekly' (default, about 5 years) or 'daily' (last 90 days, fetched live). Only for Google Search, Google Images, Google News, Google Shopping, and YouTube. |
| source | string | yes | One source, comma-separated sources (e.g. 'Amazon, TikTok, YouTube'), or 'all': 'all' = 9 ('Google Search', 'Google Images', 'Google News', 'Google Shopping', 'YouTube', 'Wikipedia', 'TikTok', 'Amazo… |
No output schema declared.
No examples provided.
trends___get_reviews ~322
What customers say about a brand, app, product or place. Returns, per source, the matched listing with its all-time rating and review count, the newest reviews (stars, text, the company's reply) and a summary (average stars, star counts, share negative, share replied). Use it for brand sentiment and complaints; get_context covers social posts. Costs 1 request per data type (source or board) in the call; boards cost 1 request per 10 rows. Only data types that answer are charged; the answer says requests_charged. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Store country, ISO code (US, GB, DE). Default US. Only for 'App Store', 'Google Play', and 'Amazon'. |
| days | integer | – | Only reviews from the last N days, 1 to 365. Default 90. |
| keyword | string | yes | A brand, app, product or place name, e.g. 'notion'. Each source matches it to one listing and returns that listing as subject; check it is the one you meant. |
| limit | integer | – | Reviews per source, newest first, 1 to 20. Default 10. |
| source | string | yes | One source, several comma-separated, or 'all': 'all' = 3 ('App Store', 'Google Play', and 'Amazon'), costing 3. Valid: 'App Store', 'Google Play', 'Amazon'. |
No output schema declared.
No examples provided.
trends___get_time_series ~633
Full historical series for one keyword on one or more sources (0-100 values, plus volume when available). Suited for charting or custom math. Live 'what's trending now' boards are on get_top_trends. get_growth answers most growth questions with less data. Costs 1 request per data type (source or board) in the call; boards cost 1 request per 10 rows. Only data types that answer are charged; the answer says requests_charged. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional ISO 3166-1 alpha-2 code (US, GB, JP). Aliases like 'UK' or 'United Kingdom' resolve too. Only for Google Search, Google Images, Google News, Google Shopping, YouTube, TikTok, and Pinterest.… |
| keyword | string | yes | What to look up. The string format is required by source. Standard sources (Google Search, Google Images, Google News, Google Shopping, YouTube, Wikipedia, TikTok, Amazon, Pinterest): any name or phr… |
| language | string | – | Optional language edition code (en, de, ja, pt). Only for Wikipedia. Default en; other languages are fetched live. |
| resolution | string | – | Optional. 'weekly' (default, about 5 years) or 'daily' (last 90 days, fetched live). Only for Google Search, Google Images, Google News, Google Shopping, and YouTube. |
| source | string | yes | One source, several comma-separated (one series each), or 'all': 'all' = 9 ('Google Search', 'Google Images', 'Google News', 'Google Shopping', 'YouTube', 'Wikipedia', 'TikTok', 'Amazon', and 'Pinter… |
No output schema declared.
No examples provided.
trends___get_top_trends ~802
Live top-trending boards: one feed type, several, or 'all'. No keyword. For 'Amazon Best Sellers by Category', 'Google Trends by Category', 'Pinterest Trending by Category', 'Top Websites', 'Substack by Category', and 'TikTok Trending Hashtags by Category', category selects the board. Default sort is current rank. Use sort='rank_change' for climbers vs a prior snapshot (window 1d, 3d, 7d, 14d, or 30d). If the requested board is not in the database yet (for example a country that is not collected on the schedule), the board is fetched live. App Store Top Free, App Store Top Paid, and Google Play are live store boards, not keyword lookups. App history is available via get_growth or get_time_series with source App Downloads or App Rankings and an Android bundle ID. Live boards are only available here, not via get_time_series. Costs 1 request per data type (source or board) in the call; boards cost 1 request per 10 rows. Only data types that answer are charged; the answer says requests_charged. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Pass this whenever type is 'Amazon Best Sellers by Category', 'Google Trends by Category', 'Pinterest Trending by Category', 'Top Websites', 'Substack by Category', or 'TikTok Trending Hashtags by Ca… |
| country | string | – | Optional ISO 3166-1 alpha-2 code (US, GB, JP). Aliases like 'USA' or 'United States' resolve to US. Omit for the default US board. Only for Google Trends, Google Trends by Category, Pinterest Trendin… |
| limit | integer | – | Rows per board. Default 100 = 10 requests per board (1 request per 10 rows); lower it to spend less, e.g. 10 = 1 request. Min 1, max 200. |
| offset | integer | – | Rows to skip for pagination. Default 0. |
| sort | string | – | How to rank the board. 'rank' (default): current leaders. 'rank_change': biggest climbers vs a prior snapshot. Mover rows include rank, keyword, prev_rank, and rank_change. |
| type | string | yes | One live feed, several comma-separated (one board each, each billed per 10 rows), or 'all' (27 boards). Valid: 'Amazon Best Sellers Top Rated', 'Amazon Best Sellers by Category', 'App Store Top Free'… |
| window | string | – | Lookback used only when sort is 'rank_change'. One of '1d', '3d', '7d', '14d', '30d'. Default '30d'. Short windows only work on daily feeds; weekly and monthly feeds return a note pointing to a longe… |
No output schema declared.
No examples provided.
trends___get_usage ~50
Shows your plan, requests used this month, requests left, and when it resets. Free: does not use a request. Call it when the user asks about their limit or after a limit error.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Amazon Trends API MCP server?
Amazon Trends API is a hosted endpoint at https://amazon.api.trendsapi.ai/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 · amazon.api.trendsapi.ai
claude mcp add --transport http ai-trendsapi-amazon 'https://amazon.api.trendsapi.ai/mcp'
What is the Amazon Trends API MCP server?
Amazon Trends API is an MCP server listed in the public MCP registry as ai.trendsapi/amazon. Amazon product search volume and best-seller trends. Free key at trendsapi.ai. This page covers its hosted endpoint (https://amazon.api.trendsapi.ai/mcp).
Is the Amazon Trends API MCP server safe to use?
Amazon Trends API scores 69 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 Amazon Trends API MCP server expose?
Amazon Trends API exposes 6 tools: trends___get_context, trends___get_growth, trends___get_reviews, trends___get_time_series, trends___get_top_trends, trends___get_usage. Their descriptions and schemas cost roughly 3,086 tokens of context every time the server is loaded.
Does the Amazon Trends API MCP server require authentication?
No. We connected to Amazon Trends API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Amazon Trends API MCP server still maintained?
Amazon Trends API 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 Amazon Trends API MCP server?
VerifyMCP ran 12 checks on Amazon Trends API, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Amazon Trends API: Authorization. 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.