Name: App Store + Google Play Data
Author: TheValkDokk

App Store + Google Play Data MCP

Live App Store and Google Play data: app details, reviews, search, top charts for 175+ storefronts.

Grade A Remote or local · Streamable HTTP · stdio API key 5 tools v0.2.0 MIT

No reviews yet by TheValkDokknpm 942 Runs on your machine or at its publisher’s address — not through us

99/100

trust score

downloads a day

local

or remote

942

downloads in 30d

What it does

Live App Store and Google Play data: app details, reviews, search, top charts for 175+ storefronts.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --env 'RAPIDAPI_KEY=${RAPIDAPI_KEY}' --transport stdio app-store-google-play-data-mcp '--' npx -y appstore-data-mcp

# 2 — ask your agent for something these tools do
#   search_apps, get_app, get_app_reviews and 2 more

It needs RAPIDAPI_KEY: this reads it from your environment, so export it first.

App Store + Google Play Data costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

TheValkDokk1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads RAPIDAPI_KEY (RapidAPI key from https://rapidapi.com/TheValkDokk/api/app-store-google-play-data-api) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx RAPIDAPI_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user --env 'RAPIDAPI_KEY=${RAPIDAPI_KEY}' --transport stdio app-store-google-play-data-mcp '--' npx -y appstore-data-mcp

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Or connect to its publisher’s address

Its publisher also runs it at https://appstore-mcp-623314400722.us-central1.run.app/mcp: nothing to start on your machine, and this marketplace is not in the path.

claude mcp add --scope user --transport http app-store-google-play-data-mcp https://appstore-mcp-623314400722.us-central1.run.app/mcp

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

It reaches a system of yours, so it needs your own credential rather than the publisher’s: RAPIDAPI_KEY — RapidAPI key from https://rapidapi.com/TheValkDokk/api/app-store-google-play-data-api. You set it in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

Search a store by keyword, using the store's own relevance ranking. Returns compact rows with the id you need for get_app.

Parameter	Type	Required	Notes
query	string	yes	Keyword(s) to search for, e.g. 'meditation', 'photo editor'.
store	string	no	Store to query: "ios" (Apple App Store) or "android" (Google Play).
country	string	no	ISO-2 storefront code, e.g. us, gb, de, jp. Defaults to us.
lang	string	no	Language code, e.g. en, es, fr, ja. Defaults to en.
limit	integer	no	Number of results, 1-50. Defaults to 10.

Full metadata for one app: name, developer, ratings, price, version, size, screenshots, store URL. Use the numeric app id (iOS) or package name (Android).

Parameter	Type	Required	Notes
app_id	string	yes	iOS: numeric Apple id (e.g. '389801252' for Instagram). Android: package name (e.g. 'com.instagram.android').
store	string	no	Store to query: "ios" (Apple App Store) or "android" (Google Play).
country	string	no	ISO-2 storefront code, e.g. us, gb, de, jp. Defaults to us.
lang	string	no	Language code, e.g. en, es, fr, ja. Defaults to en.

Paginated user reviews. sort=recent is best for monitoring new feedback; sort=helpful surfaces the loudest complaints. Page with offset and stop when has_more is false.

Parameter	Type	Required	Notes
app_id	string	yes	iOS numeric id or Android package name.
store	string	no	Store to query: "ios" (Apple App Store) or "android" (Google Play).
country	string	no	ISO-2 storefront code, e.g. us, gb, de, jp. Defaults to us.
sort	string	no	recent \| helpful \| rating (rating is Android-only).
limit	integer	no	Reviews per page, 1-50. Defaults to 20.
offset	integer	no	How many reviews to skip, for pagination.

Ranked top-chart lists per storefront. iOS collections: topfreeapplications, toppaidapplications, topgrossingapplications, newapplications (+ ipad variants). Android: topselling_free, topselling_paid, topgrossing, new_free, new_paid.

Parameter	Type	Required	Notes
store	string	no	Store to query: "ios" (Apple App Store) or "android" (Google Play).
collection	string	no	Chart name. Defaults to topfreeapplications (iOS) / topselling_free (Android).
category	string	no	Optional category id, e.g. '6018' (iOS Books) or 'GAME' (Android).
country	string	no	ISO-2 storefront code, e.g. us, gb, de, jp. Defaults to us.
limit	integer	no	Rows to return, 1-50. Defaults to 25.

The store's category taxonomy — id and name — for building filters or resolving a category id used by top_charts.

Parameter	Type	Required	Notes
store	string	no	Store to query: "ios" (Apple App Store) or "android" (Google Play).
country	string	no	ISO-2 storefront code, e.g. us, gb, de, jp. Defaults to us.

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install App Store + Google Play Data or to call it, at any volume.

ATrust score 99 / 100

Release 0.2.0 · scanned 28 Oct 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score99

Findings0 threat · 0 capability

Capabilityminimal

Coveragesource

Verificationrepo

Surface digest135b412835d5bb56c7846a5c94f5f6a0cb1f3d4104a212b56f769b15864f631c

Score vectorthreat 100 → client 99

Term	Level	What it prices	Points
capability-exposure	minimal	capability blast radius (minimal) — client exposure if the model is manipulated	−0
verification-discount	repo	publisher verification (public source) — no provenance, but the source is public and inspectable	−1
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (5 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.

Tool	Capability tags	Why the tag was assigned
search_apps	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
get_app	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
get_app_reviews	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
top_charts	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
list_categories	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest135b412835d5bb56

Scanned2026-10-28

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.