App Store Revenue & Download Estimator - MCP Server avatar

App Store Revenue & Download Estimator - MCP Server

Pricing

$5.00 / 1,000 mcp tool calls

Go to Apify Store
App Store Revenue & Download Estimator - MCP Server

App Store Revenue & Download Estimator - MCP Server

MCP server for app-store-revenue-estimator. AI-agent tools for App Store and Google Play download/revenue estimates, rank history, and publisher rollups. x402 (USDC on Base) and Skyfire agentic-payment ready. For app devs, UA teams, and app investors.

Pricing

$5.00 / 1,000 mcp tool calls

Rating

0.0

(0)

Developer

Seibs.co

Seibs.co

Maintained by Community

Actor stats

0

Bookmarked

0

Total users

0

Monthly active users

6 days ago

Last modified

Share

Model Context Protocol (MCP) server wrapper for app-store-revenue-estimator. Gives AI agents pay-per-call access to modeled download and revenue bands for iOS and Google Play apps - the Sensor-Tower-style numbers - with a stated confidence level and a plain-English methodology. No API token required when called over x402 / Skyfire.

What it is

A thin MCP server that exposes the estimation engine as four typed tools an AI agent can call. Each tool runs the upstream app-store-revenue-estimator actor and reshapes the result into small, deterministic JSON. The product is the estimate: download and revenue bands derived from public signals (chart rank, ratings velocity, Google Play install buckets, price, IAP presence), not raw store metadata. Built for market-research copilots, competitive-intel agents, and analyst dashboards.

Read this honestly: these are order-of-magnitude bands with a stated confidence, not measurements. They tighten when the upstream actor runs on a schedule and accumulates ratings-velocity history. This server is not affiliated with Apple, Google, or Sensor Tower.

Tools

ToolWhat it does
estimate_appModeled download + revenue band for one app (iOS id/URL or Play package/URL), with confidence, methodology, and caveats.
compare_appsEstimate 2-10 apps and rank them by download-band midpoint, with a leader/trailer comparison summary.
get_publisher_portfolioAll of a publisher's apps with per-app estimates plus one combined portfolio band (downloads, revenue, confidence, top app, category mix).
get_top_chart_estimatesTop N apps of a country's chart (top-free or top-paid) with an estimate attached to each, ranked by chart position. Apple feeds only; top_n cap 50.

Run modes

  • list_tools - emit the tool catalog (free, no charge) including the agentic-payment descriptor.
  • call_tool - invoke one tool. Requires tool + args.
  • batch - invoke up to 10 {tool, args} calls in one run.
{
"mode": "call_tool",
"tool": "estimate_app",
"args": { "app": "com.spotify.music", "country": "us" }
}
{
"mode": "call_tool",
"tool": "compare_apps",
"args": { "apps": ["310633997", "com.spotify.music"], "country": "us" }
}

What you get

Every tool returns the same MCP envelope: ok, count, items, summary, error. The items carry the upstream estimate_enrichment records with the bands preserved verbatim:

  • downloads_band - { low, mid, high, period } where period is daily, monthly, or lifetime.
  • revenue_band_usd - estimated GROSS revenue in USD (before the 15-30% store cut and refunds).
  • confidence - low / medium / high. High means two or more independent signals agree within 3x.
  • methodology - one human sentence naming which public signals drove the estimate.
  • caveats - the assumptions behind the number, surfaced so an agent can reason about them.

Honesty notes (read before you trust a number)

  • Estimates are order-of-magnitude bands with stated confidence, not the publisher's actual figures.
  • Revenue is gross. Multiply by roughly 0.7-0.85 for net after the store cut and refunds.
  • Estimates tighten when the upstream runs on a schedule (estimate_monitor mode) and builds a ratings-velocity time series; a one-shot call has no history and leans on coarser signals.
  • Google Play has no public top-charts feed, so get_top_chart_estimates is Apple-only. Play package estimates use the public install bucket and are best-effort.
  • Not affiliated with Apple, Google, or Sensor Tower. This tool models public signals; it does not access any private store analytics.

Agentic payments (x402 + Skyfire)

This server is x402 (USDC on Base) and Skyfire ready. When the operator enables Apify MCP monetization, an AI agent can pay per tool call with no pre-provisioned API token. The list_tools response includes a payments descriptor advertising the accepted rails and per-call price. Operators enable rails via environment variables:

EnvPurpose
X402_ENABLED1 to advertise x402 acceptance
X402_PAY_TO_ADDRESSreceiving wallet (USDC on Base)
X402_PRICE_USDper-call price advertised (default 0.005)
SKYFIRE_ENABLED1 to advertise Skyfire acceptance
SKYFIRE_SELLER_IDSkyfire seller identity

Calls through Apify always bill via standard PPE (mcp_tool_call $0.005 + upstream pass-through); x402/Skyfire are the token-less rails layered on top for direct agents.

Pricing

Flat $0.005 per MCP tool call, plus the upstream app-store-revenue-estimator PPE pass-through (app_record $0.010, estimate_enrichment $0.020, publisher_rollup $0.030) billed to the same run. list_tools is free. A run that returns nothing costs nothing.

Responsible use / data scope

The upstream actor reads only logged-out, public data: Apple's official free iTunes lookup/search endpoints and marketing RSS top-charts feeds, and the public Google Play app-detail page. No accounts, no cookies, no paywall bypass. You are responsible for lawful use of the outputs and for treating the bands as estimates. See the upstream actor's README for the full data-scope note.

  • app-store-revenue-estimator - the non-MCP actor with full input controls, publisher rollups, top-charts, and estimate_monitor (the scheduled mode that sharpens estimates over time).
  • reddit-topic-watcher - track where an app or competitor is being discussed.

Found this useful?

Leave a quick review: https://apify.com/seibs.co/mcp-app-store-revenue-estimator#reviews