Amazon Trends API is an MCP server with 3 tools an agent can call, among them trends___get_growth, trends___get_time_series, trends___get_top_trends. It answers at https://amazon.api.trendsapi.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Amazon product search volume and best-seller trends. Free key at trendsapi.ai
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
trends___get_growth | 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. Prefer this over get_time_series for Inputs: source, keyword, percent_growth |
trends___get_time_series | Full historical series for one keyword and one source (0-100 values, plus volume when available). Use for charting or custom math. Not for live 'what's trending now' boards (use get_top_trends). For most growth questions, use get_growth. If Inputs: source, keyword |
trends___get_top_trends | Live top-trending board for exactly one feed type. No keyword. For 'Amazon Best Sellers by Category', 'Google Trends by Category', 'Top Websites', 'Substack by Category', and 'TikTok Trending Hashtags by Category', always pass category. Def Inputs: country, offset, limit, sort, window, type |
Every block below points at https://amazon.api.trendsapi.ai/mcp. Pick your client and copy.
claude mcp add --transport http amazon-trends-api https://amazon.api.trendsapi.ai/mcp
{
"mcpServers": {
"amazon-trends-api": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://amazon.api.trendsapi.ai/mcp"]
}
}
}{
"mcpServers": {
"amazon-trends-api": {
"url": "https://amazon.api.trendsapi.ai/mcp"
}
}
}{
"servers": {
"amazon-trends-api": {
"type": "http",
"url": "https://amazon.api.trendsapi.ai/mcp"
}
}
}{
"context_servers": {
"amazon-trends-api": {
"url": "https://amazon.api.trendsapi.ai/mcp"
}
}
}{
"mcpServers": {
"amazon-trends-api": {
"serverUrl": "https://amazon.api.trendsapi.ai/mcp"
}
}
}{
"mcpServers": {
"amazon-trends-api": {
"url": "https://amazon.api.trendsapi.ai/mcp"
}
}
}name: Amazon Trends API
version: 0.0.1
schema: v1
mcpServers:
- name: Amazon Trends API
type: streamable-http
url: https://amazon.api.trendsapi.ai/mcp{
"mcpServers": {
"amazon-trends-api": {
"httpUrl": "https://amazon.api.trendsapi.ai/mcp"
}
}
}{
"mcpServers": {
"amazon-trends-api": {
"type": "http",
"url": "https://amazon.api.trendsapi.ai/mcp"
}
}
}{
"mcpServers": {
"amazon-trends-api": {
"url": "https://amazon.api.trendsapi.ai/mcp"
}
}
}goose://extension?url=https%3A%2F%2Famazon.api.trendsapi.ai%2Fmcp&type=streamable_http&id=amazon-trends-api&name=Amazon%20Trends%20API
It answered our last check on 17 October 2026 in 400 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by trendsapi.ai and served from amazon.api.trendsapi.ai, the vendor's own domain: https://amazon.api.trendsapi.ai/mcp.
3, as returned by the server's own tools/list on 8 September 2026: trends___get_growth, trends___get_time_series, trends___get_top_trends.
It answered our last check on 17 October 2026 in 400 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://amazon.api.trendsapi.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ai.trendsapi. Endpoint host: amazon.api.trendsapi.ai. ARD identifier: urn:air:ai.trendsapi:mcp:amazon.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.