io.github.meyusufdemirci/app-store-operator

Est-ce que io.github.meyusufdemirci/app-store-operator est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.meyusufdemirci/app-store-operator » est classé « Vérifié ». Aucun comportement malveillant détecté au test comportemental. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Versions auditées & empreintes

Vérifiez la version que vous utilisez : son empreinte doit correspondre à celle listée ici — sinon vous n'utilisez pas la version auditée.

Vous utilisez ce serveur ? Suivez-le (créez un compte) pour être alerté dès qu'une nouvelle version paraît ou que le verdict change.

Les 4 outils

• research_rivals≈ 300 tokens

  Search the App Store for a keyword and fetch SensorTower analytics for the top results — all in one call. Results are cached for 24 hours so repeat queries are instant. Use this for a quick competitive overview when you want everything in one step. Use `search_app_store` + `get_app_details` separately when you need more than 3 results, a custom limit, or selective fetching of specific apps. Do not use this for Google Play or Android apps — it covers the iOS App Store only. Requires a SensorTower account. On a cache miss the server opens a real Chromium window on the user's machine; the first run needs the user to log in there, and the session is reused from then on. If there is no session the call returns an error result carrying `{"error": "not_logged_in"}` and leaves the window open —

  Paramètres, retour & exemple (2)

  Paramètres

  • country · string · requis
    Two-letter App Store country code (e.g. us, gb, tr)
  • keyword · string · requis
    The keyword to search in the App Store (e.g. psikoloji, meditation)

  Exemple d'appel

  {"name": "research_rivals", "arguments": {"country": "texte", "keyword": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_app_store≈ 342 tokens

  Search the App Store for a keyword and return ranked results as a detailed table — instantly, no browser required. Use this when you want to discover which apps rank for a keyword before deciding which ones to analyse in depth. - Follow up with `get_app_details` to fetch SensorTower analytics for specific app IDs. - Use `research_rivals` instead for a single convenience call that searches and fetches analytics together. - Do not use this for Google Play or Android apps — it covers the iOS App Store only. Unlike `research_rivals` and `get_app_details`, this needs no SensorTower account, opens no browser window, and returns in about a second. It also carries no downloads or revenue figures — those only come from the SensorTower tools. Returns markdown (not JSON): one table per result, ran

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Number of results to return (1–25, default 3). Values above 25 are clamped to 25.
  • country · string · requis
    Two-letter App Store country code (e.g. us, gb, tr)
  • keyword · string · requis
    The keyword to search in the App Store (e.g. meditation, psikoloji)

  Exemple d'appel

  {"name": "search_app_store", "arguments": {"country": "texte", "keyword": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_app_details≈ 337 tokens

  Fetch SensorTower analytics for one or more App Store app IDs. Returns downloads, revenue, ratings, publisher info, markets, and more for each app. Use this when you already have app IDs (e.g. from `search_app_store`) and want detailed analytics for only a subset of them — avoiding unnecessary scrapes for apps you don't need. Use `research_rivals` instead for a single convenience call that searches and fetches analytics together. Do not use this for Google Play or Android apps — it takes numeric iOS App Store IDs only. Requires a SensorTower account. The server opens a real Chromium window on the user's machine; the first run needs the user to log in there, and the session is reused from then on. If there is no session the call returns an error result carrying `{"error": "not_logged_in"}

  Paramètres, retour & exemple (2)

  Paramètres

  • app_ids · array · requis
    List of numeric App Store app IDs, as strings (e.g. ["123456", "789012"]). Each is the digits from an apps.apple.com URL's `id` segment, without the `id` prefix.
  • country · string · requis
    Two-letter App Store country code (e.g. us, gb, tr)

  Exemple d'appel

  {"name": "get_app_details", "arguments": {"app_ids": [], "country": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• prepare_iae≈ 577 tokens

  Prepare an iOS App Store In-App Event (IAE) — generate copy variations and a final report. Use this when the user wants to create or draft an in-app event, prepare IAE metadata, or generate App Store event copy. Accepts user-supplied keywords and event parameters, then returns a structured brief. Do not use it for ordinary App Store listing metadata (title, subtitle, description) — it covers In-App Event fields only. Runs entirely locally: no network calls, no App Store or SensorTower lookup, and no keyword research of its own — the caller supplies the keywords (reach for `research_rivals` or `search_app_store` first if you still need to find them). Returns immediately. **After receiving the tool output, you MUST:** 1. Generate **3 distinct copy variations** in the target language (from

  Paramètres, retour & exemple (7)

  Paramètres

  • goal · string · requis
    Primary conversion goal (e.g. increase conversions, attract new users, boost engagement).
  • tone · string · requis · Engaging | Playful | Motivational | Authoritative | Calm | Urgent
    Copy tone.
  • locale · string · requis · en-us | en-gb | de | de-de | fr | fr-fr | es | es-es
    Target locale/language for the IAE copy (e.g. en-us, en-gb, de-de, fr-fr, tr, ja, ko, zh-hans). An unlisted value returns an `unknown_locale` error naming the supported ones.
  • audience · string · requis
    Target audience (e.g. students, professionals, parents, casual users).
  • keywords · array · requis
    Ordered list of keywords by priority (index 0–2 = Tier 1 must-use, 3–6 = Tier 2, 7–9 = Tier 3). Maximum 10.
  • event_context · string · requis
    Real-world hook tying the event to a moment (e.g. a holiday, season, product milestone).
  • event_purpose · string · requis
    1–2 sentences describing what the event is about and why users should care.

  Exemple d'appel

  {"name": "prepare_iae", "arguments": {"goal": "texte", "tone": "Engaging", "locale": "en-us", "audience": "texte", "keywords": [], "event_context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

Badge pour votre README

Ce serveur a passé le pentest comportemental. Le badge porte son nom et renvoie à cette fiche — la preuve, c'est la fiche (verdict live qu'on contrôle), pas l'image.

[![Vérifié par MCP Hub](https://dokore.fr/badge/io.github.meyusufdemirci--app-store-operator.svg)](https://dokore.fr/serveur/io.github.meyusufdemirci--app-store-operator)

<a href="https://dokore.fr/serveur/io.github.meyusufdemirci--app-store-operator"><img src="https://dokore.fr/badge/io.github.meyusufdemirci--app-store-operator.svg" alt="Vérifié par MCP Hub" height="20"></a>

Réévalué en continu : si le comportement change, le verdict tombe et le badge disparaît. Un badge qui ne pointe pas vers une fiche dokore.fr ne prouve rien. Comment ça marche

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

app-store-operator@0.3.5