io.github.rabdulsal/appstore-release-mcp
NPM · APPSTORE-RELEASE-MCP
App Store release pilot — version bump, TestFlight upload, metadata, review submission
Available components
Last scanned (20 hours ago)
Scores higher than 58% of npm servers
Category CI/CD and DevOps
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 77 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 642 tokens (~80/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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 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.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
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 4 Nov 2026 · Analysed npm/appstore-release-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
asc_app_status ~46
Snapshot of the app's release state: latest App Store versions with their review states, and recent builds with processing states. Use this to answer 'where is the release right now?'
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
asc_bump_version ~112
Bump the local app version before a build. Increments the build number (CURRENT_PROJECT_VERSION) and optionally sets a new marketing version. Updates every .xcodeproj/project.pbxproj in the project dir, plus project.yml if the project uses xcodegen, so all sources stay in sync.
| Name | Type | Req | Description |
|---|---|---|---|
| bump_build | boolean | – | Increment the build number |
| marketing_version | string | – | New marketing version, e.g. '1.1.0'. Omit to keep the current one. |
No output schema declared.
No examples provided.
asc_doctor ~58
Verify the release toolchain end-to-end: ASC API credentials, mac-app directory, fastlane, xcodebuild, and (if creds are present) that the app record exists in App Store Connect. Run this first in any release session.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
asc_job_status ~65
Check a build/upload job started by asc_upload_build. Returns status (running/succeeded/failed) and the tail of the log.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job ID returned by asc_upload_build |
| log_lines | integer | – | How many log lines to include |
No output schema declared.
No examples provided.
asc_list_builds ~48
List recent uploaded builds and their processing states (PROCESSING → VALID before they can be submitted). Use after an upload to watch for the build becoming VALID.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
asc_submit_review ~88
Submit the editable App Store version for review: optionally attach a build, then create and submit a review submission. The build must have processingState VALID (check asc_list_builds). This is the point of no return for a release — confirm with the human first.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | – | Build ID from asc_list_builds to attach to the version. Omit if already attached. |
No output schema declared.
No examples provided.
asc_update_metadata ~133
Update App Store listing metadata (description, keywords, what's-new, promotional text) on the currently editable version via the ASC API. If no editable version exists, pass create_version to open a new one.
| Name | Type | Req | Description |
|---|---|---|---|
| create_version | string | – | If no editable version exists, create one with this version string (e.g. '1.1.0') |
| description | string | – | – |
| keywords | string | – | Comma-separated, 100 chars max total |
| locale | string | – | – |
| promotional_text | string | – | – |
| whats_new | string | – | Release notes shown in 'What's New' |
No output schema declared.
No examples provided.
asc_upload_build ~92
Archive, sign, and upload the app to TestFlight via the configured fastlane lane (default: `fastlane beta`; see ASC_FASTLANE_* / ASC_UPLOAD_CMD env vars). Runs asynchronously (5–15 min) — returns a job ID immediately; poll with asc_job_status. Note: if the lane calls increment_build_number you do NOT need asc_bump_version first unless changing the marketing version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.rabdulsal/appstore-release-mcp server?
io.github.rabdulsal/appstore-release-mcp runs locally as an npm package, launched with npx -y appstore-release-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · appstore-release-mcp
claude mcp add rabdulsal-appstore-release-mcp -- npx -y appstore-release-mcp
What is the io.github.rabdulsal/appstore-release-mcp server?
io.github.rabdulsal/appstore-release-mcp is listed in the public MCP registry as io.github.rabdulsal/appstore-release-mcp. App Store release pilot, version bump, TestFlight upload, metadata, review submission. This page covers its npm package (appstore-release-mcp).
Is the io.github.rabdulsal/appstore-release-mcp server safe to use?
io.github.rabdulsal/appstore-release-mcp scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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 io.github.rabdulsal/appstore-release-mcp server expose?
io.github.rabdulsal/appstore-release-mcp exposes 8 tools: asc_doctor, asc_app_status, asc_list_builds, asc_bump_version, asc_upload_build, and 3 more. Their descriptions and schemas cost roughly 642 tokens of context every time the server is loaded.
Is the io.github.rabdulsal/appstore-release-mcp server still maintained?
io.github.rabdulsal/appstore-release-mcp is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.rabdulsal/appstore-release-mcp server under?
io.github.rabdulsal/appstore-release-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.