App Store & Google Play
NPM · APPSTORE-PLAY-MCP · SCANNED SEP 20
Read-only access to App Store Connect and Google Play: apps, releases, and reviews.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 26 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 538 tokens (~107/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (80% of tools); any adoption earns full credit.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
How do I install the App Store & Google Play MCP server?
App Store & Google Play runs locally as an npm package, launched with npx -y appstore-play-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-play-mcp
claude mcp add johnbilousov-appstore-play-mcp -- npx -y appstore-play-mcp
{
"mcpServers": {
"johnbilousov-appstore-play-mcp": {
"command": "npx",
"args": [
"-y",
"appstore-play-mcp"
]
}
}
} {
"servers": {
"johnbilousov-appstore-play-mcp": {
"command": "npx",
"args": [
"-y",
"appstore-play-mcp"
]
}
}
} codex mcp add johnbilousov-appstore-play-mcp -- npx -y appstore-play-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"johnbilousov-appstore-play-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"appstore-play-mcp"
],
"enabled": true
}
}
} openclaw mcp add johnbilousov-appstore-play-mcp --command npx --arg -y --arg appstore-play-mcp
mcp_servers:
johnbilousov-appstore-play-mcp:
command: "npx"
args: ["-y", "appstore-play-mcp"] {
"McpServers": {
"johnbilousov-appstore-play-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"appstore-play-mcp"
]
}
}
} assistant mcp add johnbilousov-appstore-play-mcp -t stdio -c npx -a -y appstore-play-mcp
{
"mcpServers": {
"johnbilousov-appstore-play-mcp": {
"command": "npx",
"args": [
"-y",
"appstore-play-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/appstore-play-mcp@0.1.2
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 →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 Get one app ~67
Details for a single app, found by App Store id, Play package name, or bundle id.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | App Store numeric id, Play package name, or bundle id |
| store | string | – | Which store to read. Defaults to every store that is configured |
No output schema declared.
No examples provided.
get_releases Get release state ~142
What is live, what is in review, and what is mid-rollout — for one app or the whole portfolio. States are normalised across stores: 'live', 'in_review', 'pending_developer_release', 'rejected', 'draft', 'rolling_out', 'halted'. The store's own wording is kept in rawState. Reading Play tracks opens a temporary edit and deletes it again; nothing is committed.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | – | App Store numeric id, Play package name, or bundle id. Omit to cover every configured app |
| store | string | – | Which store to read. Defaults to every store that is configured |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| releases | array | yes | – |
No examples provided.
get_reviews Get user reviews ~171
Recent user reviews from both stores in one list, newest first. Omit appId to sweep the whole portfolio, and set maxRating to 2 to triage complaints. Note the platform limits: Google Play only returns reviews from roughly the last week, and only for apps that have any.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | – | App Store numeric id, Play package name, or bundle id. Omit to cover every configured app |
| limit | integer | – | Reviews per app, newest first (default 25) |
| maxRating | integer | – | Only reviews at or below this rating. Set to 2 to triage complaints |
| minRating | integer | – | Only reviews at or above this star rating |
| store | string | – | Which store to read. Defaults to every store that is configured |
| Name | Type | Req | Description |
|---|---|---|---|
| averageRating | number|null | yes | – |
| count | number | yes | – |
| reviews | array | yes | – |
No examples provided.
list_apps List apps ~67
Every app reachable with the configured credentials, from both stores. The App Store side is discovered automatically; the Play side comes from PLAY_PACKAGES, because the Play API cannot enumerate a developer's apps.
| Name | Type | Req | Description |
|---|---|---|---|
| store | string | – | Which store to read. Defaults to every store that is configured |
| Name | Type | Req | Description |
|---|---|---|---|
| apps | array | yes | – |
| count | number | yes | – |
No examples provided.
stores_health Check store credentials ~27
Report which stores are configured and whether their credentials work. Call this first when something returns nothing.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | yes | – |
| stores | array | yes | – |
No examples provided.
What is the App Store & Google Play MCP server?
App Store & Google Play is an MCP server listed in the public MCP registry as io.github.JohnBilousov/appstore-play-mcp. Read-only access to App Store Connect and Google Play: apps, releases, and reviews. This page covers its npm package (appstore-play-mcp).
Is the App Store & Google Play MCP server safe to use?
App Store & Google Play scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 MCP server expose?
App Store & Google Play exposes 5 tools: stores_health, list_apps, get_app, get_releases, get_reviews. Their descriptions and schemas cost roughly 474 tokens of context every time the server is loaded.
Is the App Store & Google Play MCP server still maintained?
App Store & Google Play is still listed as active in the MCP registry. We last reached this channel on 20 September 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 MCP server under?
App Store & Google Play declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.