Skip to content
Trends API logo

Trends API MCP server

Which servers in the official MCP registry are Trends API's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to Trends API

Whose server it is
  • Registry nameai.trendsapi/amazonverified in the MCP registry

The registry name sits under trendsapi.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13
  • Stateanswerschecked 2026-10-13
  • Tools4
  • Server calls itselftrendsmcp
  • Server version1.0.0
  • Protocol version2025-03-26

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 256 ms.

Tools it offers4 tools · read 2026-10-13
  • 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. Designed for growth questions; for…

  • trends___get_time_series

    Full historical series for one keyword and one source (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…

  • trends___get_top_posts

    Live top posts for one hashtag on one social source. Fetched live on every call; nothing is stored. For when the user already has a hashtag and wants the posts winning on it. get_top_trends ranks the hashtags themselves. Returns a…

  • 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', category selects the…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "amazon": {
      "type": "http",
      "url": "https://amazon.api.trendsapi.ai/mcp"
    }
  }
}
Other servers listed as Trends API's
  • ai.trendsapi/app-storeanswers, 4 toolsverified in the MCP registry
  • ai.trendsapi/competitor-trackinganswers, 4 toolsverified in the MCP registry
  • ai.trendsapi/content-strategynot asked yetverified in the MCP registry
  • ai.trendsapi/cryptonot asked yetverified in the MCP registry
  • ai.trendsapi/ecommercenot asked yetverified in the MCP registry
  • ai.trendsapi/google-trendsnot asked yetverified in the MCP registry
  • ai.trendsapi/market-researchnot asked yetverified in the MCP registry
  • ai.trendsapi/news-sentimentnot asked yetverified in the MCP registry
  • ai.trendsapi/news-volumenot asked yetverified in the MCP registry
  • ai.trendsapi/npmnot asked yetverified in the MCP registry
  • ai.trendsapi/redditnot asked yetverified in the MCP registry
  • ai.trendsapi/seonot asked yetverified in the MCP registry
  • ai.trendsapi/social-medianot asked yetverified in the MCP registry
  • ai.trendsapi/spotifynot asked yetverified in the MCP registry
  • ai.trendsapi/steamnot asked yetverified in the MCP registry
  • ai.trendsapi/tiktoknot asked yetverified in the MCP registry
  • ai.trendsapi/trendsnot asked yetverified in the MCP registry
  • ai.trendsapi/wikipedianot asked yetverified in the MCP registry
  • ai.trendsapi/x-twitternot asked yetverified in the MCP registry
  • ai.trendsapi/youtubenot asked yetverified in the MCP registry

OpenAPI spec

1 paths, read 2026-10-13. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.