Trends MCP

Created By
trendsmcp2 months ago
Real-time trend data from Google Trends (Search, Images, News, Shopping), YouTube, TikTok, Reddit, Amazon, Wikipedia, X (Twitter), LinkedIn, Spotify, GitHub, Steam, npm, App Store, news sentiment and web traffic via one MCP connection. Free API key, no credit card required.
Overview

Give your AI live trend data from 20+ sources via one MCP connection.

Data sources

  • Google Trends (Search, Images, News, Shopping)
  • YouTube: video search volume trends
  • TikTok: hashtag and viral trend data
  • Reddit: community discussion volume
  • Amazon: product search demand
  • Wikipedia: page view trends
  • X (Twitter): real-time social signals
  • LinkedIn: professional topic trends
  • Spotify: music and podcast trends
  • GitHub: trending repositories
  • Steam: concurrent player data
  • npm: package download trends
  • App Store / Google Play: app download and ranking trends
  • News sentiment: positive/negative volume analysis
  • Web traffic: site visit trends

Tools

ToolWhat it does
get_trendsTime-series for any keyword on any source
get_growthGrowth % over 1M, 3M, 1Y periods
get_top_trendsWhat is trending right now
get_ranked_trendsTop trends ranked by volume

Free to start

100 requests/day free. No credit card. Get your key at trendsmcp.ai.

Works with

Claude, Cursor, VS Code, GitHub Copilot, Windsurf, ChatGPT, Cline, Raycast, and any MCP-compatible AI.

Server Config

{
  "mcpServers": {
    "trends-mcp": {
      "url": "https://api.trendsmcp.ai/mcp",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
trendsmcp
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

10 hours ago