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.

StoreReady MCP

NPM · STOREREADY-MCP

StoreReady: Whether AI app builders produce apps that pass App Store review.

Available components

npm · storeready-mcp 65
+42 this week 65 Trust /100

Last scanned (10 hours ago)

Scores higher than 37% of npm servers

Deprecated

This server is marked deprecated in the MCP registry. The registry records this reason: StoreReady is archived and its backend is no longer served.

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
  • 39 of 120 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 11 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 228 tokens (~228/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.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 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.

  • 16 Oct 26 −5
    • Source repository: pass → fail ▼ security
    • Security disclosure: fail → unverified ▼ functional
  • 14 Oct 26 +32
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
  • 11 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 7 Oct 26 23

    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 17 Oct 2026 · Analysed npm/storeready-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 120 packages
Packages resolved 120
Stale 39
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~228 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
compare_app_builders ~228

Read StoreReady, a sourced comparison of the AI mobile-app builders (Rork, Vibecode, a0.dev, Replit, Bolt and the rest) on one question: can the app it hands you go up on your own Apple Developer account and survive review. Returns what each builder outputs, whether you can export the source, who submits the binary, the App Store guidelines in play, and a verdict of ships / ships-with-caveats / blocked / unknown. Use when asked which AI app builder to pick, or whether one can actually ship to the App Store — the answer changes as builders launch and change, and every verdict here is attached to a source that was read on a stated date.

NameTypeReqDescription
builderstring–One builder slug or name for the full record with its evidence, e.g. "rork", "vibecode", "bolt".
limitnumber–How many to return, 1-10. Default 10.
verdictstring–Filter the list: ships, ships-with-caveats, blocked, unknown.

No output schema declared.

No examples provided.

Install

How do I install the StoreReady MCP server?

StoreReady MCP runs locally as an npm package, launched with npx -y storeready-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 · storeready-mcp

# add to Claude Code
claude mcp add tech-thecompound-storeready -- npx -y storeready-mcp
Common questions

What is the StoreReady MCP server?

StoreReady MCP is listed in the public MCP registry as tech.thecompound/storeready. StoreReady: Whether AI app builders produce apps that pass App Store review. This page covers its npm package (storeready-mcp).

Is the StoreReady MCP server safe to use?

StoreReady MCP scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. 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 StoreReady MCP server expose?

StoreReady MCP exposes 1 tool: compare_app_builders. Their descriptions and schemas cost roughly 228 tokens of context every time the server is loaded.

Is the StoreReady MCP server still maintained?

StoreReady MCP is marked deprecated in the MCP registry. We last reached this channel on 17 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 StoreReady MCP server under?

StoreReady 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.