ShipASO
REMOTE · API.SHIPASO.COM
Audit any App Store or Google Play listing: measured ranks, keyword gaps, draft copy. Read-only.
Available components
Last scanned (2 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Oct 26 0
- Stability: 0.97 → pass security
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 5 Sept 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.shipaso.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shipaso.com | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e5724550004f161d0e3e318966157c8b |
| SANs: shipaso.com, api.shipaso.com, *.api.shipaso.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.shipaso.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| shipaso.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.shipaso.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.shipaso.com/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_app ~89
Read-only listing audit: prioritized findings (severity + impact) plus a summary, derived from the live public listing. Read-only — never edits or pushes.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
audit_play_app ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
audit_play_app_owner ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | App brand name, so short-description brand-burn is flagged |
| language | string | – | BCP-47 listing language, e.g. en-US |
| packageName | string | yes | Your app's Play package id, e.g. com.foo.bar |
| targets | array | – | Target search terms to measure long-description coverage for |
No output schema declared.
No examples provided.
competitor_watch ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleId | string | – | Exact bundle id (skips resolution) |
| competitors | array | yes | 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 |
No output schema declared.
No examples provided.
keyword_gaps ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
localization_gaps ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | Id of a connected app you own |
No output schema declared.
No examples provided.
preview_app ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
proof ~59
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
propose_copy ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
rank_check ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
screenshot_coverage ~91
Read-only screenshot scoring for the app's live store gallery (count, score, grade, levers to improve). Read-only — never uploads or pushes assets.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
war_room ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | Id of a connected app you own |
| competitors | array | – | Competitor names to compare (max 4) |
No output schema declared.
No examples provided.
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.
remote · api.shipaso.com
claude mcp add --transport http airowe-shipaso 'https://api.shipaso.com/mcp'
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 81 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.