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.

Agent C — App Store Screenshots

REMOTE · API.THEAGENTC.IO

AI-designed App Store screenshot sets from your app's screens, uploaded to App Store Connect.

Available components

+3 this week 77 Trust /100

Last scanned (19 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1366 tokens (~136/item across 10 items; 10 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 63% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 16 Oct 26 +1

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

  • 13 Oct 26 +1

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

  • 11 Oct 26 +1

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

  • 10 Oct 26 +1

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

  • 7 Oct 26 0
    • Schema quality: pass → fail ▼ functional
    • Stability: unverified → 0.07 ▲ functional
  • 5 Oct 26 73

    First indexed and scored.

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 17 Oct 2026 · Probed https://api.theagentc.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=theagentc.io CN=YE2,O=Let's Encrypt,C=US 20 Sept 2026 19 Dec 2026 ECDSA 256 ECDSA-SHA384 6082f81c46d63fed0a10c5e61a9a920cec7
SANs: *.theagentc.io, theagentc.io
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.theagentc.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
theagentc.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="agent-c"

Bearer realm="agent-c"

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.theagentc.io/mcp Verified 200
http (plaintext) http://api.theagentc.io/mcp HTTPS enforced 301 https://api.theagentc.io/mcp
MCP tools · 10 exposed · ~1,024 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
add_app ~96

Add an app by its App Store link (imports name, icon, description), or by name if it isn't released yet. Importing a live app takes ~10-30s; poll list_apps until status is 'ready'.

NameTypeReqDescription
app_store_urlstring–e.g. https://apps.apple.com/us/app/…/id123456789
namestring–Only for apps not on the App Store yet

No output schema declared.

No examples provided.

design_set ~168

Claude art-directs a full App Store screenshot set from the uploaded screenshots: opening shot, headline per slide, close-ups, palette. Returns watermarked preview images, the slide list and a link to open it in the Agent C studio. Takes ~40-60 seconds.

NameTypeReqDescription
app_idstringyesapp_id from list_apps / add_app
devicestring––
focusstring–Optional: what to emphasize (feature, audience, angle).
includestring–What to make: the screenshot set, screenshots + the App Store product page header (iOS 27), or only the header
openerstring–Opening slide: hand holding the phone, big app icon, lifestyle photo, or a plain phone. auto lets Claude pick.

No output schema declared.

No examples provided.

edit_set ~253

Change one slide (headline, subline, screenshot, layout, position, or remove it), the opening shot, the device size, or the App Store header (header_*). Re-renders previews. Free.

NameTypeReqDescription
devicestring––
header_headlinestring–App Store header headline (*stars* color words). No prices, URLs, platform names or #1 claims.
header_layoutstring–Header visual: lifestyle photo, three phones, big icon, or a hand holding the phone
header_sublinestring––
headlinestring–Wrap words in *stars* to color them
includestring–What to make: the screenshot set, screenshots + the App Store product page header (iOS 27), or only the header
layoutstring––
move_tointeger––
openerstring––
removeboolean––
screenshotinteger–1-based screenshot to show on this slide
set_idstringyesset_id returned by design_set
slideinteger–1-based slide number to change
sublinestring––

No output schema declared.

No examples provided.

export_set ~73

Render the unlocked set at exact App Store pixels without watermark and return download links (valid 7 days). Includes the product page header (3840x1646) and search-results image (3840x2560) when the set has a header.

NameTypeReqDescription
set_idstringyesset_id returned by design_set

No output schema declared.

No examples provided.

get_set ~35

Current slides, unlock status and fresh preview images for a set.

NameTypeReqDescription
set_idstringyesset_id returned by design_set

No output schema declared.

No examples provided.

get_upload_link ~105

Best way to upload screenshots from files on disk: returns a one-time URL (valid 30 min) to POST the image files to with curl (multipart field 'files', up to 10 per request). Use this instead of upload_screenshots when you have a shell, so large images don't pass through the conversation.

NameTypeReqDescription
app_idstringyesapp_id from list_apps / add_app
replaceboolean–First upload clears the app's old screenshots

No output schema declared.

No examples provided.

list_apps ~23

The user's apps in Agent C, with how many screenshots each has uploaded.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

send_to_app_store ~101

Upload the unlocked set into the app's editable version in App Store Connect, replacing that language's screenshots for this device size. Never submits for review. Requires the user to have connected App Store Connect in Agent C. If the app has no editable version, ask the user, then call with create_version=true.

NameTypeReqDescription
create_versionboolean––
localestring––
set_idstringyesset_id returned by design_set

No output schema declared.

No examples provided.

unlock_set ~71

Unlock clean, full-resolution files for a set. Uses a free unlock if the user has one; otherwise returns a $9.99 Stripe checkout link the USER must open and pay. Studio subscribers are already unlocked. Ask the user before calling.

NameTypeReqDescription
set_idstringyesset_id returned by design_set

No output schema declared.

No examples provided.

upload_screenshots ~99

Upload 1-10 raw screenshots of the app (plain captures of the real UI, ideally 4-10, in the order you'd like them considered). Each item is base64 image data (PNG/JPEG) or a public https URL. By default replaces the app's screenshot library.

NameTypeReqDescription
app_idstringyesapp_id from list_apps / add_app
imagesarrayyes–
replaceboolean––

No output schema declared.

No examples provided.

Install

How do I install the Agent C — App Store Screenshots MCP server?

Agent C — App Store Screenshots is a hosted endpoint at https://api.theagentc.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.theagentc.io

# add to Claude Code
claude mcp add --transport http io-theagentc-app-store-screenshots 'https://api.theagentc.io/mcp'
Common questions

What is the Agent C — App Store Screenshots MCP server?

Agent C — App Store Screenshots is an MCP server listed in the public MCP registry as io.theagentc/app-store-screenshots. AI-designed App Store screenshot sets from your app's screens, uploaded to App Store Connect. This page covers its hosted endpoint (https://api.theagentc.io/mcp).

Is the Agent C — App Store Screenshots MCP server safe to use?

Agent C — App Store Screenshots scores 77 out of 100 on VerifyMCP. 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 Agent C — App Store Screenshots MCP server expose?

Agent C — App Store Screenshots exposes 10 tools: list_apps, add_app, get_upload_link, upload_screenshots, design_set, and 5 more. Their descriptions and schemas cost roughly 1,024 tokens of context every time the server is loaded.

Does the Agent C — App Store Screenshots MCP server require authentication?

Yes. Agent C — App Store Screenshots asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Agent C — App Store Screenshots MCP server still maintained?

Agent C — App Store Screenshots is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.