App Store and Google Play
NPM · @FOREVERWORKS/MCP-APP-STORES
Read and answer App Store and Google Play reviews, and see TestFlight feedback and crash logs.
Available components
Last scanned (10 hours ago)
Scores higher than 58% of npm servers
Category CRM and Sales
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 Security99
- 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
- 7 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to foreverworks/mcps). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1044 tokens (~149/item across 7 items; 7 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 Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "reply_app_store_review" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
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.
- 4 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.88 ▲ functional
- 3 Nov 26 67
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/@foreverworks/mcp-app-stores@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | foreverworks/mcps |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/foreverworks/mcps/.github/workflows/release.yml@refs/tags/release-2026-11-03.2 |
| Rekor log index | 3658001225 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:73b16ca6fcb8d089bc4f921f611f861fc805ae9fd8b191d3217d4f2077f5a5a1a03b373e0f3e73a1acf9c2836e4be498e853294766dcdd02d181df61f |
Background: How many MCP packages publish verified provenance →
Dependencies 23 packages
| Packages resolved | 23 |
|---|---|
| Stale | 7 |
| 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_testflight_crash_log Get a TestFlight crash log ~67
A crash feedback's crash log, saved whole to the server's outbox: the answer gives the file's path, SHA-256 and size, and its first 40 lines.
| Name | Type | Req | Description |
|---|---|---|---|
| submission | string | yes | A crash feedback's id, from list_testflight_feedback. |
No output schema declared.
No examples provided.
health Health ~59
Whether each store's credentials work, and what they reach: the apps the App Store Connect key sees (their bundle ids and Apple ids), and each Play package this server answers for, with one review read. A store without credentials is reported as not configured.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_app_store_reviews List App Store reviews ~206
An app's App Store reviews, newest first unless sorted otherwise: rating, title, text, the reviewer's nickname, the storefront, the date, and the developer's reply with its state (pending until Apple publishes it). Filter by star rating, storefront or whether it has a reply.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | The app: its bundle id ("com.example.app") or its Apple id (digits). Leave it out when the key sees one app (health lists them). |
| cursor | string | – | nextCursor from the previous call, to read on. |
| limit | integer | – | – |
| rating | array | – | Only these star ratings, e.g. [1, 2]. |
| replied | boolean | – | true: only reviews with a published reply; false: only those without one. |
| sort | string | – | – |
| territory | string | – | Only reviews from this storefront: Apple's three-letter code, e.g. USA, ROU, GBR. |
No output schema declared.
No examples provided.
list_play_reviews List Google Play reviews ~145
A package's Google Play reviews with text, newest first: rating, text, author, language, app version, device, the date, and the developer's reply. Google's API returns only reviews written or changed in the last 7 days; older ones are in Play Console's reports.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | nextCursor from the previous call, to read on. |
| limit | integer | – | – |
| package | string | – | The Play package, e.g. "com.example.app". Leave it out when the server answers for one (health lists them). |
| translate_to | string | – | Have Google translate each review into this language, e.g. "en". |
No output schema declared.
No examples provided.
list_testflight_feedback List TestFlight feedback ~158
What testers sent from the TestFlight app, newest first: screenshot feedback (comment and screenshots, at URLs that expire) and crash feedback (comment; get_testflight_crash_log reads the log), each with the tester's e-mail, device, OS and the build number.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | The app: its bundle id ("com.example.app") or its Apple id (digits). Leave it out when the key sees one app (health lists them). |
| cursor | string | – | nextCursor from the previous call of the same kind. |
| kind | string | – | Only crash feedback or only screenshot feedback. Default: both, merged newest first (page through one kind with its cursor). |
| limit | integer | – | – |
No output schema declared.
No examples provided.
reply_app_store_review Reply to an App Store review ~130
Publish a reply under an App Store review, in the developer's name and visible to everyone once Apple publishes it: send only text the user approved for this review. A review that already has a different reply is refused unless replace is true; the same text again sends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| replace | boolean | – | Put this reply in place of the review's existing one. Without it, a review that already has a different reply is refused. |
| review | string | yes | The review's id, from list_app_store_reviews. |
| text | string | yes | The reply, at most 5970 characters. |
No output schema declared.
No examples provided.
reply_play_review Reply to a Google Play review ~159
Publish a reply under a Google Play review, in the developer's name and visible to everyone: send only text the user approved for this review. A review that already has a different reply is refused unless replace is true; the same text again sends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | – | The Play package, e.g. "com.example.app". Leave it out when the server answers for one (health lists them). |
| replace | boolean | – | Put this reply in place of the review's existing one. Without it, a review that already has a different reply is refused. |
| review | string | yes | The review's id, from list_play_reviews. |
| text | string | yes | The reply, at most 350 characters (Google's limit). |
No output schema declared.
No examples provided.
How do I install the App Store and Google Play MCP server?
App Store and Google Play runs locally as an npm package, launched with npx -y @foreverworks/mcp-app-stores. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @foreverworks/mcp-app-stores
claude mcp add com-foreverworks-app-stores -- npx -y @foreverworks/mcp-app-stores
What is the App Store and Google Play MCP server?
App Store and Google Play is an MCP server listed in the public MCP registry as com.foreverworks/app-stores. Read and answer App Store and Google Play reviews, and see TestFlight feedback and crash logs. This page covers its npm package (@foreverworks/mcp-app-stores).
Is the App Store and Google Play MCP server safe to use?
App Store and Google Play scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 and Google Play MCP server expose?
App Store and Google Play exposes 7 tools: get_testflight_crash_log, health, list_app_store_reviews, list_play_reviews, list_testflight_feedback, and 2 more. Their descriptions and schemas cost roughly 924 tokens of context every time the server is loaded.
Is the App Store and Google Play MCP server still maintained?
App Store and Google Play 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 and Google Play MCP server under?
App Store and 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.