com.appscreens/appscreens
AppScreens: App Store and Google Play Screenshots
Is the AppScreens MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.
Editable App Store and Google Play screenshots: design, localize, preview, export and upload.
needs auth probed 2026-11-15 · unchanged since 2026-11-13 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"type":"https://appscreens.com/problems/api","title":"Authentication required","status":401,"code":"AUTHENTIC- Endpoint
- https://api.appscreens.com/mcp (streamable-http)
- Host
- api.appscreens.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.appscreens.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server api.appscreens.com, PKCE S256, grants authorization_code, refresh_token.
Scopes account:read apps:read apps:write assets:read assets:write catalog:read credentials:manage designs:read designs:write deployments:create exports:create mcp:connect operations:read projects:read projects:write renders:create schedules:write store-metadata:read store-metadata:write store-releases:write.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/AppScreens/app-store-screenshots-skill
- Website
- https://appscreens.com/developers/connect
- Registry
- active, updated 2026-11-13 · registry entry
Compare this server with others.
More servers
Servers that mention appscreens.
- AppScreenshots io.github.horace68/appscreenshots · needs auth
- com.appscreenshotstudio/mcp · alive
- AppScreenStudio com.appscreenstudio/app-screen-studio · alive
- AppScreenshoot MCP io.github.rico-c/appscreenshoot · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.