Is App Store Connect MCP safe to use?

App Store Connect MCP has an HVTrust score of 54.7/100 (Grade C), ranked #417 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for App Store Connect MCP?

App Store Connect MCP scores 54.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 46 GitHub stars and is categorized under MCP Servers.

App Store Connect MCP

erayendes/app-store-connect-mcp

Heimdall — MCP server for the Apple App Store Connect API and App Store Server API (StoreKit 2). 875 tools across 13 pro

MCP Servers TypeScript Grade C Listed MIT

54.7/100

Rank #417 of 1283

Compare App Store Connect MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-11 · 1d ago

Recent change

Rank +1

Is App Store Connect MCP safe? App Store Connect MCP scores 54.7/100 (Grade C), ranked #417 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7/10; 10% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#135 Figma Ui MCP — 55.3 (C) → #136 MCP Server Kalshi — 55.1 (C) → #138 OpenResearch MCP — 54.6 (C) → #139 Apple Books — 54.5 (C) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 16 spots (#401 → #417)

2026-08-08

Newly Listed

First tracked at rank #399

Maintainer Checklist

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for App Store Connect MCP View MCP Servers Report missing data

62.2

Activity sub-score · out of 100

#137

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

Forks

Last Push

2026-08-11

yesterday

Commits (4 wk)

186

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #417

Analysis

HVTrust Dimensions vs MCP Servers

54.7 / 100 · 67.0% confidence

App Store Connect MCP MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

16.8 / 25

11.8 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

14.4 / 17

5.6 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.5 above avg 12.4

AdoptionLog-scaled stars · package downloads

4.0 / 20

1.8 below avg 5.8

Activity Inputs

62.2 / 100

StarsRepository reach

10.0 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

2.2 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

7.0 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

10%

of last 100 commits verified

Dependency-Update-Tool 10

Maintained 0

Code-Review 0

Dangerous-Workflow 10

Security-Policy 10

Binary-Artifacts 10

Token-Permissions 10

Pinned-Dependencies 10

License 10

CII-Best-Practices 0

Vulnerabilities 10

Packaging 10

Signed-Releases -1

Branch-Protection 3

SAST 10

Fuzzing 0

Contributors 3

CI-Tests 10

Is App Store Connect MCP safe?

Public trust evidence for App Store Connect MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does App Store Connect MCP publish package provenance?

Yes. App Store Connect MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does App Store Connect MCP have an OpenSSF Scorecard?

App Store Connect MCP has an OpenSSF Scorecard score of 7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is App Store Connect MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does App Store Connect MCP use?

App Store Connect MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are App Store Connect MCP's commits signed?

10% of the last 100 commits to App Store Connect MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

App Store Connect MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain App Store Connect MCP?

For maintainers

HVTrust scores App Store Connect MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-10

Rank Moved

Rank dropped 16 spots (#401 → #417)

2026-08-08

Newly Listed

First tracked at rank #399

GitHub → npm: @erayendes/asc-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/app-store-connect-mcp.svg)](https://hvtracker.net/agents/app-store-connect-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/app-store-connect-mcp"><img src="https://hvtracker.net/badge/app-store-connect-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON