Appstore Connect (ryaker) MCP Server
@ryaker/appstore-connect-mcp
npm
v1.0.0
Published by @ryaker — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Apple Store Connect MCP Server with OAuth authentication support for Claude Desktop/iOS
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
high Shell/command execution in server code (dist/handlers/xcode.js)MTC-SRC-002
In the server's implementation (`dist/handlers/xcode.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { exec } from 'child_process'; import { promisify } from 'util'; import { existsSync, statSync } from 'fs'; con
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/handlers/xcode.js
high Shell/command execution in server code (dist/src/handlers/xcode.js)MTC-SRC-002
In the server's implementation (`dist/src/handlers/xcode.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { exec } from 'child_process'; import { promisify } from 'util'; import { existsSync, statSync } from 'fs'; con
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/src/handlers/xcode.js
Tools 39
Each tool and what it can reach — statically extracted from the published source.
download_analytics_report_segmentingests untrusted inputdownload_finance_reportingests untrusted inputdownload_sales_reportingests untrusted inputget_sales_reportingests untrusted inputlist_analytics_report_segmentsingests untrusted inputadd_tester_to_beta_groupno sensitive capabilityadd_tester_to_groupno sensitive capabilitycreate_analytics_report_requestno sensitive capabilitycreate_app_store_versionno sensitive capabilitycreate_bundle_idno sensitive capability
Show 29 more tools ↓
disable_bundle_capabilityno sensitive capabilityenable_bundle_capabilityno sensitive capabilityget_analyticsno sensitive capabilityget_app_availabilityno sensitive capabilityget_app_infono sensitive capabilityget_app_info_detailsno sensitive capabilityget_app_pricingno sensitive capabilityget_app_store_version_localizationno sensitive capabilityget_beta_feedback_screenshotno sensitive capabilityget_buildsno sensitive capabilityget_bundle_id_infono sensitive capabilityget_customer_reviewsno sensitive capabilityget_in_app_purchasesno sensitive capabilityget_sales_datano sensitive capabilitylist_analytics_reportsno sensitive capabilitylist_app_store_version_localizationsno sensitive capabilitylist_app_store_versionsno sensitive capabilitylist_appsno sensitive capabilitylist_beta_feedback_screenshotsno sensitive capabilitylist_beta_groupsno sensitive capabilitylist_buildsno sensitive capabilitylist_bundle_idsno sensitive capabilitylist_certificatesno sensitive capabilitylist_devicesno sensitive capabilitylist_group_testersno sensitive capabilitylist_schemesno sensitive capabilitylist_usersno sensitive capabilityremove_tester_from_groupno sensitive capabilityupdate_app_store_version_localizationno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (39 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.0 latest |
A 93/100 | 2 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @ryaker/appstore-connect-mcp --onlineOther implementations of Appstore Connect 6
Independent packages implementing the same tool, scanned with the same engine. Compare all 7 side by side →
MCP server for Apple App Store Connect API
Code Mode MCP server for App Store Connect — 923 endpoints through 2 tools
Model Context Protocol server for the Apple App Store Connect API
MCP server for the Apple App Store Connect API — exposes all 1200+ operations as MCP tools. Supports local (stdio) and remote (HTTP) deployment.
MCP server for interacting with App Store Connect
A Model Context Protocol (MCP) server for interacting with the App Store Connect API. This server provides tools for managing apps, beta testers, bundle IDs, devices, app metadata, and capabilities in App Store Connect.
More in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.