Asc (SardorbekR) MCP Server

asc-mcp npm v1.1.0

Published by sardorbekr — 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.

MCP server for Apple's App Store Connect API - manage iOS, macOS, tvOS, and visionOS apps with AI

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

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 − 1 = 99. 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:

PointsAdoption-risk factor
−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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 38

Each tool and what it can reach — statically extracted from the published source.

  • add_beta_testerno sensitive capability
  • create_app_versionno sensitive capability
  • create_bundle_idno sensitive capability
  • create_version_localizationno sensitive capability
  • delete_bundle_idno sensitive capability
  • delete_version_localizationno sensitive capability
  • get_appno sensitive capability
  • get_app_availabilityno sensitive capability
  • get_app_price_scheduleno sensitive capability
  • get_app_versionno sensitive capability
Show 28 more tools ↓
  • get_buildno sensitive capability
  • get_bundle_idno sensitive capability
  • get_deviceno sensitive capability
  • get_price_point_equalizationsno sensitive capability
  • get_userno sensitive capability
  • get_version_localizationno sensitive capability
  • list_app_categoriesno sensitive capability
  • list_app_info_localizationsno sensitive capability
  • list_app_infosno sensitive capability
  • list_app_price_pointsno sensitive capability
  • list_app_versionsno sensitive capability
  • list_appsno sensitive capability
  • list_beta_groupsno sensitive capability
  • list_beta_testersno sensitive capability
  • list_buildsno sensitive capability
  • list_bundle_idsno sensitive capability
  • list_devicesno sensitive capability
  • list_screenshot_setsno sensitive capability
  • list_screenshotsno sensitive capability
  • list_territoriesno sensitive capability
  • list_usersno sensitive capability
  • list_version_localizationsno sensitive capability
  • remove_beta_testerno sensitive capability
  • set_app_pricesno sensitive capability
  • update_app_info_localizationno sensitive capability
  • update_bundle_idno sensitive capability
  • update_version_localizationno sensitive capability
  • upload_screenshotno sensitive capability

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v1.1.0 latest A 99/100 0 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.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/asc-mcp/badge.svg)](https://mcptrustchecker.com/registry/asc-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/asc-mcp"><img src="https://mcptrustchecker.com/registry/asc-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/asc-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 asc-mcp --online

Use the free API → How scoring works

Other implementations of Asc 3

Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →

More in Developer Tools