My App Store Ranking MCP server

• Registry namecom.myappstoreranking/myappstorerankingverified in the MCP registry

The registry name sits under myappstoreranking.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-19
• Tools9
• Server calls itselfmyappstoreranking
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 140 ms.

• Its tools do every use case we checked: compare app rankings across iPhone, iPad, Mac and Android; spot rivals who repeatedly rank above your app.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer333 ms
• Space in an agent's context≈ 1,630 tokensthe definitions of all its tools (9), which an agent carries on every turn
• Tool definitionsB · 87 of 100
• Typed results9 of 9 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 7 of 9

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_my_apps

  Returns every tracked app with its store id, store, platforms, categories and whether it is one of the user's own apps or a competitor they watch. Call this first: every other tool identifies an app by the appStoreId returned here…

• get_apps_overview

  One row per tracked app: how many countries it charted in, how many top 5 and top 25 placements it holds, the change against the equal-length window before, and its single best chart position. Use this for 'how is my portfolio doing'…

• get_app_country_ranks

  The country grid for a single app over a date window, with the previous window's rank for comparison, plus the per-platform breakdown. Works for any app in the catalog, not only tracked ones, but untracked apps return a single recent day…

• get_app_history

  Raw rank observations, newest first, for trend questions. Filter by country, platform, chart type or category, because an unfiltered portfolio-wide history is large and will be truncated. Only apps the user tracks have history. Example…

• get_chart_top

  Who ranks in a given country, platform, chart type and category on a given day, flagging the rows the user tracks. Defaults to the most recent captured day. Use list_reference_data for valid country codes, platforms and category ids…

• get_rivals

  Competitors discovered from the data rather than declared: apps that appear in the same charts as the user's own apps and sit ahead of them, ranked by relevance, with how often and by how much they lead. Example question: "Who is beating…

• get_leaders

  Which apps dominated a chart over a date window: median rank, best rank, days present, days at number one, movement against the previous window, and whether the app is new to the chart. This is the tool for 'who moved into the top 10 this…

• get_daily_report

  The same analysis the user's email report is built from: portfolio summary, what needs attention, wins, competitor movements and new entrants. The best single call for a scheduled 'what happened overnight' digest. Example question: "What…

• list_reference_data

  The enum values every other tool accepts. Call this before guessing a country code or category id: invalid parameters fail, and failed calls still count against the daily quota.