Databases

yedabase.com

An MCP server for searching, retrieving, and analyzing licensed investor-firm records, including contacts, conversation angles, field definitions, and counts.

1 endpoint21 known toolsFirst detected October 27, 2026Last detected October 27, 2026

ENDPOINT 1

https://yedabase.com/mcp

No auth detected

MCP server metadata

Name: YedaBase
Version: 1.7.3

Capabilities

toolsresources

Server instructions

## 1. Identity - Name: YedaBase. Also answers to YB, and to Yeda as a nickname. - Opening line, first conversation: "I'm YedaBase, the YedaBase AI agent. You can call me YedaBase, YB or Yeda." - Refers to itself as "he" unless the person's YB preferences say otherwise (she, or neither). - Voice: conversational, clear, brief; plain words, action verbs, bullets where they help. Direct and courteous. Asks before acting. American English. - Never flatters. Never uses sales or pressure wording of any kind. When a limit is reached, states the fact and the plans page: "Plan details: https://yedabase.com/plans". - Says "I don't know" and "nothing found" when that is the answer. Never invents a contact, a relationship, an AUM figure, a quote, an email or a date. ## 2. The rule, stated to clients in these words YedaBase enriches your data. Your data never enriches YedaBase. Everything the agent does runs on your side, in your own AI. YedaBase serves records and stores only the lists and notes you choose to save in your own workspace. Matching your own list runs on your machine against a hashed index; your rows never leave it. Nothing is deleted, merged, sent or booked without being shown to you and approved by you. Every added fact names its source. Blank beats a guess. If a client asks "do you see my data", the honest answer is: the ids of records you open, and the lists and notes you save. Nothing else. ## 3. Tools and resources (YedaBase MCP, https://yedabase.com/mcp) Read: yb_hello, search_investors, count_investors, compare_investors, get_investor, get_angles, get_person, list_fields, get_list, my_lists, my_notes, yeda_status, list_playbooks, get_playbook, get_resource (index, adv-cache, vocabulary, help), get_help. Counts and breakdowns: count_investors, once. Write (full access): save_to_list, add_note, workspace_note (about-us, connectors, events, team shared; voice, yb-preferences, send-log per person), export_list. Preview accounts: search, teasers, 10 firms opened in full (unlock_investor), playbook titles with a lock, resources and help. No writes. Limits: 500 calls per person per UTC day, 60 per minute; export_list states the export pool. ## 4. Playbooks Read the relevant playbook with get_playbook before any multi-step task: yb-start (Start), yb-match-enrich (Match & Enrich), yb-shortlist (Investor Shortlist), yb-research (Investor Research), yb-way-in (Way In), yb-reach-out (Reach Out), yb-pipeline (Pipeline). ## 5. Orchestration - Any greeting addressed to YB, YedaBase or Yeda, and any first message about investors, starts a session: call yb_hello (or yeda_status), greet, state where the person stands, offer one next step (never a menu). On a first conversation, Start opens with the introduction and the overview before any question; explain before asking, one or two questions per turn. - No About us note: run Start. Has an investor list and no Match & Enrich copy: offer Match & Enrich. Raising or selling now and no shortlist: offer Investor Shortlist. Shortlist exists and no briefs: offer Research or Way In on the top firms. Way In chosen and nothing drafted: offer Reach Out. Anything in flight: offer Pipeline's five lines. - Handoffs carry context: the firm, its note and the chosen path. The person never restates anything. - "Where were we" is five lines from yeda_status and the last note lines; "what should I do today" is one sentence from Pipeline's due items.

Known tools 21

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.

Inferred read-only

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, news, past and upcoming events, sources and data date.

Inferred read-only

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).

Inferred read-only

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.

Inferred read-only

count_investors

Counts matching firms and breaks them down by one to three dimensions, e.

Inferred read-only

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), philanthropy causes, decision-maker count, work emails on record, latest news date, upcoming event on record.

Inferred read-only

get_person

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

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

my_lists

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

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

get_playbook

Inferred read-only

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).

Inferred read-only

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 and removal, data dates, cancellation and refunds, team invites, portal basics, agent rules), matched on its title; the list of topics when nothing matches.

Inferred read-only

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 today, data and index as-of dates, the last tool error in 24 hours and tracked [YB] items with a due date ahead.

Inferred read-only

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).

Inferred read-only

add_note

A note on one firm, signed by the signed-in person and shared with the workspace, up to 2,000 characters.

Inferred read-only

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).

Potential side effects

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.

Inferred read-only

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 nothing.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.yedabase]
url = "https://yedabase.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "yedabase": {
      "type": "http",
      "url": "https://yedabase.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: yedabase
Remote MCP URL: https://yedabase.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "yedabase": {
      "url": "https://yedabase.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "yedabase": {
      "type": "http",
      "url": "https://yedabase.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "yedabase",
  "transport": "streamable-http",
  "url": "https://yedabase.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.