YedaBase MCP server

• Registry namecom.yedabase/yedabaseverified in the MCP registry

The registry name sits under yedabase.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-29
• Tools21
• Server calls itselfYedaBase
• Server version1.7.3
• Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 242 ms.

• Its tools do every use case we checked: Find family offices that allocate to emerging managers; Build a shortlist of funds backing emerging managers.
• Checked on 5 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring5 of the 7 daily checks it takes to print a share
• Median first answer240 ms
• Space in an agent's context≈ 5,961 tokensthe definitions of all its tools (21), which an agent carries on every turn
• Tool definitionsA · 90 of 100
• Typed results0 of 21 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 12 of 21

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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…