Ext Ops Panel
Open dashboard
Comparison

Google Play Store vs net.storelift/storelift

Google Play Store is an MCP server published by kryuchenko. Marketplaces we read that list it: 1 (Official MCP Registry). net.storelift/storelift is an MCP server published by storelift.net. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceGoogle Play Storenet.storelift/storelift
Official MCP Registry Listed
Version: 0.1.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.5.2
Downloads/month (npm): 757
Downloads/week (npm): 243
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.5.2
Downloads/month (npm): 757
Downloads/week (npm): 243
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Google Play Store vs net.storelift/storelift
FactGoogle Play Storenet.storelift/storelift
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last release (differs)2026-11-08 (worse)2026-11-10 (better)
Where it runs (differs)On your machine (https://github.com/kryuchenko/google-play-scraper/releases/download/mcp-v0.1.2/gpscrape-mcp.mcpb)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/kryuchenko/google-play-scrapergithub.com/vom-core/storelift-mcp
Changes in the last 7 days44
First seen (differs)2026-11-072026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 21 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Google Play Store

In its own words, on Official MCP Registry:

Read-only Google Play data: app details, search, charts, reviews, permissions, data safety

net.storelift/storelift

In its own words, on Official MCP Registry:

App Store & Google Play keyword ranks, rivals, reviews and AI visibility. Pro plan and above.

How to run each

Google Play Store

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

net.storelift/storelift As a remote MCP server

Claude Code
claude mcp add --transport http storelift https://storelift.net/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: STORELIFT_API_KEY (secret), Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only net.storelift/storelift has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Google Play Store publish no settings it asks for, so we do not compare settings.

What it can do: Google Play Store · What it can do: net.storelift/storelift · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built