Framegrove: App Store screenshot generator
NPM · FRAMEGROVE
Render App Store, Google Play and iPhone Duo screenshots and Apple Creative Assets from templates.
Available components
Last scanned (1 hour ago)
Scores higher than 38% of npm servers
Category Design and Media
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
- 31 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1076 tokens (~215/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% 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
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.
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.
- 14 Oct 26 +29
- 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 Tool coverage: 97 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- 12 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 38
First indexed and scored.
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 18 Oct 2026 · Analysed npm/framegrove@1.0.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 105 packages
| Packages resolved | 105 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
build_project Build editable project ~407
Write a project file (.sms.json) that can be imported into the Framegrove web app (Projects → Import project) for visual fine-tuning in the browser. Use when the user wants to edit in the editor instead of final PNGs.
| Name | Type | Req | Description |
|---|---|---|---|
| accent | string | – | Brand accent hex (#16a34a). Omit to keep the template colour. |
| addIcon | boolean | – | Draw icon + app name on screen 1. |
| captions | object | – | Captions per language: {"en":[…],"tr":[…]}. Same order and count for every language. Overrides `lines` for that language. |
| frame | string | – | Device frame override: iphone-pro | iphone-notch | duo-inner | duo-outer | duo-inner-landscape | android | tablet | none. |
| icon | string | – | App icon file path (square PNG). |
| lang | string | – | Default caption language code (en, tr, de, …). |
| lines | array | – | Captions in the default language, one per screen: "Headline [highlight] | Subtitle". Headline ≤30 chars, subtitle ≤55; wrap ONE benefit word in [brackets]; \n for a line break. |
| name | string | yes | App name. Optional icon on screenshot templates; Creative Assets preserve their dedicated layout. |
| out | string | – | Output .json path. |
| rating | string | – | Rating badge text for screen 1, e.g. "4.8 · 1.2K ratings". Only if real. |
| shots | – | – | Screenshot file paths in screen order — an array (used for every device) or per family: {"global":[…],"iphone":[…],"ipad":[…],"android-phone":[…],"iphone-duo-inner":[…],"iphone-duo-outer":[…]}. |
| template | string | yes | Template key from list_templates (e.g. studio-paper, studio-midnight, creative-paper-header, creative-lime-search). |
No output schema declared.
No examples provided.
inspect_assets Inspect exported images ~80
Read exported image dimensions and PNG alpha channels, optionally validating them against an output id from list_outputs. Does not change files.
| Name | Type | Req | Description |
|---|---|---|---|
| orientation | string | – | – |
| output | string | – | Output id to validate against, e.g. iphone-6.9. |
| paths | array | yes | Image file paths, absolute or relative to the server working directory. |
No output schema declared.
No examples provided.
list_outputs List output sizes ~34
List exact output dimensions for App Store, Google Play, iPhone Duo and Creative Assets, with screenshot family slots and format constraints.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_templates List templates ~50
List the curated screenshot and Creative Assets templates (key, name, description, tags, theme light/dark/colourful, orientation, default output sizes, screen count). Pick by app category and desired theme.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
render_screenshots Render screenshots ~505
Render a complete App Store / Google Play / iPhone Duo screenshot or Creative Assets set as PNG files from a template, captions and screenshot files. Output is organised as language / size / screen. Sizes are output ids from devices (iphone-6.9, iphone-6.5, ipad-13, android-phone, android-tablet-10, watch, macos …) or "WxH". Use absolute paths; relative paths resolve against the server working directory. Fonts are downloaded once on first render.
| Name | Type | Req | Description |
|---|---|---|---|
| accent | string | – | Brand accent hex (#16a34a). Omit to keep the template colour. |
| addIcon | boolean | – | Draw icon + app name on screen 1. |
| captions | object | – | Captions per language: {"en":[…],"tr":[…]}. Same order and count for every language. Overrides `lines` for that language. |
| exportLanguages | array | – | Languages to export (default: all languages present in captions). |
| frame | string | – | Device frame override: iphone-pro | iphone-notch | duo-inner | duo-outer | duo-inner-landscape | android | tablet | none. |
| icon | string | – | App icon file path (square PNG). |
| lang | string | – | Default caption language code (en, tr, de, …). |
| lines | array | – | Captions in the default language, one per screen: "Headline [highlight] | Subtitle". Headline ≤30 chars, subtitle ≤55; wrap ONE benefit word in [brackets]; \n for a line break. |
| name | string | yes | App name. Optional icon on screenshot templates; Creative Assets preserve their dedicated layout. |
| outDir | string | – | Output directory. |
| rating | string | – | Rating badge text for screen 1, e.g. "4.8 · 1.2K ratings". Only if real. |
| shots | – | – | Screenshot file paths in screen order — an array (used for every device) or per family: {"global":[…],"iphone":[…],"ipad":[…],"android-phone":[…],"iphone-duo-inner":[…],"iphone-duo-outer":[…]}. |
| sizes | array | – | Output ids or "WxH". Each size gets its own subfolder when more than one. |
| template | string | yes | Template key from list_templates (e.g. studio-paper, studio-midnight, creative-paper-header, creative-lime-search). |
No output schema declared.
No examples provided.
How do I install the Framegrove: App Store screenshot generator MCP server?
Framegrove: App Store screenshot generator runs locally as an npm package, launched with npx -y framegrove. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · framegrove
claude mcp add tech-bam-framegrove -- npx -y framegrove
What is the Framegrove: App Store screenshot generator MCP server?
Framegrove: App Store screenshot generator is an MCP server listed in the public MCP registry as io.github.tech-bam/framegrove. Render App Store, Google Play and iPhone Duo screenshots and Apple Creative Assets from templates. This page covers its npm package (framegrove).
Is the Framegrove: App Store screenshot generator MCP server safe to use?
Framegrove: App Store screenshot generator scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 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 Framegrove: App Store screenshot generator MCP server expose?
Framegrove: App Store screenshot generator exposes 5 tools: list_templates, list_outputs, inspect_assets, render_screenshots, build_project. Their descriptions and schemas cost roughly 1,076 tokens of context every time the server is loaded.
Is the Framegrove: App Store screenshot generator MCP server still maintained?
Framegrove: App Store screenshot generator is still listed as active in the MCP registry. We last reached this channel on 18 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 Framegrove: App Store screenshot generator MCP server under?
Framegrove: App Store screenshot generator declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.