Google Trends Scraper & API

io.github.akhilrajesh213Published by GitHub account akhilrajesh213v0.1.11Updated Nov 7, 2026

Google Trends for AI agents, no key: Trending Now, interest over time, rising searches, Pinterest.

The publisher's own server: Scraper API

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Hosted Apify actor that gives an assistant Google Trends data: trending searches, interest over time, rising queries and Pinterest trends.

What you can do
  • Retrieve Google Trends data on demand: Trending Now lists, interest over time, rising searches and Pinterest trends.
  • Query trend signals for topics or keywords and use the returned rows in analysis or reporting.
  • No tool list is published, so exact operations are not documented beyond the description.
When to use it
Useful when you want an assistant to pull current search-trend signals for market research, content planning or keyword checks without building your own scraper.
Requirements
A remote streamable HTTP endpoint at an Apify actor URL. An Apify API token is required, sent as an Authorization bearer header. An Apify account with billing is needed because results are charged per row.
Before you install
The Authorization header carries your Apify API token, so keep it private. Usage is billed per row to your Apify account, so large runs cost money. Trend queries are sent to a third-party Apify actor.

Installation

In SourceWeft

  1. Open Google Trends Scraper & API in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.akhilrajesh213%2Fgoogle-trends-scraper/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "google-trends-scraper-api": {
      "type": "http",
      "url": "https://akhil-rajesh--google-trends-scraper.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

2
  1. v0.1.11LatestNov 7, 2026
  2. v0.1.9Nov 4, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Scraper-Api integrations