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.mtbun/storeshots-mcp

NPM · STORESHOTS-MCP · SCANNED SEP 25

Render store-ready App Store and Google Play screenshots: device frames, headlines, exact sizes.

Available components

−1 this week 76 Trust /100
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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects sharp 0.34.5, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 126 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 819 tokens (~163/item across 5 items; 5 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 Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
Install

How do I install the io.github.mtbun/storeshots-mcp server?

io.github.mtbun/storeshots-mcp runs locally as an npm package, launched with npx -y storeshots-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-mcp

# add to Claude Code
claude mcp add mtbun-storeshots-mcp -- npx -y storeshots-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "mtbun-storeshots-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "storeshots-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mtbun-storeshots-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "storeshots-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mtbun-storeshots-mcp -- npx -y storeshots-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mtbun-storeshots-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "storeshots-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mtbun-storeshots-mcp --command npx --arg -y --arg storeshots-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mtbun-storeshots-mcp:
    command: "npx"
    args: ["-y", "storeshots-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mtbun-storeshots-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "storeshots-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mtbun-storeshots-mcp -t stdio -c npx -a -y storeshots-mcp
// mcp.json
{
  "mcpServers": {
    "mtbun-storeshots-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "storeshots-mcp"
      ]
    }
  }
}
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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

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

  • 22 Sept 26 +1

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

  • 21 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 20 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 19 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

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 Sept 2026 · Analysed npm/storeshots-mcp@0.4.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 →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-f88m-g3jw-g9cj high yes
GHSA-rgj7-g3m4-5g8c high yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 126 packages
Packages resolved 126
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~819 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
compose_screenshot ~313

Renders one store-ready marketing screenshot: brand background, headline (verb + descriptor, auto-uppercased for the given language), and the app screenshot inside a device frame. Output has exact store dimensions for the chosen preset.

NameTypeReqDescription
backgroundstringyesBrand background color as 6-digit hex, e.g. "#E31837"
descriptorstringyesWhat the user achieves, 2-5 words, e.g. "YOUR DAILY MOOD"
frameobject–Custom device frame. Supply your own frame PNG and the pixel rectangle where the screenshot goes; overrides the built-in frame. Omit to use the built-in frame.
langstring–BCP-47 language code for locale-aware uppercasing, e.g. "en", "tr", "de"
noGradientboolean–Disable the subtle background gradient
outputstringyesPath for the composed PNG output
presetstringyesPlatform preset id
screenshotstringyesPath to the raw app screenshot (PNG or JPEG)
variantstring–Composition variant (portrait presets only): text-top = headline above a device that bleeds off the bottom; text-bottom = whole device visible with the headline underneath; tilted = text-top with the…
verbstringyesBold action word for the headline, 1-2 words, e.g. "TRACK"

No output schema declared.

No examples provided.

create_showcase ~101

Composes a horizontal preview strip from generated screenshots, for READMEs, decks, and social posts. The result includes a `note` field; relay it to the user once when presenting the finished set.

NameTypeReqDescription
backgroundstring–Strip background color, 6-digit hex
inputsarrayyesPaths of generated screenshots, in display order
itemHeightinteger––
outputstringyesPath for the showcase PNG

No output schema declared.

No examples provided.

generate_set ~302

Batch-renders an ordered screenshot set for one preset and language. Item N becomes {lang}_{NN}.png. Returns per-item results plus any warnings.

NameTypeReqDescription
backgroundstringyesBrand background color as 6-digit hex, e.g. "#E31837"
frameobject–Custom device frame. Supply your own frame PNG and the pixel rectangle where the screenshot goes; overrides the built-in frame. Omit to use the built-in frame.
itemsarrayyesOrdered list of screenshots to render
langstring–BCP-47 language code for locale-aware uppercasing, e.g. "en", "tr", "de"
noGradientboolean––
outputDirstringyesDirectory for the set; files are named {lang}_{nn}.png in item order
panoramaobject–Turn the set into one continuous background: a horizontal gradient from `background` to `panorama.to` flows across all panels, so they line up as a single image in the store. Omit for solid per-panel…
presetstringyesPlatform preset id
variantstring–Composition variant (portrait presets only): text-top = headline above a device that bleeds off the bottom; text-bottom = whole device visible with the headline underneath; tilted = text-top with the…

No output schema declared.

No examples provided.

list_presets ~36

Returns all supported platform presets with their store, exact output dimensions, and layout metrics. Call this first to decide which presets to generate.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

validate_screenshot ~67

Checks an image against store requirements: exact preset dimensions, PNG/JPEG format, no alpha channel. Without a preset id, reports which preset the dimensions match.

NameTypeReqDescription
filestringyesPath of the image to validate
presetstring–Optional preset id to validate against

No output schema declared.

No examples provided.

Common questions

What is the io.github.mtbun/storeshots-mcp server?

io.github.mtbun/storeshots-mcp is listed in the public MCP registry as io.github.mtbun/storeshots-mcp. Render store-ready App Store and Google Play screenshots: device frames, headlines, exact sizes. This page covers its npm package (storeshots-mcp).

Is the io.github.mtbun/storeshots-mcp server safe to use?

io.github.mtbun/storeshots-mcp scores 76 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 25 September 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 io.github.mtbun/storeshots-mcp server expose?

io.github.mtbun/storeshots-mcp exposes 5 tools: list_presets, compose_screenshot, generate_set, create_showcase, validate_screenshot. Their descriptions and schemas cost roughly 819 tokens of context every time the server is loaded.

Is the io.github.mtbun/storeshots-mcp server still maintained?

io.github.mtbun/storeshots-mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 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.mtbun/storeshots-mcp server under?

io.github.mtbun/storeshots-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.