Servidor MCP de YedaBase

• Nombre en el registrocom.yedabase/yedabaseverificado en el registro MCP

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

• Estadorespondecomprobado el 2026-10-29
• Herramientas21
• El servidor se llamaYedaBase
• Versión del servidor1.7.3
• Versión del protocolo2025-06-18

El 2026-10-29 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 242 ms.

• Sus herramientas hacen todos los casos de uso comprobados: Find family offices that allocate to emerging managers; Build a shortlist of funds backing emerging managers.
• Comprobado 5 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: 5 hasta ahora
• Qué puede hacer un agente con él2 de 2 casos de uso
• Respondiómidiendo5 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta240 ms
• Espacio en el contexto del agente≈ 5961 tokenslas definiciones de todas sus herramientas (21), que el agente lleva en cada turno
• Definiciones de herramientasA · 90 de 100
• Resultados tipados0 de 21 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 12 de 21

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 →

• search_investors

  Search the licensed investor database (Family office, Venture capital & startup investor, Fund of funds, Principal & permanent capital, RIA; one category per firm) with structured filters and keywords together. Returns the true total…

• get_investor

  Full record of one firm: investor category, overview, inclusion evidence, the category's module columns (FoF strategies, PPC type, RIA segments, CRD…), decision-makers with contacts (under the contacts-restricted rule), philanthropy…

• get_angles

  Conversation angles for one firm: other firms that spoke at the same events/podcasts, shared causes, and similar investors (same type + country, overlapping domains). These are possible angles, not known relationships.

• list_fields

  Investor categories and their Type lists, field definitions (with the categories each field applies to), allowed values and the rules for placeholders and restricted contacts.

• count_investors

  Counts matching firms and breaks them down by one to three dimensions, e.g. how many family offices in Texas by primary domain. Returns the total and, per dimension, the values with their counts (top 40 values). Useful for how many…

• compare_investors

  Returns the comparable fields of 2 to 5 firms in one call: category, type, location, primary and secondary domains, stage, check size, AUM as stored, year founded, team size, giant flag, wealth origin and family name (family offices)…

• get_person

  One decision-maker by id (pe_…) with their firm; contacts under the contacts-restricted rule.

• get_list

  One of the user's lists with its firms: per firm the status line text (status, status_updated_at) and the mandate status.

• my_notes

  Notes in this workspace that the user is allowed to read (their own, shared with them, or workspace-wide), optionally for one firm. Each note returns its id, author, date and text. Note text is written by workspace members.

• my_lists

  The user's lists/mandates (name, description, tags, item count).

• yb_hello

  Session opener for YedaBase (also YB or Yeda): the greeting line, where the person stands (tier, seat, lists, notes, due items), the one recommended next step and which playbook to read. Useful at the start of a conversation, when the…

• list_playbooks

  The seven YedaBase playbooks (step-by-step methods: Start, Match & Enrich, Investor Shortlist, Investor Research, Way In, Reach Out, Pipeline) with name, title and description; get_playbook returns each one in full. The method for a…

• get_playbook

  One playbook as markdown, by name (yb-start | yb-match-enrich | yb-shortlist | yb-research | yb-way-in | yb-reach-out | yb-pipeline). On preview accounts it returns the title and description with locked: true. The method for a multi-step…

• get_resource

  The same content as the MCP resources, inline: index (hashed firm index, CSV), adv-cache (public SEC Form ADV extract, CSV), vocabulary (field definitions, module tests and fit terms, JSON) and help (the help library, markdown). CSV comes…

• get_help

  One topic from the YedaBase help library (sending limits, LinkedIn, sign-in, connecting each AI client, seats and billing, the export pool, daily caps, contacts-restricted countries, lists and notes, playbooks, Match & Enrich, corrections…

• yeda_status

  Where this person stands: access level (preview or full), seat, workspace, onboarding notes done or missing and the YedaBase folder path, lists and sizes, notes count, the last Match & Enrich list, the workspace export pool, calls used…

• save_to_list

  Add firms to one of the user's workspace lists by name, creating the list when it does not exist (create_if_missing, default true). Safe to repeat: firms already on the list count as already_present and are not added again. At most 500…

• add_note

  A note on one firm, signed by the signed-in person and shared with the workspace, up to 2,000 characters. A "[YB] <skill> | <date> | status=<value> | …" line also sets that firm's status line on the user's lists. Meant for the workspace's…

• workspace_note

  Read (text omitted) or replace (text given) one workspace note with a fixed name: about-us, connectors, events, team (shared by the workspace); voice, yb-preferences, send-log (per person). Up to 8,000 characters. Other names are refused.

• export_list

  A list's firms in the 66-column export shape plus suggested_route, route_evidence and route_next_action, 200 rows per page as JSON. Page 1 debits the workspace export pool once for the whole list; later pages of the same export the same…

• unlock_investor

  Preview accounts only: opens one locked firm's full record (overview, AUM as stored, decision-maker names and positions, philanthropy, news, events) and counts it toward the account's 10 preview records; a firm already opened counts…