com.webatola/app-store-trends

Settings → Connectors → Add custom connector, then paste:
https://webatola--app-store-trends-mcp-server.apify.actor/mcp

The entry also requires the header Authorization.

{
  "mcpServers": {
    "app-store-trends": {
      "url": "https://webatola--app-store-trends-mcp-server.apify.actor/mcp",
      "headers": {
        "Authorization": "<Authorization>"
      }
    }
  }
}

{
  "servers": {
    "app-store-trends": {
      "type": "http",
      "url": "https://webatola--app-store-trends-mcp-server.apify.actor/mcp",
      "headers": {
        "Authorization": "${input:authorization}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "authorization",
      "description": "Authorization",
      "password": true
    }
  ]
}

claude mcp add --transport http app-store-trends https://webatola--app-store-trends-mcp-server.apify.actor/mcp --header "Authorization: <Authorization>"

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://webatola--app-store-trends-mcp-server.apify.actor/mcp --transport http

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

• com.browser-use/browser-usecompare with this one
• io.github.D4Vinci/ScraplingScrapling MCP Servercompare with this one
• io.github.upstash/context7Context7compare with this one
• io.github.bytedance/mcp-server-browsercompare with this one
• io.github.bytedance/mcp-server-searchcompare with this one
• io.github.feder-cr/aihawkAIHawkcompare with this one

Active servers whose topic is also “search-and-web-data”, most GitHub stars first. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Needs the operator's credential

The server requires sign-in. We never use a credential its operator did not give us, so most checks could not run. No security score is given; a check we did not run is never counted as passed.

Why not security-tested: The server required a sign-in before it would list anything, and we never use a credential its operator did not give us. Its operator can test it with their own credential, on their own machine, with our self-test command (/docs/selftest). — the server's own choice

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 1 of the 18 checks that apply to it was exercised. We do not publish security-check outcomes for named servers.

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

The steps in order, as the test record holds them.

1. 0 msStarted a session with the server's remote endpoint
2. The server asked for sign-in before listing anything.
3. 3,574 msFinished: 1 check exercised.

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.