# App Store & Google Play (npm · appstore-play-mcp)

Read-only access to App Store Connect and Google Play: apps, releases, and reviews.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `appstore-play-mcp`: 84/100 (this document), [markdown](https://verifymcp.io/servers/johnbilousov-appstore-play-mcp/appstore-play-mcp.md), [page](https://verifymcp.io/servers/johnbilousov-appstore-play-mcp/appstore-play-mcp)

## Channel facts

- Registry: `npm`
- Package: `appstore-play-mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 26 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 538 tokens (~107/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (80% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add johnbilousov-appstore-play-mcp -- npx -y appstore-play-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "johnbilousov-appstore-play-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "appstore-play-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "johnbilousov-appstore-play-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "appstore-play-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add johnbilousov-appstore-play-mcp -- npx -y appstore-play-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "johnbilousov-appstore-play-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "appstore-play-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add johnbilousov-appstore-play-mcp --command npx --arg -y --arg appstore-play-mcp
```

### Hermes

```yaml
mcp_servers:
  johnbilousov-appstore-play-mcp:
    command: "npx"
    args: ["-y", "appstore-play-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "johnbilousov-appstore-play-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "appstore-play-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add johnbilousov-appstore-play-mcp -t stdio -c npx -a -y appstore-play-mcp
```

### Other

```json
{
  "mcpServers": {
    "johnbilousov-appstore-play-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "appstore-play-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 84, +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.

### 2026-09-17 (score 83, +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.

### 2026-09-15 (score 82, +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.

### 2026-09-13 (score 81, +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.

### 2026-09-11 (score 80, +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.

### 2026-09-09 (score 79, +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.

### 2026-09-07 (score 78, +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.

### 2026-09-04 (score 77, +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.

## MCP tools (5)

### `stores_health` (~27 tokens)

Check store credentials

Report which stores are configured and whether their credentials work. Call this first when something returns nothing.

Output parameters:

- `mode` (string)
- `stores` (array)

### `list_apps` (~67 tokens)

List apps

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.

Input parameters:

- `store` (string): Which store to read. Defaults to every store that is configured

Output parameters:

- `apps` (array)
- `count` (number)

### `get_app` (~67 tokens)

Get one app

Details for a single app, found by App Store id, Play package name, or bundle id.

Input parameters:

- `appId` (string, required): App Store numeric id, Play package name, or bundle id
- `store` (string): Which store to read. Defaults to every store that is configured

### `get_releases` (~142 tokens)

Get release state

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.

Input parameters:

- `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

Output parameters:

- `count` (number)
- `releases` (array)

### `get_reviews` (~171 tokens)

Get user reviews

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.

Input parameters:

- `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

Output parameters:

- `averageRating` (number|null)
- `count` (number)
- `reviews` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/johnbilousov-appstore-play-mcp/appstore-play-mcp#diagnostics

## Score history

- 2026-09-20: 84
- 2026-09-19: 84
- 2026-09-18: 83
- 2026-09-17: 83
- 2026-09-16: 82
- 2026-09-15: 82
- 2026-09-14: 81
- 2026-09-13: 81
- 2026-09-12: 80
- 2026-09-11: 80
- 2026-09-10: 79
- 2026-09-09: 79
- 2026-09-08: 78
- 2026-09-07: 78
- 2026-09-06: 77
- 2026-09-05: 77
- 2026-09-04: 77
- 2026-09-03: 76
- 2026-09-02: 76
- 2026-09-01: 75
- 2026-08-31: 71
- 2026-08-30: 71
- 2026-08-29: 71
- 2026-08-28: 71
- 2026-08-27: 71
- 2026-08-26: 71
- 2026-08-25: 69
- 2026-08-24: 54

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/appstore-play-mcp
- Socket report: https://socket.dev/npm/package/appstore-play-mcp
- Repository: https://github.com/JohnBilousov/appstore-play-mcp
- Changelog RSS feed: https://verifymcp.io/servers/johnbilousov-appstore-play-mcp/appstore-play-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/johnbilousov-appstore-play-mcp/appstore-play-mcp.json
- HTML version of this page: https://verifymcp.io/servers/johnbilousov-appstore-play-mcp/appstore-play-mcp