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.

StoreShots

NPM · STORESHOTS-API-MCP

Turn raw app screenshots into App Store and Google Play marketing screenshots.

Available components

+3 this week 81 Trust /100

Last scanned (6 hours ago)

Scores higher than 74% of npm servers

Category Design and Media

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
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1056 tokens (~176/item across 6 items; 6 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 Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
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.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 18 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +6
    • Stability: unverified → 0.43 ▲ functional
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 25 Oct 2026 · Analysed npm/storeshots-api-mcp@0.1.2

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 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,056 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
buy_credits ~137

Return a Stripe Payment Link for a credit pack, personalised for this API key (client reference + prefilled email). Nothing is charged by this tool: give the link to the user to pay in their browser; credits are added automatically after payment, so confirm with get_balance afterwards. Use when generate_screenshots fails for lack of credits or the user wants unwatermarked output. If it returns an error (e.g. an unknown pack id), get valid pack ids from get_balance.

NameTypeReqDescription
packstringyesPack id from get_balance (starter = 10 sets for $3, pro = 20 sets for $5).

No output schema declared.

No examples provided.

generate_screenshots ~465

Turn 1–5 raw app screenshots (local file paths or http(s) URLs) into framed App Store / Google Play marketing screenshots with headlines. One call = one set (all requested sizes) = 1 credit; free keys get 3 watermarked sets per month. Returns a jobId plus per-target file list; set download_to (or call get_output later) to save the PNGs/ZIP locally — outputs are kept on the server for 24h. Call list_styles/list_devices first for valid ids. If free sets and credits are used up it returns an error: call get_balance, then buy_credits.

NameTypeReqDescription
appNamestring–App name, used in output file names.
captionsarray–Smaller caption under each headline (≤220 chars), same order as screenshots. Missing entries blank; extras ignored.
devicestring–Device frame. Omit to use each target's default device.
download_formatstring–What to download when download_to is set: zip = one ZIP of all sizes, png = individual PNGs in per-target subfolders, both = both (default zip).
download_tostring–If set, download the results into this local directory right away (same as calling get_output). Existing files with the same names are overwritten.
headlinesarray–Headline per slide (≤140 chars), same order as screenshots. Missing entries are left blank; entries beyond the number of screenshots are ignored.
screenshotsarrayyes1–5 local image paths (absolute, ~ or relative to cwd), file:// or http(s) URLs. PNG/JPEG/WebP, ≤10 MB each. One slide per screenshot.
stylestring–Style id (default glow). See list_styles.
targetsarray–Output sizes (default ios-6.9, ios-6.5, android-phone).
themeobject–Optional overrides on top of the style: gradFrom/gradTo (gradient), bgColor + bgMode (solid or gradient background), headlineColor, captionColor, frameColor (hex like #4f46e5), textAlign, screenFit (…

No output schema declared.

No examples provided.

get_balance ~69

Show remaining paid credits, free generations left this month, and the available credit packs (ids and prices). Call before generate_screenshots to check you have quota, and before buy_credits to get a valid pack id. Takes no parameters; read-only live data that requires STORESHOTS_API_KEY.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_output ~200

Download a finished job's ZIP and/or individual PNGs to a local directory (default ~/StoreShots/<jobId>, or STORESHOTS_OUTPUT_DIR/<jobId>). Use after generate_screenshots when download_to was not set, or to download again in another format/folder; existing files with the same names are overwritten. Returns the saved file paths and sizes. Jobs expire after 24h; an unknown or expired job_id returns an error (generate again).

NameTypeReqDescription
formatstring–zip = one ZIP of all sizes, png = individual PNGs in per-target subfolders, both = both. Default zip.
job_idstringyesThe jobId returned by generate_screenshots, e.g. 20260929-a1b2c3d4e5.
output_dirstring–Local directory to save into (absolute, ~ or relative; created if missing). Default ~/StoreShots/<jobId>.

No output schema declared.

No examples provided.

list_devices ~107

List device frames (iphone, iphone-duo, android, ipad) and store output targets with pixel sizes (ios-6.9 1320x2868, ios-6.5 1242x2688, android-phone, ipad-13). Call this before generate_screenshots to pick valid device and targets values; use list_styles instead for colours/layouts. Takes no parameters; read-only, fetched live from the StoreShots API and requires STORESHOTS_API_KEY.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_styles ~78

List the curated visual styles (background colours, text colours and layout) with the ids accepted by generate_screenshots.style. Call this before generate_screenshots to choose a look; use list_devices instead for device frames and output sizes. Takes no parameters; read-only, fetched live from the StoreShots API and requires STORESHOTS_API_KEY.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the StoreShots MCP server?

StoreShots runs locally as an npm package, launched with npx -y storeshots-api-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 · storeshots-api-mcp

# add to Claude Code
claude mcp add uk-co-qaimos-storeshots-storeshots -- npx -y storeshots-api-mcp
Common questions

What is the StoreShots MCP server?

StoreShots is an MCP server listed in the public MCP registry as uk.co.qaimos.storeshots/storeshots. Turn raw app screenshots into App Store and Google Play marketing screenshots. This page covers its npm package (storeshots-api-mcp).

Is the StoreShots MCP server safe to use?

StoreShots scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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 StoreShots MCP server expose?

StoreShots exposes 6 tools: list_styles, list_devices, generate_screenshots, get_output, get_balance, buy_credits. Their descriptions and schemas cost roughly 1,056 tokens of context every time the server is loaded.

Is the StoreShots MCP server still maintained?

StoreShots is still listed as active in the MCP registry. We last reached this channel on 25 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 StoreShots MCP server under?

StoreShots declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.