Marketing

shipaso.com

Provides app store optimization (ASO) tools to audit and analyze Apple App Store and Google Play listings, including keyword gap analysis and listing audits.

1 endpoint12 known toolsFirst detected September 6, 2026Last detected September 6, 2026

ENDPOINT 1

https://api.shipaso.com/mcp

No auth detected

MCP server metadata

Name: shipaso
Version: 0.1.0

Capabilities

tools.listChanged

Server instructions

ShipASO exposes read-only ASO data and the proof surfaces as tools. Tools audit, check ranks, find keyword gaps, and draft optimized copy — but NEVER publish. Pushing a change to the App Store is a human-approved step inside ShipASO; no tool here writes to the store. `propose_copy` returns a draft only.

Known tools 12

preview_app

Read-only ASO snapshot of any App Store app (grade, lead rank, top-10 count, sample).

Inferred read-only

audit_app

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

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

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 read-only

rank_check

Read-only organic rank check across the app's target keywords, plus winnability-ranked opportunities computed from those measured positions.

Inferred read-only

screenshot_coverage

Read-only screenshot scoring for the app's live store gallery (count, score, grade, levers to improve).

Inferred read-only

competitor_watch

Read-only competitor diff: resolves the named competitors and reports their current listings, what changed vs.

Inferred read-only

war_room

Read-only head-to-head rank war room for one of YOUR connected apps: your tracked-keyword rank history vs.

Inferred read-only

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.

Inferred read-only

proof

Read-only, anonymized aggregate proof across all tracked apps (real rank-win numbers — no app names, no user data).

Inferred read-only

propose_copy

Returns a DRAFT optimized listing (name/subtitle/keywords/description) with validation for any app.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.shipaso]
url = "https://api.shipaso.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: shipaso
Remote MCP URL: https://api.shipaso.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "shipaso": {
      "url": "https://api.shipaso.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "shipaso",
  "transport": "streamable-http",
  "url": "https://api.shipaso.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.