Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/erayendes/app-store-connect-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/erayendes/app-store-connect-mcp/access-asc-access)<a href="https://agentmods.dev/mcp/erayendes/app-store-connect-mcp/access-asc-access"><img src="https://agentmods.dev/badge/mcp/erayendes/app-store-connect-mcp/access-asc-access/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/erayendes/app-store-connect-mcp/access-asc-access"><img src="https://agentmods.dev/badge/mcp/erayendes/app-store-connect-mcp/access-asc-access.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ASC-Access scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 14d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"ASC-Access": {
"command": "npx",
"args": [
"-y",
"@erayendes/asc-mcp",
"access"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 14d ago Changed cb9f5ba5a47d
- 27d ago First seen · 10 lines scan A 5db7fd14825b
ASC-Access is an MCP server published in the GitHub repository erayendes/app-store-connect-mcp (53 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-19.
Other mcp servers, from other repositories
appstore-connect
MCP server for Apple's App Store Connect API. Manage apps, TestFlight, and more. Runs locally from the asc-mcp npm package.
app-store-connect-mcp
App Store Connect + StoreKit 2: 1,293 Apple operations behind 11 tools, writes confirmed. Runs locally from the @abd3lraouf/app-store-connect-mcp npm package. Needs 5 environment variables to run.
blitz
Give AI agents full control over iOS/macOS development via a native macOS app with 30+ MCP tools. Runs locally from the @blitzdev/blitz-mcp npm package.
app-publish
MCP server for App Store Connect & Google Play Console — iOS/Android app management. Runs locally from the app-publish-mcp npm package. Needs 4 environment variables to run.
appstoreconnect-mcp
App Store Connect for MCP clients: PPP pricing, subscriptions, TestFlight, reviews, reports & more. Runs locally from the @akoskomuves/appstoreconnect-mcp npm package. Needs 4 environment variables to run.
asc-mcp
41 tools to ship an App Store release: metadata, screenshots, builds, TestFlight, IAP, submit. Runs locally from the @pofky/asc-mcp npm package. Needs 4 environment variables to run.