store-review-check MCP server
Commit Oct 16, 2026Identifies App Store and Google Play rejection risks in iOS, Android, Flutter, and Expo projects by scanning configuration files and store listings.
Also known as Rocketech-Software-Development/store-review-check
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 16, 2026
- License
- MIT
What is store-review-check MCP?
store-review-check identifies App Store and Google Play rejection risks in iOS, Android, Flutter, and Expo projects by scanning configuration files and store listings.
Summary generated from the project's README
About store-review-check MCP server
Identifying App Store and Google Play rejection risks before submission is what store-review-check enables for mobile developers. It scans configuration files and store listings in iOS, Android, Flutter, and Expo projects to find potential compliance issues. The tool works as a CLI or an MCP server, allowing it to be integrated into a terminal, a continuous integration pipeline, or an AI coding assistant.
By examining files like Info.plist, AndroidManifest.xml, package.json, and pubspec.yaml, the server flags missing privacy manifests, incorrect permission strings, or outdated billing libraries. It also checks store listing text for length limits and prohibited terminology. The tool is designed to run locally, ensuring that no project data leaves your machine. Unlike many automated tools, it does not use AI for its checks, providing consistent and predictable reports based on static rules.
What you can do with it
- 1Verify iOS privacy complianceCheck if your Swift or Objective-C code uses required reason APIs without declaring them in the privacy manifest.
- 2Audit Android SDK requirementsEnsure your target SDK version meets the current Google Play requirements to avoid being hidden from new users.
- 3Validate social app featuresConfirm that dating or social apps include necessary tools like report and block functionality for user-generated content.
- 4Check store listing metadataScan your app store descriptions and titles for length violations or prohibited keywords.
Written from the project's README. Every use case is checked against a quote from it.
How to install store-review-check MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall store-review-check MCP in Claude Code
$ claude mcp add store-review-check -- npx -y store-review-checkInstall store-review-check MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"store-review-check": {
"command": "npx",
"args": [
"-y",
"store-review-check"
]
}
}
}Install store-review-check MCP in VS Code
.vscode/mcp.json
{
"servers": {
"store-review-check": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"store-review-check"
]
}
}
}Install store-review-check MCP in VS Code CLI
$ code --add-mcp '{"name":"store-review-check","type":"stdio","command":"npx","args":["-y","store-review-check"]}'Install store-review-check MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"store-review-check": {
"command": "npx",
"args": [
"-y",
"store-review-check"
]
}
}
}Install store-review-check MCP in Codex
$ codex mcp add store-review-check -- npx -y store-review-checkInstall store-review-check MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.store-review-check] command = "npx" args = ["-y", "store-review-check"]
Install store-review-check MCP in Gemini CLI
$ gemini mcp add -s user store-review-check npx -- -y store-review-checkInstall store-review-check MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"store-review-check": {
"command": "npx",
"args": [
"-y",
"store-review-check"
]
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablerocketech-software-development/store-review-check is public and reachablegithub.com/rocketech-software-development/store-review-check ↗Pass
- Package names this repository as its sourcestore-review-check names rocketech-software-development/store-review-check as sourcenpmjs.com/package/store-review-check ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-16github.com/rocketech-software-development/store-review-check ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from store-review-checkPass
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubstore-review-check
Find App Store and Google Play rejection risks in an iOS, Android, Flutter, React Native or Expo project before you submit it. It runs as a CLI and as an MCP server, so you can use it from a terminal, from CI, or from an AI coding assistant.
npx store-review-check ./my-app
It reads Info.plist, entitlements, PrivacyInfo.xcprivacy, StoreKit configuration files, AndroidManifest.xml, Gradle files and version catalogs, pubspec.yaml, package.json and Expo app.json, plus your store listing text if you provide it. Each finding names the guideline section, links to the official Apple or Google page and says how to fix the problem.
The rule set leans toward problems dating and social apps run into, such as user-generated content without report and block tools, missing account deletion, social login without Sign in with Apple and subscription terms. Most rules apply to any app.
There is no AI in the checks. The same project gives the same report every time, and nothing leaves your machine.
Contents
- What it checks
- Sample output
- Install and run
- Store listing data
- Use it as an MCP server
- Rules
- How it works, and what it can't see
- Contributing
- Credits
What it checks
- iOS permissions: if the code or a library uses the camera, photos, location, contacts, microphone, tracking and so on, the matching
NS…UsageDescriptionkey has to exist and say why. Empty, placeholder and Expo default strings are flagged too. - iOS privacy manifest: whether the app has
PrivacyInfo.xcprivacy, and whether your own Swift and Objective-C code uses required reason APIs (UserDefaults, file timestamps, disk space, boot time, active keyboards) without declaring them. - Accounts: account creation without in-app deletion, the Google Play web deletion link, third-party login without Sign in with Apple, and a missing demo account for reviewers.
- User-generated content: report, block, content filtering, published contact details and terms acceptance, plus an age check for dating apps.
- Payments: subscriptions shorter than seven days, missing restore purchases, missing terms and price details, third-party payment SDKs for digital goods, and an outdated Play Billing Library.
- Android platform:
targetSdkagainst the current Google Play requirement, restricted permissions (SMS, call log, all-files access and others), photo and video permissions, background location, and sensitive permissions with no disclosure screen. - Store listing: length limits, price and ranking claims, other apps' names in keywords, mentions of other platforms, emoji and ALL CAPS in Play titles, and wording tied to hookup or anonymous chat apps.
Sample output
Output of a run against the risky Flutter dating app in test/fixtures/flutter-dating-risky, errors only:
$ npx store-review-check test/fixtures/flutter-dating-risky --min-severity error
store-review-check 0.1.0 · rules 2026.10.15
Project: test/fixtures/flutter-dating-risky
Platforms: ios, android (flutter)
Listing data: store-review.yaml
Dating app: yes (app.category is "dating")
User content: yes (dating apps show profiles, photos and messages)
Accounts: yes (dependency firebase_auth (pubspec.yaml), lib/main.dart)
ERRORS (9)
✖ android.billing-library Google Play Billing Library version is no longer accepted
com.android.billingclient:billing:6.2.1 in android/app/build.gradle. Play requires Billing Library 8 or later since 2026-08-31 (extension until 2026-11-01).
Files: android/app/build.gradle
Fix: Update com.android.billingclient:billing (or billing-ktx) to 8.x or newer. If billing comes from a plugin (in_app_purchase, RevenueCat, react-native-iap), update the plugin to a release built on PBL 8+.
See: Google Play · Google Play Billing Library version deprecation · https://developer.android.com/google/play/billing/deprecation-faq
✖ android.target-sdk targetSdk is below the current Google Play requirement
targetSdk is 34 (android/app/build.gradle). Google Play requires 36 or higher for new apps and updates since 2026-08-31 (extension requests until 2026-11-01). At 34 an already published app is also hidden from new users on newer Android versions. Wear OS and Android Automotive OS apps need API 35; Android TV and Android XR apps need API 34.
Files: android/app/build.gradle
Fix: Raise targetSdk (and compileSdk) to 36 in the app module's build.gradle, then test the Android 15 and 16 behavior changes.
See: Google Play · Meet Google Play's target API level requirement · https://developer.android.com/google/play/requirements/target-sdk
Google Play · Target API level requirements for Google Play apps · https://support.google.com/googleplay/android-developer/answer/11926878
✖ ios.privacy-manifest-required-reason Required reason API used but not declared in the privacy manifest
User defaults APIs are used in ios/Runner/AppDelegate.swift but NSPrivacyAccessedAPICategoryUserDefaults is not declared in the app (no PrivacyInfo.xcprivacy exists yet).
Files: ios/Runner/AppDelegate.swift
Fix: Add a dictionary to NSPrivacyAccessedAPITypes with NSPrivacyAccessedAPIType set to the category and NSPrivacyAccessedAPITypeReasons set to the approved reason code that matches your use (for example CA92.1 for UserDefaults read and written only by the app itself).
See: Apple · Describing use of required reason API · https://developer.apple.com/documentation/bundleresources/describing-use-of-required-reason-api
Apple · NSPrivacyAccessedAPIType · https://developer.apple.com/documentation/bundleresources/app-privacy-configuration/nsprivacyaccessedapitypes/nsprivacyaccessedapitype
✖ ios.purpose-string-missing Protected resource used without a purpose string
- Camera is used (dependency image_picker (pubspec.yaml)) but NSCameraUsageDescription is missing from ios/Runner/Info.plist.
Files: ios/Runner/Info.plist, pubspec.yaml
- Location (while in use) is used (dependency geolocator (pubspec.yaml)) but NSLocationWhenInUseUsageDescription is missing from ios/Runner/Info.plist.
Files: ios/Runner/Info.plist, pubspec.yaml
Fix: Add the key to Info.plist (or to INFOPLIST_KEY_* build settings, or expo.ios.infoPlist) with one specific sentence: what the app uses it for, e.g. "Your camera is used to take profile photos and verify your identity."
See: Apple 5.1.1(ii) · Data Collection and Storage: Permission · https://developer.apple.com/app-store/review/guidelines/#5.1.1
Apple · Requesting access to protected resources · https://developer.apple.com/documentation/uikit/requesting-access-to-protected-resources
✖ ios.subscription-min-period Auto-renewable subscription shorter than seven days
Subscription com.example.amoryx.boost3day renews every P3D (3 days) in ios/Runner/Products.storekit.
Files: ios/Runner/Products.storekit
Fix: Use a period of one week or longer. For short boosts (a common dating-app product) sell a consumable in-app purchase instead.
See: Apple 3.1.2(a) · Subscriptions: Permissible uses · https://developer.apple.com/app-store/review/guidelines/#3.1.2a
✖ listing.field-limits Store listing field is over the length limit
appStore.name is 38 characters; the limit is 30.
Fix: Shorten the field. App Store Connect and Play Console will not save values over the limit.
See: Apple 2.3.7 · Accurate Metadata: app names · https://developer.apple.com/app-store/review/guidelines/#2.3.7
Apple · App information (name, subtitle) · https://developer.apple.com/help/app-store-connect/reference/app-information/app-information
Apple · Platform version information (keywords, description, promotional text) · https://developer.apple.com/help/app-store-connect/reference/app-information/platform-version-information
Google Play · Best practice for your store listing · https://support.google.com/googleplay/android-developer/answer/13393723
✖ listing.privacy-policy No privacy policy URL in the store listing data
links.privacyPolicyUrl is not set.
Fix: Publish a privacy policy that covers what you collect, who you share it with, retention and how to delete data. Set links.privacyPolicyUrl in store-review.yaml and link it in the app's settings.
See: Apple 5.1.1(i) · Data Collection and Storage: Privacy Policies · https://developer.apple.com/app-store/review/guidelines/#5.1.1
Google Play · Provide information for Google Play's Data safety section · https://support.google.com/googleplay/android-developer/answer/10787469
✖ listing.prohibited-dating-terms Listing uses terms tied to hookup or compensated dating
appStore.description contains "hookup".
Fix: Remove these terms from the name, subtitle, keywords and descriptions, and make sure the product itself does not offer what they describe.
See: Apple 1.1.4 · Objectionable Content: overtly sexual material · https://developer.apple.com/app-store/review/guidelines/#1.1.4
Google Play · Inappropriate Content: sexual content · https://support.google.com/googleplay/android-developer/answer/9878810
Summary: 9 errors, 22 warnings, 5 info · 40 rules checked, 0 not applicable · 9 files scanned
27 findings below --min-severity not shown.
Static checks against public App Store and Google Play guidelines. A clean report does not guarantee approval: review is done by people, and policies change. Treat findings as a checklist, not a verdict.
$ npx store-review-check test/fixtures/flutter-dating-risky
store-review-check 0.1.0 · rules 2026.10.15
Project: test/fixtures/flutter-dating-risky
Platforms: ios, android (flutter)
Listing data: store-review.yaml
Dating app: yes (app.category is "dating")
User content: yes (dating apps show profiles, photos and messages)
Accounts: yes (dependency firebase_auth (pubspec.yaml), lib/main.dart)
ERRORS (9)
✖ android.billing-library Google Play Billing Library version is no longer accepted
com.android.billingclient:billing:6.2.1 in android/app/build.gradle. Play requires Billing Library 8 or later since 2026-08-31 (extension until 2026-11-01).
Files: android/app/build.gradle
Fix: Update com.android.billingclient:billing (or billing-ktx) to 8.x or newer. If billing comes from a plugin (in_app_purchase, RevenueCat, react-native-iap), update the plugin to a release built on PBL 8+.
See: Google Play · Google Play Billing Library version deprecation · https://developer.android.com/google/play/billing/deprecation-faq
✖ android.target-sdk targetSdk is below the current Google Play requirement
targetSdk is 34 (android/app/build.gradle). Google Play requires 36 or higher for new apps and updates since 2026-08-31 (extension requests until 2026-11-01). At 34 an already published app is also hidden from new users on newer Android versions. Wear OS and Android Automotive OS apps need API 35; Android TV and Android XR apps need API 34.
Files: android/app/build.gradle
Fix: Raise targetSdk (and compileSdk) to 36 in the app module's build.gradle, then test the Android 15 and 16 behavior changes.
See: Google Play · Meet Google Play's target API level requirement · https://developer.android.com/google/play/requirements/target-sdk
Google Play · Target API level requirements for Google Play apps · https://support.google.com/googleplay/android-developer/answer/11926878
✖ ios.privacy-manifest-required-reason Required reason API used but not declared in the privacy manifest
User defaults APIs are used in ios/Runner/AppDelegate.swift but NSPrivacyAccessedAPICategoryUserDefaults is not declared in the app (no PrivacyInfo.xcprivacy exists yet).
Files: ios/Runner/AppDelegate.swift
Fix: Add a dictionary to NSPrivacyAccessedAPITypes with NSPrivacyAccessedAPIType set to the category and NSPrivacyAccessedAPITypeReasons set to the approved reason code that matches your use (for example CA92.1 for UserDefaults read and written only by the app itself).
See: Apple · Describing use of required reason API · https://developer.apple.com/documentation/bundleresources/describing-use-of-required-reason-api
Apple · NSPrivacyAccessedAPIType · https://developer.apple.com/documentation/bundleresources/app-privacy-configuration/nsprivacyaccessedapitypes/nsprivacyaccessedapitype
✖ ios.purpose-string-missing Protected resource used without a purpose string
- Camera is used (dependency image_picker (pubspec.yaml)) but NSCameraUsageDescription is missing from ios/Runner/Info.plist.
Files: ios/Runner/Info.plist, pubspec.yaml
- Location (while in use) is used (dependency geolocator (pubspec.yaml)) but NSLocationWhenInUseUsageDescription is missing from ios/Runner/Info.plist.
Files: ios/Runner/Info.plist, pubspec.yaml
Fix: Add the key to Info.plist (or to INFOPLIST_KEY_* build settings, or expo.ios.infoPlist) with one specific sentence: what the app uses it for, e.g. "Your camera is used to take profile photos and verify your identity."
See: Apple 5.1.1(ii) · Data Collection and Storage: Permission · https://developer.apple.com/app-store/review/guidelines/#5.1.1
Apple · Requesting access to protected resources · https://developer.apple.com/documentation/uikit/requesting-access-to-protected-resources
✖ ios.subscription-min-period Auto-renewable subscription shorter than seven days
Subscription com.example.amoryx.boost3day renews every P3D (3 days) in ios/Runner/Products.storekit.
Files: ios/Runner/Products.storekit
Fix: Use a period of one week or longer. For short boosts (a common dating-app product) sell a consumable in-app purchase instead.
See: Apple 3.1.2(a) · Subscriptions: Permissible uses · https://developer.apple.com/app-store/review/guidelines/#3.1.2a
✖ listing.field-limits Store listing field is over the length limit
appStore.name is 38 characters; the limit is 30.
Fix: Shorten the field. App Store Connect and Play Console will not save values over the limit.
See: Apple 2.3.7 · Accurate Metadata: app names · https://developer.apple.com/app-store/review/guidelines/#2.3.7
Apple · App information (name, subtitle) · https://developer.apple.com/help/app-store-connect/reference/app-information/app-information
Apple · Platform version information (keywords, description, promotional text) · https://developer.apple.com/help/app-store-connect/reference/app-information/platform-version-information
Google Play · Best practice for your store listing · https://support.google.com/googleplay/android-developer/answer/13393723
✖ listing.privacy-policy No privacy policy URL in the store listing data
links.privacyPolicyUrl is not set.
Fix: Publish a privacy policy that covers what you collect, who you share it with, retention and how to delete data. Set links.privacyPolicyUrl in store-review.yaml and link it in the app's settings.
See: Apple 5.1.1(i) · Data Collection and Storage: Privacy Policies · https://developer.apple.com/app-store/review/guidelines/#5.1.1
Google Play · Provide information for Google Play's Data safety section · https://support.google.com/googleplay/android-developer/answer/10787469
✖ listing.prohibited-dating-terms Listing uses terms tied to hookup or compensated dating
appStore.description contains "hookup".
Fix: Remove these terms from the name, subtitle, keywords and descriptions, and make sure the product itself does not offer what they describe.
See: Apple 1.1.4 · Objectionable Content: overtly sexual material · https://developer.apple.com/app-store/review/guidelines/#1.1.4
Google Play · Inappropriate Content: sexual content · https://support.google.com/googleplay/android-developer/answer/9878810
WARNINGS (22)
▲ account.deletion Account creation without in-app account deletion
Accounts are created (dependency firebase_auth (pubspec.yaml), lib/main.dart) but no delete-account flow was found in source or strings.
Fix: Add Settings > Delete account that deletes the account and its data server-side (not just deactivation). If deletion lives in a WebView or on the server, declare it with features.accountDeletionInApp: true in store-review.yaml.
See: Apple 5.1.1(v) · Data Collection and Storage: Account Sign-In · https://developer.apple.com/app-store/review/guidelines/#5.1.1v
Apple · Offering account deletion in your app · https://developer.apple.com/support/offering-account-deletion-in-your-app/
Google Play · Understanding Google Play's app account deletion requirements · https://support.google.com/googleplay/android-developer/answer/13327111
▲ account.deletion-web-link No web link for account deletion (Google Play)
No links.accountDeletionUrl in the store listing data. Google Play asks for this link in the Data safety form.
Fix: Publish a page (for example https://example.com/delete-account) that explains the steps and accepts requests, then set links.accountDeletionUrl in store-review.yaml and add it in Play Console.
See: Google Play · Understanding Google Play's app account deletion requirements · https://support.google.com/googleplay/android-developer/answer/13327111
▲ android.background-location ACCESS_BACKGROUND_LOCATION declared
ACCESS_BACKGROUND_LOCATION declared in android/app/src/main/AndroidManifest.xml.
Files: android/app/src/main/AndroidManifest.xml
Fix: Request location only while the app is in use. If background access is truly core, prepare the declaration form and a video of the disclosure flow.
See: Google Play · Location Permissions · https://support.google.com/googleplay/android-developer/answer/9799150
▲ android.permission-rationale Sensitive runtime permissions with no disclosure or rationale found
Declared: CAMERA, ACCESS_FINE_LOCATION, ACCESS_BACKGROUND_LOCATION, READ_CONTACTS, RECEIVE_SMS, READ_MEDIA_IMAGES. No rationale or disclosure code found (shouldShowRequestPermissionRationale, a rationale dialog, or permission_handler's shouldShowRequestRationale).
Files: android/app/src/main/AndroidManifest.xml
Fix: Before each runtime request, show a screen that says what data you access and why, and handle the shouldShowRequestPermissionRationale case. Request permissions in context (camera when the user taps Add photo), not all at launch.
See: Google Play · User Data: Prominent Disclosure & Consent Requirement · https://support.google.com/googleplay/android-developer/answer/10144311
Google Play · Request runtime permissions · https://developer.android.com/training/permissions/requesting
▲ android.photo-video-permissions READ_MEDIA_IMAGES / READ_MEDIA_VIDEO declared
READ_MEDIA_IMAGES declared in android/app/src/main/AndroidManifest.xml.
Files: android/app/src/main/AndroidManifest.xml
Fix: Use the Android Photo Picker (androidx.activity 1.7.0+ PickVisualMedia; Flutter image_picker and Expo ImagePicker use it) and remove the permissions. If a library adds them through manifest merging, remove them with tools:node="remove".
See: Google Play · Photo and Video Permissions (restricted permissions with minimum scope alternatives) · https://support.google.com/googleplay/android-developer/answer/14115180
▲ android.restricted-permissions Restricted permission declared
RECEIVE_SMS declared in android/app/src/main/AndroidManifest.xml. SMS and Call Log permissions are limited to default SMS/phone handlers and listed exceptions. For one-time codes use the SMS Retriever or SMS User Consent API.
Files: android/app/src/main/AndroidManifest.xml
Fix: Remove the permission (check merged manifests from libraries too), or prepare the declaration for the approved use case listed in the policy.
See: Google Play · Permissions and APIs that Access Sensitive Information · https://support.google.com/googleplay/android-developer/answer/9888170
▲ dating.age-gate Dating app with no age check found
Dating app (app.category is "dating") with no date-of-birth or age check found.
Fix: Ask for date of birth at sign-up and block under-18s (or use Apple's Declared Age Range API), state the minimum age in your terms, and declare it as age assurance in the rating questionnaires. Set features.ageGate: true when done.
See: Apple 2.3.6 · Accurate Metadata: age rating · https://developer.apple.com/app-store/review/guidelines/#2.3.6
Apple · Age ratings values and definitions · https://developer.apple.com/help/app-store-connect/reference/app-information/age-ratings-values-and-definitions
Google Play · Content Ratings · https://support.google.com/googleplay/android-developer/answer/9898843
Google Play · User Generated Content (incidental sexual content) · https://support.google.com/googleplay/android-developer/answer/9876937
▲ iap.subscription-disclosure Subscription terms, price or legal links missing
Subscriptions found: no links.termsOfUseUrl (Apple requires a Terms of Use link in the app and in App Store metadata); no plans listed under subscriptions, so price and period cannot be checked.
Fix: Set links.termsOfUseUrl and links.privacyPolicyUrl, list each plan under subscriptions (price, period, trial) in store-review.yaml, and put the same facts on the paywall next to the buy button.
See: Apple 3.1.2(c) · Subscriptions: Subscription Information · https://developer.apple.com/app-store/review/guidelines/#3.1.2c
Apple · Auto-renewable subscriptions · https://developer.apple.com/app-store/subscriptions/
Google Play · Subscriptions · https://support.google.com/googleplay/android-developer/answer/9900533
▲ iap.third-party-payments Third-party payment SDK in an app that sells digital features
Found dependency flutter_stripe (pubspec.yaml). Make sure it only charges for physical goods or real-world services. This is a dating app, so premium features count as digital goods.
Files: pubspec.yaml
Fix: Sell digital features through StoreKit / Play Billing. Keep Stripe or PayPal only for physical goods or real-world services, or follow the specific external-link programs for the storefronts you target.
See: Apple 3.1.1 · In-App Purchase · https://developer.apple.com/app-store/review/guidelines/#3.1.1
Google Play · Payments · https://support.google.com/googleplay/android-developer/answer/9858738
▲ ios.privacy-manifest-missing No app privacy manifest (PrivacyInfo.xcprivacy)
No PrivacyInfo.xcprivacy found for the app target. Expected something like ios/Runner/PrivacyInfo.xcprivacy.
Fix: In Xcode choose File > New File > App Privacy, add it to the app target, and declare collected data types and each required reason API category your own code uses. Flutter: ios/Runner/PrivacyInfo.xcprivacy. Expo: expo.ios.privacyManifests in app.json.
See: Apple · Privacy manifest files · https://developer.apple.com/documentation/bundleresources/privacy-manifest-files
Apple · Describing use of required reason API · https://developer.apple.com/documentation/bundleresources/describing-use-of-required-reason-api
▲ ios.purpose-string-quality Purpose string is
store-review-check MCP questions
How do I add store-review-check MCP to Claude Code?
Run claude mcp add store-review-check -- npx -y store-review-check in your terminal. Add --scope user to make it available in every project.
How do I add store-review-check MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Does this tool use AI to perform checks?
No, the tool uses static checks against public guidelines and does not use AI.
What kind of files does the tool scan?
It scans various configuration files including Info.plist, AndroidManifest.xml, pubspec.yaml, package.json, and Expo app.json.
Does a clean report guarantee app approval?
No, a clean report is a checklist and does not guarantee approval since human reviewers perform the final check.