# ShipASO (remote · api.shipaso.com)

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

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.shipaso.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/airowe-shipaso/api.md), [page](https://verifymcp.io/servers/airowe-shipaso/api)

## Channel facts

- Endpoint: `https://api.shipaso.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1394 tokens (~116/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ShipASO MCP server?

ShipASO is a hosted endpoint at https://api.shipaso.com/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.

### Claude

```bash
claude mcp add --transport http airowe-shipaso 'https://api.shipaso.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "airowe-shipaso": {
      "url": "https://api.shipaso.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "airowe-shipaso": {
      "type": "http",
      "url": "https://api.shipaso.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.airowe-shipaso]
url = "https://api.shipaso.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "airowe-shipaso": {
      "type": "remote",
      "url": "https://api.shipaso.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add airowe-shipaso --url 'https://api.shipaso.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  airowe-shipaso:
    url: "https://api.shipaso.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "airowe-shipaso": {
      "Transport": "http",
      "Url": "https://api.shipaso.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add airowe-shipaso -t streamable-http -u 'https://api.shipaso.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "airowe-shipaso": {
      "type": "http",
      "url": "https://api.shipaso.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 68, +1)

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

### 2026-09-18 (score 67, +1)

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

### 2026-09-16 (score 66, +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.

### 2026-09-14 (score 65, +1)

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

### 2026-09-12 (score 64, +1)

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

### 2026-09-10 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 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.

### 2026-09-07 (score 62, +1)

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

### 2026-09-06 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (12)

### `preview_app` (~105 tokens)

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.

Input parameters:

- `bundleId` (string): Exact bundle id (skips resolution)
- `country` (string): ISO country storefront, e.g. US
- `query` (string): App name, App Store URL, numeric id, or bundle id

### `audit_app` (~89 tokens)

Read-only listing audit: prioritized findings (severity + impact) plus a summary, derived from the live public listing. Read-only — never edits or pushes.

Input parameters:

- `bundleId` (string): Exact bundle id (skips resolution)
- `country` (string): ISO country storefront, e.g. US
- `query` (string): App name, App Store URL, numeric id, or bundle id

### `audit_play_app` (~209 tokens)

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.

Input parameters:

- `brand` (string): App brand name, so brand-burn in the short description is flagged
- `country` (string): ISO country storefront, e.g. US
- `packageName` (string): Exact Play package id (skips resolution)
- `query` (string): Google Play package id (com.foo.bar) or a play.google.com app URL
- `targets` (array): Target search terms to measure long-description coverage for

### `audit_play_app_owner` (~167 tokens)

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.

Input parameters:

- `brand` (string): App brand name, so short-description brand-burn is flagged
- `language` (string): BCP-47 listing language, e.g. en-US
- `packageName` (string, required): Your app's Play package id, e.g. com.foo.bar
- `targets` (array): Target search terms to measure long-description coverage for

### `keyword_gaps` (~104 tokens)

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.

Input parameters:

- `bundleId` (string): Exact bundle id (skips resolution)
- `country` (string): ISO country storefront, e.g. US
- `query` (string): App name, App Store URL, numeric id, or bundle id

### `rank_check` (~91 tokens)

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.

Input parameters:

- `bundleId` (string): Exact bundle id (skips resolution)
- `country` (string): ISO country storefront, e.g. US
- `query` (string): App name, App Store URL, numeric id, or bundle id

### `screenshot_coverage` (~91 tokens)

Read-only screenshot scoring for the app's live store gallery (count, score, grade, levers to improve). Read-only — never uploads or pushes assets.

Input parameters:

- `bundleId` (string): Exact bundle id (skips resolution)
- `country` (string): ISO country storefront, e.g. US
- `query` (string): App name, App Store URL, numeric id, or bundle id

### `competitor_watch` (~118 tokens)

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.

Input parameters:

- `bundleId` (string): Exact bundle id (skips resolution)
- `competitors` (array, required): Competitor app names or bundle ids to compare against
- `country` (string): ISO country storefront, e.g. US
- `query` (string): App name, App Store URL, numeric id, or bundle id

### `war_room` (~81 tokens)

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.

Input parameters:

- `appId` (string, required): Id of a connected app you own
- `competitors` (array): Competitor names to compare (max 4)

### `localization_gaps` (~80 tokens)

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.

Input parameters:

- `appId` (string, required): Id of a connected app you own

### `proof` (~59 tokens)

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_copy` (~126 tokens)

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.

Input parameters:

- `bundleId` (string): Exact bundle id (skips resolution)
- `country` (string): ISO country storefront, e.g. US
- `query` (string): App name, App Store URL, numeric id, or bundle id

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/airowe-shipaso/api#diagnostics

## Score history

- 2026-09-20: 68
- 2026-09-19: 67
- 2026-09-18: 67
- 2026-09-17: 66
- 2026-09-16: 66
- 2026-09-15: 65
- 2026-09-14: 65
- 2026-09-13: 64
- 2026-09-12: 64
- 2026-09-11: 63
- 2026-09-10: 63
- 2026-09-09: 62
- 2026-09-08: 62
- 2026-09-07: 62
- 2026-09-06: 61
- 2026-09-05: 61

## Common questions

### What is the ShipASO MCP server?

ShipASO is an MCP server listed in the public MCP registry as io.github.airowe/shipaso. Audit any App Store or Google Play listing: measured ranks, keyword gaps, draft copy. Read-only. This page covers its hosted endpoint (https://api.shipaso.com/mcp).

### Is the ShipASO MCP server safe to use?

ShipASO scores 68 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 ShipASO MCP server expose?

ShipASO exposes 12 tools: preview_app, audit_app, audit_play_app, audit_play_app_owner, keyword_gaps, and 7 more. Their descriptions and schemas cost roughly 1,320 tokens of context every time the server is loaded.

### Does the ShipASO MCP server require authentication?

No. We connected to ShipASO without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ShipASO MCP server still maintained?

ShipASO is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.shipaso.com/mcp
- Repository: https://github.com/airowe/store-ops
- Website: https://shipaso.com/
- Changelog RSS feed: https://verifymcp.io/servers/airowe-shipaso/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/airowe-shipaso/api.json
- HTML version of this page: https://verifymcp.io/servers/airowe-shipaso/api