# App Store + Google Play Data (remote · appstore-mcp-623314400722.us-central1.run.app)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `appstore-mcp-623314400722.us-central1.run.app`: 76/100 (this document), [markdown](https://verifymcp.io/servers/thevalkdokk-appstore-data/appstore-mcp-623314400722.md), [page](https://verifymcp.io/servers/thevalkdokk-appstore-data/appstore-mcp-623314400722)
- npm · `appstore-data-mcp`: 64/100, [markdown](https://verifymcp.io/servers/thevalkdokk-appstore-data/appstore-data-mcp.md), [page](https://verifymcp.io/servers/thevalkdokk-appstore-data/appstore-data-mcp)

## Channel facts

- Endpoint: `https://appstore-mcp-623314400722.us-central1.run.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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.
- **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 Data MCP server?

App Store + Google Play Data is a hosted endpoint at https://appstore-mcp-623314400722.us-central1.run.app/mcp, so there is nothing to install locally. 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 --transport http thevalkdokk-appstore-data 'https://appstore-mcp-623314400722.us-central1.run.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "thevalkdokk-appstore-data": {
      "url": "https://appstore-mcp-623314400722.us-central1.run.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "thevalkdokk-appstore-data": {
      "type": "http",
      "url": "https://appstore-mcp-623314400722.us-central1.run.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.thevalkdokk-appstore-data]
url = "https://appstore-mcp-623314400722.us-central1.run.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thevalkdokk-appstore-data": {
      "type": "remote",
      "url": "https://appstore-mcp-623314400722.us-central1.run.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add thevalkdokk-appstore-data --url 'https://appstore-mcp-623314400722.us-central1.run.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  thevalkdokk-appstore-data:
    url: "https://appstore-mcp-623314400722.us-central1.run.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "thevalkdokk-appstore-data": {
      "Transport": "http",
      "Url": "https://appstore-mcp-623314400722.us-central1.run.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add thevalkdokk-appstore-data -t streamable-http -u 'https://appstore-mcp-623314400722.us-central1.run.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "thevalkdokk-appstore-data": {
      "type": "http",
      "url": "https://appstore-mcp-623314400722.us-central1.run.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-05 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

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

### 2026-10-31 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 70)

First indexed and scored.

## MCP tools (5)

### `search_apps` (~155 tokens)

Search apps

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

Input parameters:

- `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, required): Keyword(s) to search for, e.g. 'meditation', 'photo editor'.
- `store` (string): Store to query: "ios" (Apple App Store) or "android" (Google Play).

### `get_app` (~161 tokens)

App details

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

Input parameters:

- `app_id` (string, required): 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).

### `get_app_reviews` (~166 tokens)

App reviews

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.

Input parameters:

- `app_id` (string, required): 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).

### `top_charts` (~186 tokens)

Top charts

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

Input parameters:

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

### `list_categories` (~85 tokens)

Store categories

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

Input parameters:

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/thevalkdokk-appstore-data/appstore-mcp-623314400722#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 70
- 2026-10-23: 70

## Common questions

### 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 hosted endpoint (https://appstore-mcp-623314400722.us-central1.run.app/mcp).

### Is the App Store + Google Play Data MCP server safe to use?

App Store + Google Play Data scores 76 out of 100 on VerifyMCP. 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.

### Does the App Store + Google Play Data MCP server require authentication?

No. We connected to App Store + Google Play Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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 did VerifyMCP test on the App Store + Google Play Data MCP server?

VerifyMCP ran 13 checks on App Store + Google Play Data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://appstore-mcp-623314400722.us-central1.run.app/mcp
- Authorisation metadata: https://appstore-mcp-623314400722.us-central1.run.app/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/TheValkDokk/appstore-data-mcp
- Changelog RSS feed: https://verifymcp.io/servers/thevalkdokk-appstore-data/appstore-mcp-623314400722.xml
- Changelog JSON feed: https://verifymcp.io/servers/thevalkdokk-appstore-data/appstore-mcp-623314400722/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/thevalkdokk-appstore-data/appstore-mcp-623314400722.json
- HTML version of this page: https://verifymcp.io/servers/thevalkdokk-appstore-data/appstore-mcp-623314400722