# AppScreen (npm · @appscreen/mcp)

Render App Store and Google Play screenshots from app captures: device frames, sizes, languages.

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- npm · `@appscreen/mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/co-appscreen-mcp/appscreen-mcp.md), [page](https://verifymcp.io/servers/co-appscreen-mcp/appscreen-mcp)

## Channel facts

- Registry: `npm`
- Package: `@appscreen/mcp`
- Version: `0.30.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 94 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 856 tokens (~71/item across 12 items; 2 tools + 10 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 80/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 40% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the AppScreen MCP server?

AppScreen runs locally as an npm package, launched with npx -y @appscreen/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add co-appscreen-mcp -- npx -y @appscreen/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "co-appscreen-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@appscreen/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-appscreen-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@appscreen/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add co-appscreen-mcp -- npx -y @appscreen/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-appscreen-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@appscreen/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-appscreen-mcp --command npx --arg -y --arg @appscreen/mcp
```

### Hermes

```yaml
mcp_servers:
  co-appscreen-mcp:
    command: "npx"
    args: ["-y", "@appscreen/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "co-appscreen-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@appscreen/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-appscreen-mcp -t stdio -c npx -a -y @appscreen/mcp
```

### Other

```json
{
  "mcpServers": {
    "co-appscreen-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@appscreen/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 74, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-10-14 (score 70, +42)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Known CVEs: 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).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Tool coverage: 40
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good

### 2026-10-13 (score 28, −10)

- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: 0.85 → unverified
- [functional] Package version: 0.29.0 → 0.30.0

### 2026-10-12 (score 38, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-11 (score 38)

First indexed and scored.

## MCP tools (2)

### `render_screenshots` (~496 tokens)

Render App Store / Play Store screenshots

Queue a screenshot render; returns jobId, poll get_render_status until done, then fetch the bundle from the resource_link.

BEFORE CALLING THIS: read the appscreen://options resource and present the user the FULL menu of background effects, frames, and presets — each has a preview URL they can open. Let the user pick; never choose a background or frame silently. blur+tint, mesh, and every frame are all valid choices they should see.

IMAGES — put a local file path right on the element; the server reads the bytes off disk and wires up the binding for you. Never base64 real screenshots (a large base64 corrupts token-by-token → renders black):
• screenshot: screens[i].screenshot.path = "~/shot.png" (or pathsByLang: { en, es } for per-locale shots)
• background image: screens[i].bg = { kind:"image", box, path:"~/bg.png" }
• logo/decoration: screens[i].objects[] = { kind:"image", id:"logo", box, mime:"image/png", path:"~/logo.png" }

Geometry is automatic: omit screenshot.box and the server centers the device at the correct aspect ratio. screensMeta is auto-derived when you upload exactly one file per screen. Text overlays use the tiptap doc format and support rich, PARTIAL styling — per-run color, fontSize, fontWeight, fontFamily (~37 fonts), plus bold/italic/underline and per-paragraph align. See appscreen://schema/text + appscreen://catalog/fonts. Free anonymous tier: 5 lifetime renders.

Input parameters:

- `cornerRadius` (string)
- `files` (array): Low-level uploads + manual screensMeta binding. PREFER inline paths instead: put screenshot.path / screenshot.pathsByLang on each screen, bg.path on an image background, and path on image objects — t…
- `idempotencyKey` (string)
- `langs` (array, required): Locales (catalog.langs).
- `layout` (string): One of catalog.layouts (default = `default`).
- `rounded` (boolean)
- `screens` (array, required)
- `screensMeta` (array)
- `sizes` (array, required): Target canvas sizes (catalog.sizes[].id).

### `get_render_status` (~84 tokens)

Poll a render job

Returns status (queued|running|done|failed), progress, and downloadUrl when ready. Only needed when render_screenshots returned a jobId with status=queued (the keyed/async path). Anonymous and small renders often complete inline — if render_screenshots already returned a downloadUrl, you do NOT need to poll.

Input parameters:

- `jobId` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/co-appscreen-mcp/appscreen-mcp#diagnostics

## Score history

- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 70
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 70
- 2026-10-16: 70
- 2026-10-15: 70
- 2026-10-14: 70
- 2026-10-13: 28
- 2026-10-12: 38
- 2026-10-11: 38

## Common questions

### What is the AppScreen MCP server?

AppScreen is an MCP server listed in the public MCP registry as co.appscreen/mcp. Render App Store and Google Play screenshots from app captures: device frames, sizes, languages. This page covers its npm package (@appscreen/mcp).

### Is the AppScreen MCP server safe to use?

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

AppScreen exposes 2 tools: render_screenshots, get_render_status. Their descriptions and schemas cost roughly 580 tokens of context every time the server is loaded.

### Is the AppScreen MCP server still maintained?

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

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

## Links

- npm package: https://www.npmjs.com/package/@appscreen/mcp
- Socket report: https://socket.dev/npm/package/@appscreen/mcp
- Repository: https://github.com/omelas-tech/appscreen-mcp
- Website: https://appscreen.co/mcp
- Changelog RSS feed: https://verifymcp.io/servers/co-appscreen-mcp/appscreen-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-appscreen-mcp/appscreen-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-appscreen-mcp/appscreen-mcp