ai.deployit/product-expert

Est-ce que ai.deployit/product-expert est sûr ?

Au dernier audit MCP Hub, le serveur MCP « ai.deployit/product-expert » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. 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.

Les 3 outils

• ask_product_expert≈ 677 tokens

  Ask a question about "deployit" and get an answer verified against its live source code and git history. Use it for anything about product behavior, features, settings, limits, error messages, or recent changes. HOW IT WORKS AND HOW LONG IT TAKES: the expert genuinely investigates — it searches and reads the product's real source code before answering. A fresh investigation takes 20-60 SECONDS. Do not give up early, and if a human is waiting, tell them the verified answer may take up to a minute. Repeated questions asked without `context` are served from cache in under a second; the cache resets whenever the product's code changes. IF IT TIMES OUT: you get an error saying the expert could not finish in time. The investigation KEEPS RUNNING in the background — re-ask the IDENTICAL question (same wording, no `context`) about a minute later and the finished answer is served instantly from cache. Retry with the same words; rephrasing restarts the investigation. READING THE ANSWER: it ends with a Sources block (the files and commits actually consulted) and a Verification status carrying both confidence and polarity: - verified: confirmed in the code — safe to relay. - backend_only: the capability exists server-side but has no visible UI path. - not_found: searched, and it does NOT exist — a factual "no", relayable as such. - unknown: the expert could not conclude — do NOT relay as fact; consider retrying with depth "thorough". LIMITS: strictly read-only — it can never change anything. Some topics may be refused by the project's policy. A monthly question quota may apply (the error message says so when reached; cached answers never count). At most 60 requests per minute per access key.

  Paramètres, retour & exemple (3)

  Paramètres

  • depth · string · optionnel · quick | thorough
    quick (default): up to ~1 minute of investigation, right for support questions. thorough: digs much deeper for hard questions — expect the timeout-then-retry-from-cache flow.
  • context · string · optionnel
    Optional context from your own conversation with the end user (symptoms, plan, what they tried…). Makes the answer more targeted, but context-carrying questions are never cached — omit it for generic questions.
  • question · string · requis
    The question about the product, as specific as possible. Identical wording hits the cache — when retrying after a timeout, repeat the question verbatim.

  Exemple d'appel

  {"name": "ask_product_expert", "arguments": {"question": "texte"}}

  Exemple de retour

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

• get_recent_changes≈ 171 tokens

  Instant list of recent changes to "deployit" — the semantic changelog derived from its commits. No AI processing: responds in under a second, costs nothing, and never counts against any quota. Use this FIRST for "what changed", "what's new", "since when" questions; escalate to ask_product_expert only when you need an investigated answer.

  Paramètres, retour & exemple (1)

  Paramètres

  • days · number · optionnel
    How many days back (default 14, max 90).

  Exemple d'appel

  {"name": "get_recent_changes", "arguments": {"days": 1}}

  Exemple de retour

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

• server_info≈ 122 tokens

  Describe this MCP server: which product it answers for, which repositories back it, and how fresh the underlying code index is. Instant (no AI). Call it once at the start of a session to confirm you are talking to the right product — if the index is stale or still building, say so instead of trusting deep answers.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "server_info", "arguments": {}}

  Exemple de retour

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

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

https://mcp.deployit.ai/demo