io.github.rabdulsal/appstore-release-mcp
NPM · APPSTORE-RELEASE-MCP · SCANNED AUG 3
App Store release pilot — version bump, TestFlight upload, metadata, review submission
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 27 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · appstore-release-mcp
claude mcp add rabdulsal-appstore-release-mcp -- npx -y appstore-release-mcp
codex mcp add rabdulsal-appstore-release-mcp -- npx -y appstore-release-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rabdulsal-appstore-release-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"appstore-release-mcp"
],
"enabled": true
}
}
} openclaw mcp add rabdulsal-appstore-release-mcp --command npx --arg -y --arg appstore-release-mcp
mcp_servers:
rabdulsal-appstore-release-mcp:
command: "npx"
args: ["-y", "appstore-release-mcp"] {
"mcpServers": {
"rabdulsal-appstore-release-mcp": {
"command": "npx",
"args": [
"-y",
"appstore-release-mcp"
]
}
}
} 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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +46
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 45
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.