App Store & Google Trends

com.webatolaPublished by webatola.comv0.1.0Updated Oct 26, 2026

App Store top charts, keyword search and rank, app details, and Google Trends trending searches.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Remote Apify-hosted MCP server that gives an assistant App Store top charts, keyword search and rank, app details, and Google Trends trending searches.

What you can do
  • Look up App Store top charts and app details
  • Search App Store keywords and check keyword rank
  • Retrieve Google Trends trending searches
When to use it
Useful when you want an assistant to research app market positioning, compare chart placement, check keyword rankings, or pull current trending search topics without building your own scrapers.
Requirements
A remote streamable HTTP endpoint at the provider's Apify actor URL. An Apify account and API token are required, sent as a bearer token in the Authorization header. Calls are billed to that Apify account.
Before you install
The Authorization header carries your Apify API token, a secret that grants access to your account. Usage is billed to your Apify account, so repeated calls cost money. Queries are sent to a third-party Apify-hosted service.

Installation

In SourceWeft

  1. Open App Store & Google Trends 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/com.webatola%2Fapp-store-trends/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": {
    "app-store-google-trends": {
      "type": "http",
      "url": "https://webatola--app-store-trends-mcp-server.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

1
  1. v0.1.0LatestOct 21, 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.