The chain runs from search_rejections to get_rejection_reason for Apple's own message template and the guideline it points at, then to get_solutions for fixes that arrive with a difficulty level and a success rate. get_cases supplies the other half of the picture: what the developer wrote, what Apple wrote back, and whether the appeal held. get_guideline works in the opposite direction, from a section number such as '5.1.1' back to the reasons that cite it.
A lookup service over App Store rejection reasons, the App Store Review Guidelines they cite, and cases reported by developers who hit them.
- Natural-language matching from a pasted rejection message to ranked rejection reasons through search_rejections.
- The full record for a reason through get_rejection_reason: Apple's message template, affected categories, guideline reference and tags.
- Step-by-step fixes from get_solutions, carrying implementation details, code examples, difficulty level and success rates.
- Guideline lookup by section or subsection number through get_guideline — '2.1', '4.3', '5.1.1' — returning the text and the rejection reasons related to it.
- Frequency-ranked rejection reasons from list_common_rejections, ordered by how often reviewers raise them.
- Developer-reported cases through get_cases, filterable by rejection reason, app category or appeal status, each with the developer's message, Apple's response and the resolution.
No account and no key. The rejection message from Apple is worth having on hand, since search_rejections matches against its text.
One command — npx -y appstore-rejections-mcp