io.github.Gingiris-1031/analook

Est-ce que io.github.Gingiris-1031/analook est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.Gingiris-1031/analook » 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 8 outils

• analyze_competitor≈ 676 tokens

  Submit a competitor analysis job. Analyzes a competitor's website across 15+ data sources (SEO, traffic, social, Product Hunt, GitHub, Wayback Machine history, AI-generated insights, etc.) and returns a job_id. Use get_report_status(job_id) to poll and get_report(job_id) to retrieve results when status='completed'. Typical analysis takes 2-5 minutes. Requires authentication (deducts 1 credit from your Analook balance). Args: url: Competitor website URL (e.g. 'https://linear.app' or 'lovable.dev') product_name: Optional product name override (defaults to domain) lang: Report language, 'en' (default) or 'zh' for Chinese output Returns: {job_id: str, status: 'started', poll_url: str} on success {error: str, hint?: str} on auth/validation failure

  Paramètres, retour & exemple (6)

  Paramètres

  • url · string · requis
  • lang · ? · optionnel
  • context · string · requis
    Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
  • llm_model · string · requis
    The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
  • product_name · ? · optionnel
  • conversation_id · string · optionnel
    Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

  Exemple d'appel

  {"name": "analyze_competitor", "arguments": {"url": "texte", "context": "texte", "llm_model": "texte"}}

  Exemple de retour

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

• browse_public_reports≈ 539 tokens

  Browse Analook's public competitor-intelligence report gallery. Returns recently published public reports (product name, domain, category, and a link). No authentication or credits required — a fast way to discover existing analyses before spending a credit on a fresh one. Args: category: Optional filter, e.g. 'AI / Agents', 'Dev Tools', 'Crypto / Web3', 'Marketing / SEO', 'SaaS / Other'

  Paramètres, retour & exemple (4)

  Paramètres

  • context · string · requis
    Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
  • category · ? · optionnel
  • llm_model · string · requis
    The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
  • conversation_id · string · optionnel
    Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

  Exemple d'appel

  {"name": "browse_public_reports", "arguments": {"context": "texte", "llm_model": "texte"}}

  Exemple de retour

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

• get_growth_audit≈ 498 tokens

  Fetch a Growth Audit's three reports (Executive Summary, Diagnosis, Action Plan) as Markdown. Args: job_id: ID from run_growth_audit() (starts with 'ga-') Returns: {status, reports: {executive_summary, diagnosis_report, action_plan}} while running, only {status, progress} is returned.

  Paramètres, retour & exemple (4)

  Paramètres

  • job_id · string · requis
  • context · string · requis
    Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
  • llm_model · string · requis
    The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
  • conversation_id · string · optionnel
    Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

  Exemple d'appel

  {"name": "get_growth_audit", "arguments": {"job_id": "texte", "context": "texte", "llm_model": "texte"}}

  Exemple de retour

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

• get_report≈ 538 tokens

  Fetch the full competitor analysis report as structured JSON. Reports contain: website snapshot, Wayback Machine history, SEO/traffic data (DataForSEO), social media presence, Product Hunt launches, GitHub stats, pricing, funding, AI-generated business insights, growth playbooks, and more. Args: job_id: ID from analyze_competitor(); status must be 'completed' Returns: The full report dict (nested structure), or {error} if not found / not ready.

  Paramètres, retour & exemple (4)

  Paramètres

  • job_id · string · requis
  • context · string · requis
    Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
  • llm_model · string · requis
    The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
  • conversation_id · string · optionnel
    Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

  Exemple d'appel

  {"name": "get_report", "arguments": {"job_id": "texte", "context": "texte", "llm_model": "texte"}}

  Exemple de retour

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

• get_report_markdown≈ 499 tokens

  Fetch the competitor analysis report as human-readable Markdown. Suitable for piping into agents that prefer text over structured JSON, or for direct display to end users. Args: job_id: ID from analyze_competitor(); status must be 'completed' Returns: {markdown: str} or {error: str}

  Paramètres, retour & exemple (4)

  Paramètres

  • job_id · string · requis
  • context · string · requis
    Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
  • llm_model · string · requis
    The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
  • conversation_id · string · optionnel
    Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

  Exemple d'appel

  {"name": "get_report_markdown", "arguments": {"job_id": "texte", "context": "texte", "llm_model": "texte"}}

  Exemple de retour

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

• get_report_status≈ 466 tokens

  Poll an analysis job's status. Args: job_id: ID returned from analyze_competitor() Returns: {status: 'running'|'completed'|'failed', progress?: str, report_url?: str}

  Paramètres, retour & exemple (4)

  Paramètres

  • job_id · string · requis
  • context · string · requis
    Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
  • llm_model · string · requis
    The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
  • conversation_id · string · optionnel
    Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

  Exemple d'appel

  {"name": "get_report_status", "arguments": {"job_id": "texte", "context": "texte", "llm_model": "texte"}}

  Exemple de retour

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

• list_my_reports≈ 481 tokens

  List your recent competitor analysis reports (up to 50). Requires authentication. Returns a lightweight list (id, url, product_name, created_at, status) — use get_report(job_id) to fetch the full report for any of them. Returns: {reports: [{id, url, product_name, created_at, status}, ...]}

  Paramètres, retour & exemple (3)

  Paramètres

  • context · string · requis
    Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
  • llm_model · string · requis
    The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
  • conversation_id · string · optionnel
    Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

  Exemple d'appel

  {"name": "list_my_reports", "arguments": {"context": "texte", "llm_model": "texte"}}

  Exemple de retour

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

• run_growth_audit≈ 640 tokens

  Run a full Growth Audit — three linked strategic reports for a product. Unlike analyze_competitor (a single 15-signal intelligence snapshot), a Growth Audit produces an Executive Summary + a Diagnosis Report + a 30-day Action Plan, grounded in real channel/tactic playbooks. Best for 'how do I grow THIS product' rather than 'what is this competitor doing'. Takes ~4-6 minutes. Requires authentication and deducts 10 credits. Poll with get_growth_audit(job_id) until status='completed'. Args: url: Product website URL to audit product_name: Optional product name override (defaults to domain) lang: Report language, 'en' (default) or 'zh'

  Paramètres, retour & exemple (6)

  Paramètres

  • url · string · requis
  • lang · ? · optionnel
  • context · string · requis
    Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
  • llm_model · string · requis
    The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
  • product_name · ? · optionnel
  • conversation_id · string · optionnel
    Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

  Exemple d'appel

  {"name": "run_growth_audit", "arguments": {"url": "texte", "context": "texte", "llm_model": "texte"}}

  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://www.analook.com/mcp/