ASOScan

io.github.ASOScanPublished by GitHub account ASOScanv1.0.0Updated Nov 15, 2026

App Store Optimization for your own iOS and Android apps. Needs an ASOScan account (OAuth sign-in).

The publisher's own server: scan.mx Email Diagnostics

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

ASOScan is a remote MCP server for App Store Optimization of your own iOS and Android apps, accessed with an ASOScan account via OAuth.

What you can do
  • App Store Optimization for your own iOS and Android apps, per the registry description.
  • No tool list, instructions or README is supplied, so the specific actions the assistant can take are not documented here.
  • Access is tied to an ASOScan account signed in through OAuth.
When to use it
Consider it if you manage your own iOS or Android app listings and want an assistant to work on App Store Optimization tasks through ASOScan. Because no tools are documented, verify what it can actually do before relying on it.
Requirements
A remote streamable HTTP endpoint at asoscan.com; no local package or runtime is needed. An ASOScan account with OAuth sign-in is required. No environment variables or headers are declared.
Before you install
OAuth sign-in grants the server access to your ASOScan account, so review the scopes requested during authorization. The tool set is undocumented, so it is unclear whether it can change app listing data; confirm before granting access.

Installation

In SourceWeft

  1. Open ASOScan 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/io.github.ASOScan%2Fasoscan/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": {
    "asoscan": {
      "type": "http",
      "url": "https://asoscan.com/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 15, 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.

Other Scan integrations