mcpbeat Sign in

ShipASO MCP Server

answering

ShipASO is answering right now. Last checked 9 min ago. It exposes 12 tools. Last commit 7 Sep 2026.

Audit any App Store or Google Play listing: measured ranks, keyword gaps, draft copy. Read-only.

Uptime history 13 days of history
13 days agonow
100.0%
Uptime 24h
91 of 91 checks
12
Tools
read from the server
234 ms
Response time
average over 24h
1
Stars
last commit 7 Sep 2026

What the code does

We read the source, 20 h ago · tools taken from the live server · rules 3dff92dd89df

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Claims read-only, but the code runs commands lib/aso_offstore_mine.py:223
        subprocess.run(
Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command lib/aso_offstore_mine.py:223
        subprocess.run(
Sends data to a third-party sink cloud/src/notify/telegramDeliverer.ts:78
  const endpoint = `https://api.telegram.org/bot${botToken}/sendMessage`;
        env = env or dict(os.environ)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch ShipASO and you get told the day something new turns up.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add shipaso --transport http https://api.shipaso.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "shipaso": {
      "url": "https://api.shipaso.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.shipaso]
url = "https://api.shipaso.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "shipaso": {
      "url": "https://api.shipaso.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "shipaso": {
      "url": "https://api.shipaso.com/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

audit
audit_app
Read-only listing audit: prioritized findings (severity + impact) plus a summary, derived from the live public listing. Read-only — never edits or pushes.
audit_play_app
Read-only GOOGLE PLAY listing audit: screenshot grade, the 30/80/4000 title/short/long-description budget, target-term coverage in the long description (Play's keyword surface), a keyword-stuffing guard, prioritized findings + summary, and capability locks for surfaces a public read can't see. Takes a Play package id (com.foo.bar) or a play.google.com URL — NOT a free-text name (Play has no public name search). Play has NO keyword field. Reads public Play data only; never edits or pushes.
audit_play_app_owner
Read-only audit of YOUR OWN Google Play app via the official Play Developer API — full fidelity including the short description (which the public page can't show), with NO capability locks. Requires a configured Play service account (GOOGLE_PLAY_SERVICE_ACCOUNT). Reads only — it opens and DISCARDS a Play 'edit' and NEVER commits, so it can't publish. Owner-only; for a competitor use audit_play_app.
competitor
competitor_watch
Read-only competitor diff: resolves the named competitors and reports their current listings, what changed vs. the last seen state, and a digest line. Read-only metadata comparison; no ranking-algorithm data is invented.
keyword
keyword_gaps
Read-only keyword opportunities: terms tracked competitors VISIBLY use that this app doesn't target and doesn't rank top-50 for, sorted by winnability. Inferred from competitor name/subtitle only — never their ranking algorithm.
localization
localization_gaps
Read-only localization expansion recommendations (ROI-sorted locales to add) for one of YOUR connected apps, from its most recent App Store Connect run. A static, bundled heuristic over the locales already read — no live install data is fabricated. Empty until you've run an ASC-connected pass.
preview
preview_app
Read-only ASO snapshot of any App Store app (grade, lead rank, top-10 count, sample). No account or store push — the optimized copy + push commands stay behind the human-approved loop. Works without a key.
proof
proof
Read-only, anonymized aggregate proof across all tracked apps (real rank-win numbers — no app names, no user data). This is the 'prove the rank moved' surface that closes the prepare → approve → push → prove loop. Works without a key.
propose
propose_copy
Returns a DRAFT optimized listing (name/subtitle/keywords/description) with validation for any app. THIS IS A DRAFT ONLY: it does NOT persist a proposal and does NOT push to the App Store. Publishing stays a human-approved action in ShipASO — an agent can draft and read; only a human approves and pushes.
rank
rank_check
Read-only organic rank check across the app's target keywords, plus winnability-ranked opportunities computed from those measured positions. Positions are live-measured, never fabricated.
screenshot
screenshot_coverage
Read-only screenshot scoring for the app's live store gallery (count, score, grade, levers to improve). Read-only — never uploads or pushes assets.
war
war_room
Read-only head-to-head rank war room for one of YOUR connected apps: your tracked-keyword rank history vs. live competitor positions on those same keywords. Reads stored data + live competitor ranks; writes nothing.

Endpoints

URLTransportStateLatencyChecked
https://api.shipaso.com/mcp streamable-http answering 253 ms 9 min ago

Alternatives to ShipASO

same job, measured the same way
Appfollow
by pipeworx-io

AppFollow MCP — App Store & Google Play reviews, ratings, and ASO keyword

answering
App Store & Google Play
by johnbilousov

Read-only access to App Store Connect and Google Play: apps, releases, and reviews.

51 installs/wk local only
Storelift
by storelift

App Store & Google Play keyword ranks, rivals, reviews, charts and AI visibility as an MCP server

246 installs/wk answering
Getappniche
by getappniche

Live App Store & Google Play data for AI agents: app discovery, ASO keywords, reviews.

28 installs/wk 7 tools answering
Reply Argus
by replyargus

Stop drowning in app reviews: auto-reply on App Store & Google Play, on-brand, 100+ languages.

answering
Shipkit
by readmigo

Unified app publishing MCP Server for Google Play, App Store, and 10+ Chinese stores

32 installs/wk local only
My App Store Ranking
by myappstoreranking

Access to your Apple App Store and Google Play Store rankings, competitors and chart moves.

9 tools answering
Storebridge MCP
by isaiahdupree

Remote MCP connector for App Store + Google Play data via StoreBridge API. No auth required.

13 tools answering

ShipASO — questions

Answers built from our own checks of this server.

What can ShipASO do?
It exposes 12 tools, read directly from the server on our last check. Among them: audit_app, audit_play_app, audit_play_app_owner, competitor_watch, keyword_gaps, localization_gaps and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is ShipASO working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 234 ms. The bar chart above shows every period we have measured.
How do I connect ShipASO?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does ShipASO need an API key?
No. ShipASO completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is ShipASO?
It answers our handshake in 234 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is ShipASO open source?
Yes — it is published under the MIT licence, written in TypeScript, 1 stars on GitHub and 12 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.