Command Palette

Search for a command to run...

UnylyUnyly
Весь каталог

AppScope Server

БесплатноНе проверен

Self-hosted MCP server for app market intelligence, enabling tools to query app download/revenue estimates, ad intensity proxies, creator mentions, and rank his

GitHubEmbed

Описание

Self-hosted MCP server for app market intelligence, enabling tools to query app download/revenue estimates, ad intensity proxies, creator mentions, and rank history from local collected data.

README

The AppScope periscope, scanning a wall of app icons

AppScope

vendors sell app "installs" from a black box. this shows the facts, bands the guesses. 🔭

AppScope — self-hosted app market intelligence, estimates capped at MEDIUM

411 apps · 597 ranks · 7,203 reviews — all observed · estimates ≤ MEDIUM · $0 ad-spend invented


observed estimate ad_spend


A rendered app-intel-report.html — observed rank and install bucket at HIGH confidence, download estimate as a band at MEDIUM, revenue honestly not modeled

The deliverable: observed facts are HIGH, estimates are bands, missing data says so.


A self-hosted, federated open-source app market-intelligence tool + MCP server. An honest OSS take on the reproducible ~60% of tools like AppKittie / Sensor Tower / AppTweak.

Every number is produced by a documented model on real, locally-captured data, always with a confidence label, a method tag, and the data behind it. The system refuses to fabricate the two figures vendors model from private panels (dollar ad spend, panel-grade installs).


There is no central server

Each user self-hosts. You clone the repo, supply your own keys, and run the collectors, estimator, REST API and MCP server on your own machine (or your own cheap VPS). Your captured data lives in a local SQLite database. Your own Claude/Cursor connects to your own local MCP server.

There is no shared API endpoint, no central bill, no shared uptime obligation, no central scraping-ToS exposure. If your machine is down, only your instance is affected.

The only shared component is an opt-in Hugging Face dataset of public app-store calibration anchors that everyone pulls back to sharpen their estimates (see Federation).

📖 For a full how-it-works walkthrough (the estimator math, the data model, and the CI auto-merge setup), read USER_MANUAL.md.


What it does

Capability How Honesty
Rankings + metadata Apple RSS top charts, iTunes lookup, Google Play Fully reproducible (HIGH = observed fact)
Install buckets (Android) google-play-scraper minInstalls/realInstalls Observed fact; the anchor source
Download/revenue estimates Garg–Telang rank→download power law, scale calibrated from pooled anchors Ranges, capped at MEDIUM, with method + provenance
Ad creative & cadence Meta Ad Library (official API), Google Ads Transparency, optional TikTok Spend-intensity proxies, never dollars. Local only
Creator attribution YouTube Data API + rule-based mention classifier Partial recall, precision-gated. Local only
Reviews Apple RSS + Play Observed counts
REST API + MCP FastAPI + FastMCP Local
Federation contribute.py / refresh_dataset.py → HF dataset Public anchors only

The honesty rules (enforced)

  • P1 — Every number carries confidence + method + provenance. Envelope: {value, low, high, confidence, method, sources, flags}.
  • P2 — Estimates are ranges, capped at MEDIUM. HIGH is reserved for directly observed facts (a captured rank, a real install bucket, a real review count). A modeled estimate is never HIGH.
  • P3 — Proxies, not dollars, for ads. The ad module emits intensity proxies and a mandatory disclaimer; it never outputs USD spend.
  • P4 — Sanity bounds. A cumulative download estimate must respect the Google install bucket; violations are flagged and downgraded, never silently emitted.
  • N4 — Free-app revenue is never invented. Returns not estimable unless you supply an ARPU.
  • P8 — Local-first; federate only public anchors. Ads and creator data never leave your machine. A guard (assert_public_only) aborts any contribution carrying ad/creator/identity fields.

The three known gaps (stated plainly)

The AppScope periscope drooping in an apologetic shrug beside an empty radar ring — when a segment is uncalibrated, it says so
  1. Downloads / revenue — partially solvable, and improves with the shared dataset. Calibrating absolute scale is the hard part; federation pools install-bucket-derived anchors so segments reach ≥5 anchors and graduate LOW → MEDIUM. Never panel-grade.
  2. Ad spend — a hard gap; proxies only. Spend = impressions × CPM ÷ 1000, and impressions live only in opt-in panels. Public ad libraries expose creatives + run dates (banded spend only for EU/political ads). So we emit intensity proxies, never dollars — and ads never federate.
  3. Creator attribution — the hardest; partial recall, local-first. YouTube Data API is the one fully-compliant organic-discovery route; the rule-based mention classifier is the missing middle layer. Creator data stays local.

Use as a Claude Code skill (the easy way)

/plugin marketplace add Ahad690/open-app-intel
/plugin install appscope@appscope-marketplace

Then just ask — "how many downloads does com.spotify.music get?" — or run /appscope. Claude collects the app into your local DB, answers with the estimator's confidence-banded envelopes verbatim (never a fabricated number), and renders app-intel-report.html with provenance on every row. Under the hood it drives the same JSON CLI you can use yourself:

python -m appscope.cli collect  --app <id> [--charts]
python -m appscope.cli summary  --app <id>            # observed facts (HIGH)
python -m appscope.cli estimate --app <id>            # banded estimate (≤ MEDIUM)
python -m appscope.cli report   --app <id>            # the HTML deliverable
python -m appscope.cli backup                         # timestamped DB snapshot

