Appdex

com.app-dexPublished by app-dex.comv1.1.1Updated Oct 24, 2026

iOS App Store revenue & download estimates with confidence labels

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

Appdex gives an assistant iOS App Store revenue and download estimates with confidence labels, via a local npm MCP server.

What you can do
Appdex is a local MCP server that surfaces iOS App Store revenue and download estimates, each carrying a confidence label so the assistant can convey how reliable a figure is. The manifest does not list individual tools, so the exact query surface is not documented here. It runs as a local process over stdio and talks to the Appdex API.
When to use it
Useful when you want an assistant to look up or compare estimated App Store revenue and download figures for iOS apps, for example during market or competitor research. Less relevant if you need data outside the iOS App Store or need guaranteed, high-volume access.
Requirements
Runs locally as an npm package (appdex-mcp) over stdio, so Node.js is required. An Appdex API key is supplied through the APPDEX_API_KEY environment variable; without it you get 2 requests per day, and a free-tier key gives 5 requests per day. APPDEX_API_URL optionally overrides the API base URL and defaults to the Appdex site. Network access to the Appdex API is needed.
Before you install
The server requires the APPDEX_API_KEY secret, which is sent to the Appdex API; treat it as a credential and keep it out of shared configuration. Queries and any app identifiers you look up are sent to a third-party service, and usage is rate-limited by tier. Estimates are labeled with confidence levels, so they should not be treated as exact financial figures.

Installation

In SourceWeft

  1. Open Appdex in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

15% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.