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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

20 minutes ago