App Store + Google Play Data
NPM · APPSTORE-DATA-MCP · 2 COMPONENTS
Live App Store and Google Play data: app details, reviews, search, top charts for 175+ storefronts.
Available components
Last scanned (9 hours ago)
Scores higher than 32% of npm servers
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 846 tokens (~169/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +10
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/appstore-data-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_app App details ~161
Full metadata for one app: name, developer, ratings, price, version, size, screenshots, store URL. Use the numeric app id (iOS) or package name (Android).
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | iOS: numeric Apple id (e.g. '389801252' for Instagram). Android: package name (e.g. 'com.instagram.android'). |
| country | string | – | ISO-2 storefront code, e.g. us, gb, de, jp. Defaults to us. |
| lang | string | – | Language code, e.g. en, es, fr, ja. Defaults to en. |
| store | string | – | Store to query: "ios" (Apple App Store) or "android" (Google Play). |
No output schema declared.
No examples provided.
get_app_reviews App reviews ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | iOS numeric id or Android package name. |
| country | string | – | ISO-2 storefront code, e.g. us, gb, de, jp. Defaults to us. |
| limit | integer | – | Reviews per page, 1-50. Defaults to 20. |
| offset | integer | – | How many reviews to skip, for pagination. |
| sort | string | – | recent | helpful | rating (rating is Android-only). |
| store | string | – | Store to query: "ios" (Apple App Store) or "android" (Google Play). |
No output schema declared.
No examples provided.
list_categories Store categories ~85
The store's category taxonomy — id and name — for building filters or resolving a category id used by top_charts.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO-2 storefront code, e.g. us, gb, de, jp. Defaults to us. |
| store | string | – | Store to query: "ios" (Apple App Store) or "android" (Google Play). |
No output schema declared.
No examples provided.
search_apps Search apps ~155
Search a store by keyword, using the store's own relevance ranking. Returns compact rows with the id you need for get_app.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO-2 storefront code, e.g. us, gb, de, jp. Defaults to us. |
| lang | string | – | Language code, e.g. en, es, fr, ja. Defaults to en. |
| limit | integer | – | Number of results, 1-50. Defaults to 10. |
| query | string | yes | Keyword(s) to search for, e.g. 'meditation', 'photo editor'. |
| store | string | – | Store to query: "ios" (Apple App Store) or "android" (Google Play). |
No output schema declared.
No examples provided.
top_charts Top charts ~186
Ranked top-chart lists per storefront. iOS collections: topfreeapplications, toppaidapplications, topgrossingapplications, newapplications (+ ipad variants). Android: topselling_free, topselling_paid, topgrossing, new_free, new_paid.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category id, e.g. '6018' (iOS Books) or 'GAME' (Android). |
| collection | string | – | Chart name. Defaults to topfreeapplications (iOS) / topselling_free (Android). |
| country | string | – | ISO-2 storefront code, e.g. us, gb, de, jp. Defaults to us. |
| limit | integer | – | Rows to return, 1-50. Defaults to 25. |
| store | string | – | Store to query: "ios" (Apple App Store) or "android" (Google Play). |
No output schema declared.
No examples provided.
How do I install the App Store + Google Play Data MCP server?
App Store + Google Play Data runs locally as an npm package, launched with npx -y appstore-data-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · appstore-data-mcp
claude mcp add thevalkdokk-appstore-data -- npx -y appstore-data-mcp
What is the App Store + Google Play Data MCP server?
App Store + Google Play Data is an MCP server listed in the public MCP registry as io.github.TheValkDokk/appstore-data. Live App Store and Google Play data: app details, reviews, search, top charts for 175+ storefronts. This page covers its npm package (appstore-data-mcp).
Is the App Store + Google Play Data MCP server safe to use?
App Store + Google Play Data scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the App Store + Google Play Data MCP server expose?
App Store + Google Play Data exposes 5 tools: search_apps, get_app, get_app_reviews, top_charts, list_categories. Their descriptions and schemas cost roughly 753 tokens of context every time the server is loaded.
Is the App Store + Google Play Data MCP server still maintained?
App Store + Google Play Data is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the App Store + Google Play Data MCP server under?
App Store + Google Play Data declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the App Store + Google Play Data MCP server?
VerifyMCP ran 15 checks on App Store + Google Play Data, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about App Store + Google Play Data: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.