mcpbeat Sign in

Trends MCP Server

answering

Trends MCP is answering right now. Last checked 12 min ago. It exposes 4 tools.

Trend data from Google Trends, YouTube, TikTok, Reddit, Amazon, Wikipedia, npm, Steam and more

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 47 days of history · worst day 99%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
492 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 29 August 2026. No other catalogue keeps this.

16 Sep a tool appeared trends___get_top_posts
5 Sep a tool description was rewritten trends___get_top_trends
5 Sep a tool changed the parameters it asks for trends___get_top_trends
29 Aug a tool description was rewritten trends___get_top_trends
29 Aug a tool changed the parameters it asks for trends___get_top_trends

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add trends --transport http https://api.trendsmcp.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "trends": {
      "url": "https://api.trendsmcp.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.trends]
url = "https://api.trendsmcp.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "trends": {
      "url": "https://api.trendsmcp.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "trends": {
      "url": "https://api.trendsmcp.ai/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

trends
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 growth questions. 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. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.
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 the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.
trends___get_top_posts
Live top posts for one hashtag on one social source. Fetched live on every call; nothing is stored. Use when the user already has a hashtag and wants the posts winning on it. For ranking hashtags themselves, use get_top_trends. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.
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. 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 handler fetches that one board live. App Store Top Free, App Store Top Paid, and Google Play are live store boards, not keyword lookups. For an app's history use get_growth or get_time_series with source app downloads or app rankings and an Android bundle ID. Do not use get_time_series for live boards. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

Endpoints

URLTransportStateLatencyChecked
https://api.trendsmcp.ai/mcp streamable-http answering 519 ms 12 min ago

Alternatives to Trends MCP

same job, measured the same way
Trends API
by trendsapi

Trend data from Google, TikTok, Amazon, Reddit, YouTube, Steam, npm and more as JSON

4 tools answering
Scavio
by scavio-ai

Structured web data from 31 platforms: Google, YouTube, Amazon, Walmart, Reddit, TikTok, LinkedIn

322 installs/wk answering
Multi Scraper MCP
by perufitlife

14 web scrapers as MCP tools: Reddit, Amazon, Google Maps, Yelp, YouTube, Indeed & more.

21 installs/wk local only
API Direct
by apidirect

Search social media, news, forums and Google Maps: LinkedIn, X, Reddit, TikTok, YouTube.

102 tools answering
Scrapingdog
by darshan972

Scrapingdog web-scraping & SERP APIs: web scrape, Google, Amazon, LinkedIn, YouTube, and more.

40 installs/wk local only
Scrapio MCP
by xsronhou

Fetch, crawl, and search the web: Google, Amazon, Walmart, Booking.com, Agoda, and YouTube data.

87 installs/wk local only
Social Research MCP
by themineworks

8 social listening tools over one MCP endpoint: Reddit, X, Threads, YouTube, Google Trends, news.

answering
Synter Ads
by jshorwitz

Manage ad campaigns across Google, Meta, LinkedIn, Reddit, TikTok, and more via AI.

73 installs/wk 209 tools answering

Trends MCP — questions

Answers built from our own checks of this server.

What can Trends MCP do?
It exposes 4 tools, read directly from the server on our last check. Among them: trends___get_growth, trends___get_time_series, trends___get_top_posts, trends___get_top_trends. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Trends MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 492 ms. The bar chart above shows every period we have measured.
Is Trends MCP still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Trends MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Trends MCP need an API key?
No. Trends MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Trends MCP?
It answers our handshake in 492 ms on average, which is faster than 29% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.