Skip to content

Launch Shots MCP server

com.launchshots/launchshotslaunchshots.comstreamable-httpv1.0.0Scanned

Turn your app's screens into editable App Store and Google Play screenshot sets, from your agent.

5 tools: 2 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Launch Shots MCP server can do

The Launch Shots MCP server is published by launchshots.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: prepare_screenshot_upload and generate_screenshot_set), but cannot delete data. 3 tools only read.

1 tool brings in text other people can write (prepare_screenshot_upload).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 2Claude Code: ask
  • generate_screenshot_setDesign a finished App Store / Google Play screenshot set from uploaded screenshots.No findings

    Why it is in this group

    • The name "generate_screenshot_set" says "generate": a word for a change.
    Description, as the server wrote it
    Design a finished App Store / Google Play screenshot set from uploaded screenshots. Step 2 of 3. Returns immediately with a review link while the set is designed in the background (about 1–2 minutes) — then call get_screenshot_set to wait for it. The result is three art directions sharing one set of headlines, each fully editable in the LaunchShots editor. Write app_description from the real source: the README, store listing, or the app's own copy — what it does, who it's for, and what makes it different. Specific beats generic; the headlines are only as sharp as this. Either pass set_id from prepare_screenshot_upload (preferred), or pass the screenshots inline as base64 if you cannot run shell commands (keep each under ~1 MB). Calling again with the same set_id after a failure retries it; nothing is charged for a failed run.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • prepare_screenshot_uploadStart a screenshot set and get one upload URL per screenshot.Reads text others writeNo findings

    Why it is in this group

    • The name "prepare_screenshot_upload" says "screenshot": a word for reading.
    • The description's first verb is "start": a word for a change.

    What it can reach

    • untrusted-inputThe description's first sentence says "start" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Start a screenshot set and get one upload URL per screenshot. Step 1 of 3. Pick the app's key screens — one per core feature, in roughly the order a new user would care about them — captured with realistic content. Avoid empty states, onboarding walls, permission dialogs, debug banners and lorem ipsum: the headlines are written from what is on screen. Upload each file with an HTTP PUT of the raw bytes to its URL (the response includes ready-to-run curl commands). URLs are valid for 2 hours; PUT to the same slot again to replace a file. Then call generate_screenshot_set with the returned set_id.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_accountShow which LaunchShots account this connection uses and how many generations it has left.No findings

    Why it is in this group

    • The name "get_account" says "get": a word for reading.
    Description, as the server wrote it
    Show which LaunchShots account this connection uses and how many generations it has left. Without an API key, explains the free tier and how to connect an account.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_screenshot_setCheck on a screenshot set, waiting up to wait_seconds for it to finish.No findings

    Why it is in this group

    • The name "get_screenshot_set" says "get": a word for reading.
    Description, as the server wrote it
    Check on a screenshot set, waiting up to wait_seconds for it to finish. Step 3 of 3. When it is ready this returns the review link, the headline written for every screen and the three directions. Share the link with the user: they choose a direction and the set opens in the LaunchShots editor (free signup if they are not signed in). If it is still generating, call again — a set usually takes 1–2 minutes.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_projectsList the most recently edited projects in this API key's LaunchShots account, with a link to open each in the editor.No findings

    Why it is in this group

    • The name "list_projects" says "list": a word for reading.
    Description, as the server wrote it
    List the most recently edited projects in this API key's LaunchShots account, with a link to open each in the editor. Requires an API key.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:23 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.launchshots.com/api/mcp: tools/list returned 5 tools to an anonymous client, including prepare_screenshot_upload (write), generate_screenshot_set (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http launchshots https://www.launchshots.com/api/mcp
claude mcp add --transport http launchshots https://www.launchshots.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__launchshots__get_screenshot_set",
      "mcp__launchshots__get_account",
      "mcp__launchshots__list_projects"
    ],
    "ask": [
      "mcp__launchshots__prepare_screenshot_upload",
      "mcp__launchshots__generate_screenshot_set"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as launchshots. Review it before you use it.

Capability tags behind 1 rule
  • mcp__launchshots__prepare_screenshot_upload untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.launchshots/launchshots/verify?hash=b54aee193fb11bdbba01349acfae368aac9ea85e93f37826e4ad3eba9e659b0f" | jq -e '.changed == false'

Pinned hash b54aee193fb1, from Nov 10, 2026, 19:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.launchshots/launchshots/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.launchshots/launchshots
[![Anlyon Radar](https://radar.anlyon.com/badge/com.launchshots/launchshots.svg)](https://radar.anlyon.com/servers/com.launchshots/launchshots)

Source: MCP Registry. Synced Oct 29, 2026, 11:17 UTC.

Launch Shots MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Launch Shots MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Launch Shots MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Launch Shots MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Launch Shots MCP server have?

5 tools: 2 write, 3 read. prepare_screenshot_upload, generate_screenshot_set, get_screenshot_set, get_account and list_projects.

Does the Launch Shots MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Launch Shots MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Launch Shots MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.