ASOLens

dev.danielhan.asolensPublished by asolens.danielhan.devv0.4.1Updated Oct 25, 2026

ASOLens MCP server: App Store ranks, competitors and weaknesses, from your own machine

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

ASOLens is a local MCP server that lets an assistant look up App Store ranks, competitors and weaknesses, optionally including your own listing.

What you can do
Look up App Store rankings, competitors and weaknesses for apps, as described for the ASOLens MCP server. Optionally read your own App Store listing through App Store Connect API credentials. Optionally retrieve keyword search volume through DataForSEO, US storefront only. No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when you want an assistant to research App Store rankings and competing apps, or to review your own listing alongside competitor data, from your local machine.
Requirements
Runs as a local stdio process installed from the npm package @asolens/mcp, so Node.js is needed. Optional App Store Connect access uses ASC_API_ISSUER_ID, ASC_API_KEY_ID and a .p8 key at ~/.appstoreconnect/private_keys/AuthKey_ .p8 or the path in ASC_API_PRIVATE_KEY_PATH. Optional keyword volume uses the paid DataForSEO service with DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD. Desktop only.
Before you install
The DataForSEO integration is optional and paid, so enabling it can incur charges. It requires DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD, and the password is a secret. App Store Connect access requires an API private key file on disk; keep it protected. Data is sent to DataForSEO and Apple when those integrations are enabled.

Installation

In SourceWeft

  1. Open ASOLens in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.1LatestOct 13, 2026

Score

15% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.