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.sonlenef/storepilot-mcp

PYPI · STOREPILOT

Run an app portfolio across Google Play and the App Store: vitals, reviews, earnings, releases.

Available components

+15 this week 97 Trust /100

Last scanned (7 hours ago)

Scores higher than 99% of PyPI servers

Category Marketing and SEO

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 55 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to sonlenef/storepilot-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 80 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 148 tokens (~148/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 5 Nov 26 +17
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: partial → pass ▲ security
    • Dependency health: partial → 1.00 functional
  • 4 Nov 26 −17
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → partial ▼ security
    • Dependency health: 1.00 → partial functional
  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.97 functional
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: unverified → pass ▲ functional
  • 30 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: pass → unverified ▼ functional
  • 28 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
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 5 Nov 2026 · Analysed pypi/storepilot@0.1.1

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo sonlenef/storepilot-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/sonlenef/storepilot-mcp/.github/workflows/release.yml@refs/tags/v0.1.1
Rekor log index 2496515420
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:ae7f6aaefa5f70a58c7a8fa50be44d1047dfefa7b3f87e851bd54ce2c9e84077

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 55 packages
Packages resolved 55
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~148 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
setup_doctor ~148

Diagnose StorePilot's store credentials and report exactly what is missing. Runs every setup step independently and reports all of them, so a single failure never hides the rest. For Google Play it verifies: the service account key parses (and shows the email you must grant access to), the Android Publisher API is reachable, the Play Developer Reporting API is reachable and lists your apps, the "Reply to reviews" permission is present (the API returns an empty list rather than an error when it is missing), and the Cloud Storage reports bucket is configured and readable. Each failing step comes with the exact fix. Run this first whenever a Play tool returns empty or unexpected data.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the io.github.sonlenef/storepilot-mcp server?

io.github.sonlenef/storepilot-mcp runs locally as a PyPI package, launched with uvx storepilot. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · storepilot

# add to Claude Code
claude mcp add sonlenef-storepilot-mcp -- uvx storepilot
Common questions

What is the io.github.sonlenef/storepilot-mcp server?

io.github.sonlenef/storepilot-mcp is listed in the public MCP registry as io.github.sonlenef/storepilot-mcp. Run an app portfolio across Google Play and the App Store: vitals, reviews, earnings, releases. This page covers its PyPI package (storepilot).

Is the io.github.sonlenef/storepilot-mcp server safe to use?

io.github.sonlenef/storepilot-mcp scores 97 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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.sonlenef/storepilot-mcp server expose?

io.github.sonlenef/storepilot-mcp exposes 1 tool: setup_doctor. Their descriptions and schemas cost roughly 148 tokens of context every time the server is loaded.

Is the io.github.sonlenef/storepilot-mcp server still maintained?

io.github.sonlenef/storepilot-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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.sonlenef/storepilot-mcp server under?

io.github.sonlenef/storepilot-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.

What did VerifyMCP test on the io.github.sonlenef/storepilot-mcp server?

VerifyMCP ran 16 checks on io.github.sonlenef/storepilot-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.