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/pofky/asc-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/plugins/pofky/asc-mcp/plugin)<a href="https://agentmods.dev/plugins/pofky/asc-mcp/plugin"><img src="https://agentmods.dev/badge/plugins/pofky/asc-mcp/plugin/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/plugins/pofky/asc-mcp/plugin"><img src="https://agentmods.dev/badge/plugins/pofky/asc-mcp/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
asc-mcp 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "asc-mcp",
"displayName": "asc-mcp",
"version": "1.9.14",
"description": "Run an App Store release from a conversation: review status, reviews and sales, metadata, screenshots, builds, TestFlight, in-app purchases, submit and release. A local MCP server for App Store Connect plus a review-triage skill.",
"author": {
"name": "Povilas Konopackas",
"url": "https://asc-mcp.pages.dev"
},
"homepage": "https://asc-mcp.pages.dev",
"repository": "https://github.com/pofky/asc-mcp",
"license": "MIT",
"keywords": [
"app-store-connect",
"ios",
"testflight",
"app-store",
"release"
],
"documentationUrl": "https://github.com/pofky/asc-mcp/blob/master/USER_GUIDE.md",
"supportUrl": "https://github.com/pofky/asc-mcp/issues",
"privacyPolicyUrl": "https://asc-mcp-license.remewdy.workers.dev/privacy",
"termsOfServiceUrl": "https://asc-mcp-license.remewdy.workers.dev/terms",
"userConfig": {
"asc_issuer_id": {
"type": "string",
"title": "Issuer ID",
"description": "The UUID from App Store Connect > Users and Access > Integrations > Keys",
"required": true
},
"asc_private_key": {
"type": "file",
"title": "API private key (.p8)",
"description": "Your AuthKey_XXXXXXXXXX.p8 from Apple. Leave empty if it is in ~/.appstoreconnect/private_keys. Read on this machine only, never transmitted."
},
"asc_license_key": {
"type": "string",
"title": "License key (optional)",
"description": "Leave empty for the free tier. A free 7-day trial is available by asking Claude, and needs your email address.",
"sensitive": true
}
},
"mcpServers": {
"asc-mcp": {
"command": "npx",
"args": [
"-y",
"@pofky/[email protected]"
],
"env": {
"ASC_ISSUER_ID": "${user_config.asc_issuer_id}",
"ASC_PRIVATE_KEY_PATH": "${user_config.asc_private_key}",
"ASC_LICENSE_KEY": "${user_config.asc_license_key}",What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 102 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 59 lines scan A 3c272eac238c
asc-mcp is a plugin published in the GitHub repository pofky/asc-mcp (1 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-10.
Other plugins, from other repositories
asc
Production workflows for shipping apps with the unofficial App Store Connect CLI, including builds, TestFlight, metadata, submissions, signing, screenshots, and Apple Ads.
apple-dev-skills
Apple platform development skills (ios-standards, ios26-api-reference, ios-design, accessibility, concurrency, apple-review, ASC build checks, submission prep, verify-against-spec, complete-feature, merge-check, regression-test), App Store Connect MCP server, and build agent.
odh-llm-d
llm-d release orchestration for opendatahub-io.
atlas-publish
Takes the open PRs of the Atlas/Bella monorepo to a registered draft release on either the over-the-air or the App Store lane, classifying between them from the expo-updates native fingerprint rather than from intent — ios.buildNumber sits inside that fingerprint, so a buildNumber bump alone forces a store release.…
android-release-bump
Reusable Android release workflow with version bumps, Play release notes, verification, optional headless emulator QA, and optional Play upload.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.