App Store + Google Play Data
REMOTE · APPSTORE-MCP-623314400722.US-CENTRAL1.RUN.APP · 2 COMPONENTS
Live App Store and Google Play data: app details, reviews, search, top charts for 175+ storefronts.
Available components
Last scanned (7 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Entertainment and Games
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management43
- Stability observed for 13 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
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
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.
- 5 Nov 26 +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.
- 3 Nov 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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 70
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 · Probed https://appstore-mcp-623314400722.us-central1.run.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.a.run.app | CN=WR2,O=Google Trust Services,C=US | 7 Oct 2026 | 30 Dec 2026 | ECDSA 256 | SHA256-RSA | 53da11951e5eb49012fb872c3cb3e54d |
| SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more | ||||||
| CN=WR2,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a07c4cded100ad9d66a5107b98 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of appstore-mcp-623314400722.us-central1.run.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| run.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://appstore-mcp-623314400722.us-central1.run.app/mcp | Verified | 200 | |
| http (plaintext) | http://appstore-mcp-623314400722.us-central1.run.app/mcp | HTTPS enforced | 302 | https://appstore-mcp-623314400722.us-central1.run.app/mcp |
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 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.
remote · appstore-mcp-623314400722.us-central1.run.app
claude mcp add --transport http thevalkdokk-appstore-data 'https://appstore-mcp-623314400722.us-central1.run.app/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 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.