Servidor MCP de Aidenix

• Nombre en el registrocom.aidenix/aidenixverificado en el registro MCP

El nombre en el registro está bajo aidenix.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-11-03
• Herramientas18
• El servidor se llamaAidenix Insight MCP Server
• Versión del servidor1.28.1
• Versión del protocolo2025-06-18

El 2026-11-03 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 625 ms.

• Sus herramientas hacen todos los casos de uso comprobados: Score a company list by fit before sending; Check that contacts still work at their company.
• Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
• Qué puede hacer un agente con él2 de 2 casos de uso
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta645 ms
• Espacio en el contexto del agente≈ 5405 tokenslas definiciones de todas sus herramientas (18), que el agente lleva en cada turno
• Definiciones de herramientasA · 94 de 100
• Resultados tipados2 de 18 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 6 de 18

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y 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…