No data is ever destroyed: captured observations (ranks, install buckets, reviews) are append-only — a re-collect can never overwrite history; derived estimates are recomputable; backup snapshots are never pruned. Your data accumulates locally until you opt in to contribute anchors (see Federation).

Install (manual)

git clone <your-fork> open-app-intel && cd open-app-intel
python -m venv .venv && . .venv/bin/activate     # Windows: .venv\Scripts\activate
pip install -r requirements.txt
cp config.sample.json config.json                # then edit tracking.apps etc.

Keys are read from environment variables named in config.json (never stored):

export META_AD_TOKEN=...      # Meta Ad Library (ads, optional)
export YOUTUBE_API_KEY=...    # YouTube Data API (creators, optional)
export HF_TOKEN=...           # Hugging Face (contributors only)

Run

# 1. Collect (one pass now, or run as a daily scheduler)
python -m appscope.scheduler --once
python -m appscope.scheduler            # daily at config.schedule.daily_hour_utc (UTC)

# 2. Seed + calibrate from the community anchors
python -m appscope.federation.refresh_dataset

# 3a. Local REST API
uvicorn appscope.api:app --host 127.0.0.1 --port 8000
#   GET /apps/{app_id}/estimate?country=us   -> P1 envelope
#   GET /apps/{app_id}/ads                    -> intensity proxies (no USD)
#   GET /apps/{app_id}/creators?min_confidence=0.6
#   GET /apps/{app_id}/ranks?days=30
#   GET /apps/{app_id}/reviews?days=30

# 3b. Local MCP server (point your Claude/Cursor at this)
python -m appscope.mcp_server

Connecting your local Claude to your local MCP server

Add to your Claude/Cursor MCP config (each user, locally):

{
  "mcpServers": {
    "appscope": {
      "command": "python",
      "args": ["-m", "appscope.mcp_server"],
      "cwd": "/path/to/open-app-intel"
    }
  }
}

Tools exposed: app_estimate, ad_intensity, creator_mentions, rank_history.


Federation

The AppScope periscope hugging a pull-request icon — contributions grow everyone's calibration

The estimator's weak link is calibrating absolute scale (scale_b), which needs anchor points that are scarce solo. Federating Android install-bucket deltas as observed download-flow anchors pools enough data to calibrate per segment.

# Pull everyone's public anchors, validate, merge, and refit calibration
python -m appscope.federation.refresh_dataset            # --dry-run to preview

# Share YOUR public anchors (opt-in; needs --contributor AND HF_TOKEN)
python -m appscope.federation.contribute --dry-run        # prints what would be shared
python -m appscope.federation.contribute --contributor you

Shared dataset: https://huggingface.co/datasets/Ahad690/app-rank-anchors (CC-BY-4.0). A contribution row is only: platform, category, country, list_type, rank, observed_downloads, window_days, min_installs, real_installs, price_usd, is_free, rating_count, captured_on. app_id is intentionally omitted. No ads, no creators, no identity — enforced by assert_public_only and proven by tests/test_anchor_guard.py. See DATA_POLICY.md.

Contribution PRs are auto-merged daily by a GitHub Action (.github/workflows/automerge-dataset-prs.yml) that re-validates every anchor row on the receiving side before merging — see USER_MANUAL.md §7 for the one-time HF_TOKEN secret setup.


Tests

pip install pytest
pytest -q

Covers anchor derivation, calibration, the never-HIGH cap, free-app revenue, the no-USD ad gate (K2), the mention-precision gate (K5), and the federation guard (K-P8).


Legal / compliance

Self-host, compliant by default: Apple RSS, iTunes lookup, official Meta Ad Library API, Google Ads Transparency, YouTube Data API, used within terms. Opt-in scrapers (Play HTML, TikTok, Instagram) are operator responsibility under each platform's ToS; the legal landscape is unsettled. Estimates are modeled, not measured — labeled as such; the project warrants nothing about accuracy.

Code: MIT (LICENSE). Data + docs: CC-BY-4.0 (LICENSE-DATA).

Related projects (same honesty architecture)

AppScope is part of a family of local-first, no-fabricated-numbers Claude Code skills — deterministic scripts, provenance envelopes, an HTML deliverable, append-only local data, opt-in federation:

The AppScope periscope powered down for the night in a tiny nightcap, zzz
~ end of file · estimates stayed ≤ MEDIUM the whole way ~

from github.com/Ahad690/open-app-intel

Установка AppScope Server

У этого сервера нет опубликованного пакета — он собирается из исходников. Открой репозиторий и следуй инструкции в README.

▸ github.com/Ahad690/open-app-intel

FAQ

AppScope Server MCP бесплатный?

Да, AppScope Server MCP бесплатный — установка в пару кликов через Unyly без оплаты.

Нужен ли API-ключ для AppScope Server?

Нет, AppScope Server работает без API-ключей и переменных окружения.

AppScope Server — hosted или self-hosted?

Self-hosted: сервер запускается локально на твоей машине командой из раздела установки.

Как установить AppScope Server в Claude Desktop, Claude Code или Cursor?

Открой AppScope Server на unyly.org, выбери вкладку своего клиента (Claude Desktop, Claude Code, Cursor) и нажми Install — конфиг сгенерируется автоматически, без правки JSON.

Похожие MCP

Compare AppScope Server with

Не уверен что выбрать?

Найди свой стек за 60 секунд

Автор?

Embed-бейдж для README

Похожее

Все в категории development