Servidor MCP de Aidenix

• Nome no registrocom.aidenix/aidenixverificado no registro MCP

O nome no registro fica sob aidenix.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-11-03
• Ferramentas18
• O servidor se chamaAidenix Insight MCP Server
• Versão do servidor1.28.1
• Versão do protocolo2025-06-18

Em 2026-11-03 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 625 ms.

• As ferramentas fazem todos os casos de uso verificados: Score a company list by fit before sending; Check that contacts still work at their company.
• Verificado em 2 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 2 até agora
• O que um agente consegue fazer com ele2 de 2 casos de uso
• Respondeumedindo2 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta645 ms
• Espaço no contexto do agente≈ 5.405 tokensas definições de todas as ferramentas (18), que o agente carrega a cada turno
• Definições das ferramentasA · 94 de 100
• Resultados tipados2 de 18 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 6 de 18

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• get_account_context

  Return the authenticated Aidenix account plan, quota, and selected ICP, using the profile website as its human-readable label.

• list_icp_profiles

  List ICP profiles by website and product description, including which website is selected.

• analyze_contact

  Return a complete user-facing single-contact business-fit analysis and outreach drafts. When presenting a completed result, hide technical metadata and use human-readable headings while preserving every user-facing content field.

• get_analysis

  Poll one business-fit analysis job and return the complete user-facing result when finished; hide technical metadata and use human-readable headings while preserving every user-facing content field.

• analyze_contacts

  Submit up to 500 contacts for a named batch business-fit analysis.

• list_batches

  List batch analyses by name with readable status and progress.

• get_batch

  Get readable batch progress and optionally one page of results.

• export_batch

  Create a short-lived CSV or JSON export link for a completed batch.

• email_intel

  Decide whether an email address is worth contacting, before drafting anything. Answers two independent questions: does the mailbox accept mail, and is the person still there. Catches what email verifiers miss — someone who left the…

• email_intel_bulk

  Assess a whole list of addresses in one call, before spending analysis on any of them. Same two questions as email_intel — does the mailbox accept mail, is the person still there — answered per address, and returned as a split by…

• build_icp_profile

  Build the seller's ICP profile by reading their own website: what they sell, the value proposition, which roles and industries they sell to, the pain points, proof points and tone of voice. The new profile becomes the active one, so every…

• company_signals

  Profile a company and its current moment before working its people. Given a domain or name, returns firmographics + revenue, team makeup, hiring velocity from careers (which catches layoffs a static card misses), activity signals…

• company_people

  Admin-only: the upstream refuses this tool for customer accounts, so do not offer it as an option — company_signals covers the account and analyze_contact covers the person. Get the people of a company and the addresses to reach them…

• company_search

  Find companies that fit — by industry, size, country, revenue, website tech, the tools their team uses inside, hiring, funding and what they are researching now — without people. Returns one row per company: name, domain, LinkedIn page…

• person_search

  Find people who fit — by role, company and timing — with their contacts. Returns one row per person: name, title, seniority, department, company and its website, LinkedIn, location, the work email at the CURRENT employer, all known work…

• person_signals

  Who a person is and what is going on with them. Given an email, LinkedIn URL, or slug, returns their role, grade and current company; the career trajectory from dates (months in the seat, whether they grew inside, their usual tenure)…

• add_opt_out

  Record a person in this account's opt-out list when they ask not to be contacted. Takes an email, phone or LinkedIn profile and detects which it is. Repeating a contact is safe — the second call reports it was already there instead of…

• remove_opt_out

  Take a contact off this account's opt-out list — for a record added by mistake, or a person who asked to be contacted again. Only a record this account created can be lifted: the list is shared, so one account must not undo an exclusion…