appstore-play-mcp

MCPattested
v0.1.2io.github.JohnBilousovUnknownUpdated 1mo agonpmGitHub

Read-only access to App Store Connect and Google Play: apps, releases, and reviews.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
1mo agoLast update
Reads these credentials
  • ASC_KEY_PATHAPI keyoptional

    Path to the AuthKey_<KEY_ID>.p8 private key downloaded from App Store Connect.

  • PLAY_SERVICE_ACCOUNT_PATHAPI keyoptional

    Path to the Google service account JSON with Android Publisher access.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.JohnBilousov
LicenseUnknown
Version0.1.2
Sourcenpm+mcp-registry
npmappstore-play-mcp
GitHubJohnBilousov/appstore-play-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 3f6fa1e
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface5 tools · none privileged
Security scan✓ Cleanv0.1.3 · 29d agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

5 tools · none privileged
Statically extracted from the published packagev0.1.3 · 29d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

stores_healthReport which stores are configured and whether their credentials work. Call this first when something returns nothing.

Report which stores are configured and whether their credentials work. Call this first when something returns nothing.

No input schema was published for this tool.

list_appsEvery app reachable with the configured credentials, from both stores. The App Store side is discovered automatically; the Play side comes from PLAY_PACKAGES, because the Play API cannot enumerate a developer's apps.

Every app reachable with the configured credentials, from both stores. The App Store side is discovered automatically; the Play side comes from PLAY_PACKAGES, because the Play API cannot enumerate a developer's apps.

No input schema was published for this tool.

get_appDetails for a single app, found by App Store id, Play package name, or bundle id.

Details for a single app, found by App Store id, Play package name, or bundle id.

No input schema was published for this tool.

get_releasesWhat is live, what is in review, and what is mid-rollout — for one app or the whole portfolio. States are normalised across stores: 'live', 'in_review', 'pending_developer_release', 'rejected', 'draft', 'rolling_out', 'halted'. The store's own wording is kept in rawState. Reading Play tracks opens…

What is live, what is in review, and what is mid-rollout — for one app or the whole portfolio. States are normalised across stores: 'live', 'in_review', 'pending_developer_release', 'rejected', 'draft', 'rolling_out', 'halted'. The store's own wording is kept in rawState. Reading Play tracks opens…

No input schema was published for this tool.

get_reviewsNo description published

This tool published no description. Forge does not invent one.

4 of 5 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Read-only access to App Store Connect and Google Play: apps, releases, and reviews.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

5 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-13 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.