App Store Rejection Help
Server Details
Explains App Store and Google Play rejections in plain English and what to change to pass review.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
explain_guideline and explain_rejection both explain policy rules, but the descriptions draw a clear boundary: one takes a single identifier, the other a pasted rejection message. list_common_rejections is unambiguously a discovery tool. Minor risk remains that an agent pastes a single guideline into explain_rejection or vice versa, but the descriptions guide selection well.
All three tools use consistent snake_case with a leading verb (explain, explain, list) followed by the target noun. The pattern is predictable and readable, with no mixing of conventions.
Three tools is on the lean side but fits a narrowly scoped helper domain: explain one rule, explain a full rejection, or enumerate coverage. Each tool has a distinct job and none feels redundant or padded.
The core lifecycle is covered: discover what's supported, look up a known guideline/code, and diagnose a full rejection message. A keyword or reverse search (e.g. find guidelines by topic or platform filter) is a mild gap, but agents can work around it via list_common_rejections.
Available Tools
3 toolsexplain_guidelineExplain one guideline or policyARead-onlyIdempotentInspect
Explain a single App Store Review Guideline (e.g. "4.2", "2.5.19", "5.1.1(v)"), an ITMS upload error ("ITMS-91053") or a Google Play policy name ("Data safety section"). Use it when there is no full rejection message.
Inputs: reference (required).
explain_rejectionExplain a store rejectionARead-onlyIdempotentInspect
Paste an App Store or Google Play rejection message and get, for each guideline, ITMS code or Play policy it cites: what it means, what to change, and the related automated checks. Nothing is stored.
Inputs: message (required).
list_common_rejectionsList common rejectionsARead-onlyIdempotentInspect
List the App Store guidelines, ITMS codes and Google Play policies this server has a plain-English guide for.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Audit apps against App Store, Google Play and Google OAuth review rules; get the required docs.
Review, versions, builds and ratings for your apps
App Store + Google Play reviews: top complaints, what got worse by version, cross-store comparisons.
Manage App Store and Google Play apps: listings, screenshots, builds, releases, reviews, metrics.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to diagnose and fix iOS app issues that cause App Store rejections, such as missing privacy manifests, permission strings, and test credentials, before submission.167 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to scan an iOS, Android, Flutter, React Native or Expo project for App Store and Google Play rejection risks, returning deterministic findings that cite the guideline section, link to the official Apple or Google page and explain how to fix each problem. Nothing leaves the machine and no AI is used in the checks.8 npmMIT
- AlicenseNot gradedqualityCmaintenanceApple App Store Pre-Flight Guideline Auditor & Privacy Manifest Generator7 npmMIT
- AlicenseAqualityDmaintenanceAn MCP server that gives AI assistants access to a curated database of Apple App Store rejection reasons, solutions, and real-world cases.622 npm16MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.