AppHitlist

com.apphitlistPublished by apphitlist.comOfficial publisherv1.1.0Updated Nov 4, 2026

App Store research: new winning apps, chart risers, revenue figures, complaints and Meta ads.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for App Store research: surfaces new winning apps, chart risers, revenue figures, user complaints and Meta ads.

What you can do
  • Research App Store market data: find new winning apps and chart risers.
  • Look up revenue figures for apps.
  • Review user complaints and Meta ads tied to apps.
  • No individual tools are documented, so the exact queries and output formats are not described.
When to use it
Useful when you want an assistant to help with mobile app market research — spotting rising or newly successful apps, checking revenue signals, or scanning complaints and Meta ad activity before deciding what to build or promote.
Requirements
A remote MCP endpoint at apphitlist.com over streamable HTTP. Authentication is required via OAuth, with an Authorization header carrying a bearer API key obtained from the provider's account page.
Before you install
The server requires an API key sent in the Authorization header; keep it private and scope it as narrowly as the provider allows. Research data and any queries you send go to a third-party service. No tool list is published, so review what the server can access after connecting.

Installation

In SourceWeft

  1. Open AppHitlist in the dashboard and add it to a workspace.
  2. Connect the required 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.apphitlist%2Fmcp/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "apphitlist": {
      "type": "http",
      "url": "https://apphitlist.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.1.0LatestNov 4, 2026
  2. v1.0.0Oct 11, 2026

Score

83% 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
  • 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.