vibe-aso vs App Store + Google Play Data
vibe-aso is a plugin bundle for AI coding tools published by Kronop. Marketplaces we read that list it: 1 (Community GitHub marketplaces). App Store + Google Play Data is an MCP server published by TheValkDokk. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
| Marketplace |  App Store + Google Play Data | |
|---|---|---|
| Community marketplace kronop/vibe-aso | Listed Version: 0.1.0 Forks (GitHub): 48 Stars (GitHub): 476 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Downloads/month (npm): 1 028 Downloads/week (npm): 104 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | vibe-aso | App Store + Google Play Data |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 476 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 48 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-23 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (appstore-mcp-623314400722.us-central1.run.app/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/kronop/vibe-aso | github.com/thevalkdokk/appstore-data-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-26 | 2026-10-23 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 16 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
vibe-aso
You vibe-coded the app — now vibe the ASO. Keyword research, 50-locale App Store metadata, localized screenshots, worldwide pricing, in-app localization, and a verified submission checklist, end to end from Claude Code.
App Store + Google Play Data
Live App Store and Google Play data: app details, reviews, search, top charts for 175+ storefronts.
How to run each
vibe-aso As a Claude Code plugin
/plugin marketplace add kronop/vibe-aso
/plugin install vibe-aso@vibe-aso-marketplaceApp Store + Google Play Data As a remote MCP server
claude mcp add --transport http appstore-data https://appstore-mcp-623314400722.us-central1.run.app/mcp --header "X-RapidAPI-Key: <YOUR_X_RAPIDAPI_KEY>"Requires: RAPIDAPI_KEY (secret), X-RapidAPI-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only App Store + Google Play Data 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 vibe-aso publish no settings it asks for, so we do not compare settings.
What it can do: vibe-aso · What it can do: App Store + Google Play Data · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.