Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.devinwang/google-play-developer-mcp

NPM · GOOGLE-PLAY-DEVELOPER-MCP

MCP server for Google Play: full Android Publisher API v3 and Play Developer Reporting API.

74 Trust /100

Last scanned (12 hours ago)

Scores higher than 44% of npm servers

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 42 of 117 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to devinwang/google-play-developer-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 10902 tokens (~69/item across 157 items; 157 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 44% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 21 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "accounts_remove" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 157 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 21 Oct 26 59

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 23 Oct 2026 · Analysed npm/google-play-developer-mcp@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo devinwang/google-play-developer-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/devinwang/google-play-developer-mcp/.github/workflows/release.yml@refs/tags/v0.2.0
Rekor log index 3346481120
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:0245e53db9d354f36bdb544e343b8690d49b385f85efcfbc89ea2177a8202295d913ed80a0812d3acc4002425ca25879399b1a18bb2cd2b5a2013cfe4

Background: How many MCP packages publish verified provenance →

Dependencies 117 packages
Packages resolved 117
Deprecated 1
Stale 41
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 157 exposed · ~10,902 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
tracks_list ~75

List every track visible in this edit (includes default internal/alpha/beta/production + any custom closed-testing tracks).

NameTypeReqDescription
editIdstringyesEdit id returned by `edits_insert` — required for all edits.* writes
packageNamestringyesAndroid application package name, e.g. com.example.app

No output schema declared.

No examples provided.

tracks_patch ~89

Partial update of track state.

NameTypeReqDescription
editIdstringyesEdit id returned by `edits_insert` — required for all edits.* writes
packageNamestringyesAndroid application package name, e.g. com.example.app
releasesarrayyes–
trackstringyesTrack name: internal, alpha, beta, production — or a custom closed-testing track id

No output schema declared.

No examples provided.

tracks_update ~142

Full replacement of track state. `releases` is an array of release objects — versionCodes, status (draft|inProgress|halted|completed), userFraction (0-1 for staged rollout), inAppUpdatePriority (0-5), countryTargeting, and releaseNotes.

NameTypeReqDescription
editIdstringyesEdit id returned by `edits_insert` — required for all edits.* writes
packageNamestringyesAndroid application package name, e.g. com.example.app
releasesarrayyes–
trackstringyesTrack name: internal, alpha, beta, production — or a custom closed-testing track id

No output schema declared.

No examples provided.

users_create ~45

Add a new team member to the developer account. Pass the user resource with email + roles + optional expirationTime.

NameTypeReqDescription
parentstringyes–
userobjectyes–

No output schema declared.

No examples provided.

users_delete ~35

Remove a user from the developer account.

NameTypeReqDescription
namestringyesFull user resource name: developers/{dev}/users/{user}

No output schema declared.

No examples provided.

users_list ~65

List all users on a developer account. `parent` is the developer account id in the form `developers/{developerId}` (find it in the Play Console URL).

NameTypeReqDescription
pageSizenumber––
pageTokenstring––
parentstringyes–

No output schema declared.

No examples provided.

users_update ~53

Patch-update a team member (roles, access level).

NameTypeReqDescription
namestringyesFull user resource name: developers/{dev}/users/{user}
updateMaskstring––
userobjectyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.devinwang/google-play-developer-mcp server?

io.github.devinwang/google-play-developer-mcp runs locally as an npm package, launched with npx -y google-play-developer-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · google-play-developer-mcp

# add to Claude Code
claude mcp add devinwang-google-play-developer-mcp -- npx -y google-play-developer-mcp
Common questions

What is the io.github.devinwang/google-play-developer-mcp server?

io.github.devinwang/google-play-developer-mcp is listed in the public MCP registry as io.github.devinwang/google-play-developer-mcp. MCP server for Google Play: full Android Publisher API v3 and Play Developer Reporting API. This page covers its npm package (google-play-developer-mcp).

Is the io.github.devinwang/google-play-developer-mcp server safe to use?

io.github.devinwang/google-play-developer-mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.devinwang/google-play-developer-mcp server expose?

io.github.devinwang/google-play-developer-mcp exposes 157 tools: accounts_list, accounts_current, accounts_add, accounts_remove, accounts_switch, and 152 more. Their descriptions and schemas cost roughly 10,902 tokens of context every time the server is loaded.

Is the io.github.devinwang/google-play-developer-mcp server still maintained?

io.github.devinwang/google-play-developer-mcp is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.devinwang/google-play-developer-mcp server under?

io.github.devinwang/google-play-developer-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.