ClearedToShip

dev.clearedtoshipPublished by clearedtoship.devOfficial publisherv1.0.0Updated Nov 14, 2026

Scan iOS and Android project files for common App Store and Play review issues over MCP.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP server that scans iOS and Android project files for common App Store and Play review issues.

What you can do
  • Scan iOS and Android project files for common App Store and Play review problems
  • Report findings from the scan so an assistant can review them before submission
When to use it
Useful when preparing a mobile app release and you want an assistant to check project files for issues that commonly trigger App Store or Play review rejections.
Requirements
Remote endpoint at clearedtoship.dev over streamable HTTP. Authentication is required: an Authorization header with a bearer API key from the provider's account page, or MCP OAuth discovery via the 401 WWW-Authenticate header.
Before you install
Requires an API key sent in the Authorization header; keep it secret and check what project files are uploaded to the remote service. The manifest lists no tools, so confirm the exact capabilities before relying on it.

Installation

In SourceWeft

  1. Open ClearedToShip in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.clearedtoship%2Fshipcheck/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "clearedtoship": {
      "type": "http",
      "url": "https://clearedtoship.dev/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 14, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.