# YedaBase (remote · yedabase.com)

Search and open investor records: family offices, VCs, funds of funds, permanent capital, RIAs.

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `yedabase.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-yedabase-yedabase/yedabase.md), [page](https://verifymcp.io/servers/com-yedabase-yedabase/yedabase)

## Channel facts

- Endpoint: `https://yedabase.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.7.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 81/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 51/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 5359 tokens (~255/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 76% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the YedaBase MCP server?

YedaBase is a hosted endpoint at https://yedabase.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-yedabase-yedabase 'https://yedabase.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.com-yedabase-yedabase]
url = "https://yedabase.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-yedabase-yedabase": {
      "type": "remote",
      "url": "https://yedabase.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-yedabase-yedabase --url 'https://yedabase.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-yedabase-yedabase:
    url: "https://yedabase.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-yedabase-yedabase": {
      "Transport": "http",
      "Url": "https://yedabase.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-yedabase-yedabase -t streamable-http -u 'https://yedabase.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 72, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-04 (score 72, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-03 (score 71, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-02 (score 71, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-01 (score 70, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-31 (score 70, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-30 (score 69, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (21)

### `search_investors` (~1373 tokens)

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, matching firms with location, domains, stage, AUM as stored, decision-maker counts (dm_count, email_count, linkedin_count), has_upcoming_event and the suggested_route, matched_by on each row (tag: has a requested domain tag; text: mentions a keyword in its record), directory_url (the same search in the YedaBase directory) and unmatched_values (domain values that are not stored tags, searched as keywords instead). Results are paged, 25 rows per page; the page argument returns more rows of the same search. Placeholder words (Undisclosed, Not provided, Unknown) are real stored values, not missing data.

Input parameters:

- `any_domain` (array): Matches primary OR secondary domains; industry sectors are stored here, e.g. Healthcare, Biotech, Digital Health, Medical Devices, Pharmaceuticals, Technology, Industrial, Consumer, Financial Service…
- `aum_disclosed` (boolean): Only firms whose AUM is a real value, not a placeholder
- `capital_source` (array): Principal & permanent capital only: Own balance sheet | Principals | Family or founder | Group | Foundation endowment | External, permanent or evergreen mandate
- `category` (array): Investor category, exact values: Family office | Venture capital & startup investor | Fund of funds | Principal & permanent capital | RIA. Filters by kind of investor (e.g. "RIAs", "funds of funds",…
- `cause` (array): Philanthropic causes (family offices; principal & permanent-capital firms where stated)
- `city` (string)
- `country` (array): Country names as stored, e.g. USA, United Kingdom, Switzerland
- `domain_mode` (string): How any_domain and keywords combine. tag_or_text: a firm matches when it has one of the domain tags OR its record mentions a keyword. tag: a firm matches when it has one of the domain tags AND its re…
- `emerging_manager_focus` (array): Fund of funds only: Y | N | Unknown
- `fof_strategy` (array): Fund of funds only: Primaries | Secondaries | Co-investments | Direct investments | GP stakes or seeding
- `geo_focus` (array): Geographic focus tags
- `giant_any` (boolean): Only billionaire families or 13F filers (family offices only)
- `has_news` (boolean): Only firms with news on record
- `has_philanthropy` (boolean): Only firms with philanthropy data (family offices and principal & permanent-capital firms only)
- `has_work_email` (boolean): Only firms with at least one work email on a decision-maker
- `investment_approach` (array): Principal & permanent capital: Control | Minority | Direct | Fund commitments | Credit | Real assets. RIA: Third-party funds | Direct | Co-invest | SPVs | OCIO mandates
- `keywords` (array): Words and phrases that describe what the person is looking for, beyond the exact tags: synonyms, sub-sectors, related terms, e.g. for healthcare: healthcare, medical, hospital, life sciences, biotech…
- `ownership` (array): RIA only: Founder-owned | PE-backed | Bank or insurer-owned | Public | Employee-owned
- `page` (integer)
- `page_size` (integer)
- `ppc_type` (array): Principal & permanent capital only: Investment holding company | Holding company / conglomerate investment arm | Permanent-capital acquisition firm | Evergreen investment vehicle (principal-backed) |…
- `primary_domain` (array): Primary investment domains are ASSET CLASSES, exact stored values: Private Equity | Real Estate | Startups | Public Equities | Venture Capital | Philanthropy | Private Credit | Impact | Hedge Funds |…
- `private_funds` (array): RIA only: Y | N
- `q` (string): Keyword search over firm name, description, city, family name, decision-maker names and research titles.
- `region` (array): North America | Europe | Middle East | South East Asia | Oceania | East Asia | LATAM | Africa
- `ria_segment` (array): RIA only: Alts allocator | Gatekeeper | Direct and co-invest | OCIO or consultant | M&A target | M&A acquirer
- `sort` (string)
- `stage` (array): Exact stored values: Pre-seed/Seed | Early | Growth | Buyout | Lower Middle Market | SMB
- `state` (array): US state names, e.g. Texas
- `type` (array): Investor type, exact stored values only; each category has its own list: Family office: Single family office | Multi family office | Family owned holding co | Family led private investment firm | VC/…
- `updated_since` (string): ISO date (YYYY-MM-DD): only firms whose record changed (data_version moved) on or after it

### `get_investor` (~132 tokens)

Open an 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), website, philanthropy, news, past and upcoming events, sources and data date. Each firm whose full record is returned counts once per seat per calendar month toward the allowance of 500 firms a month (opening it again this month is free); past the allowance the firm's teaser is returned instead.

Input parameters:

- `id_or_slug` (string, required): Firm id (fo_…) or slug

### `get_angles` (~59 tokens)

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

Input parameters:

- `id_or_slug` (string, required)

### `list_fields` (~37 tokens)

Fields and categories

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` (~1260 tokens)

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, breakdown, distribution and coverage questions; one call covers what paging through search results would.

Input parameters:

- `any_domain` (array): Matches primary OR secondary domains; industry sectors are stored here, e.g. Healthcare, Biotech, Digital Health, Medical Devices, Pharmaceuticals, Technology, Industrial, Consumer, Financial Service…
- `aum_disclosed` (boolean): Only firms whose AUM is a real value, not a placeholder
- `capital_source` (array): Principal & permanent capital only: Own balance sheet | Principals | Family or founder | Group | Foundation endowment | External, permanent or evergreen mandate
- `category` (array): Investor category, exact values: Family office | Venture capital & startup investor | Fund of funds | Principal & permanent capital | RIA. Filters by kind of investor (e.g. "RIAs", "funds of funds",…
- `cause` (array): Philanthropic causes (family offices; principal & permanent-capital firms where stated)
- `city` (string)
- `country` (array): Country names as stored, e.g. USA, United Kingdom, Switzerland
- `domain_mode` (string): How any_domain and keywords combine. tag_or_text: a firm matches when it has one of the domain tags OR its record mentions a keyword. tag: a firm matches when it has one of the domain tags AND its re…
- `emerging_manager_focus` (array): Fund of funds only: Y | N | Unknown
- `fof_strategy` (array): Fund of funds only: Primaries | Secondaries | Co-investments | Direct investments | GP stakes or seeding
- `geo_focus` (array): Geographic focus tags
- `giant_any` (boolean): Only billionaire families or 13F filers (family offices only)
- `group_by` (array): One to three dimensions to break the total down by.
- `has_news` (boolean): Only firms with news on record
- `has_philanthropy` (boolean): Only firms with philanthropy data (family offices and principal & permanent-capital firms only)
- `has_work_email` (boolean): Only firms with at least one work email on a decision-maker
- `investment_approach` (array): Principal & permanent capital: Control | Minority | Direct | Fund commitments | Credit | Real assets. RIA: Third-party funds | Direct | Co-invest | SPVs | OCIO mandates
- `keywords` (array): Words and phrases that describe what the person is looking for, beyond the exact tags: synonyms, sub-sectors, related terms, e.g. for healthcare: healthcare, medical, hospital, life sciences, biotech…
- `ownership` (array): RIA only: Founder-owned | PE-backed | Bank or insurer-owned | Public | Employee-owned
- `ppc_type` (array): Principal & permanent capital only: Investment holding company | Holding company / conglomerate investment arm | Permanent-capital acquisition firm | Evergreen investment vehicle (principal-backed) |…
- `primary_domain` (array): Primary investment domains are ASSET CLASSES, exact stored values: Private Equity | Real Estate | Startups | Public Equities | Venture Capital | Philanthropy | Private Credit | Impact | Hedge Funds |…
- `private_funds` (array): RIA only: Y | N
- `q` (string): Keyword search over firm name, description, city, family name, decision-maker names and research titles.
- `region` (array): North America | Europe | Middle East | South East Asia | Oceania | East Asia | LATAM | Africa
- `ria_segment` (array): RIA only: Alts allocator | Gatekeeper | Direct and co-invest | OCIO or consultant | M&A target | M&A acquirer
- `stage` (array): Exact stored values: Pre-seed/Seed | Early | Growth | Buyout | Lower Middle Market | SMB
- `state` (array): US state names, e.g. Texas
- `type` (array): Investor type, exact stored values only; each category has its own list: Family office: Single family office | Multi family office | Family owned holding co | Family led private investment firm | VC/…
- `updated_since` (string): ISO date (YYYY-MM-DD): only firms whose record changed (data_version moved) on or after it

### `compare_investors` (~165 tokens)

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. Each firm whose full record is returned counts once per seat per calendar month toward the allowance of 500 firms a month (opening it again this month is free); past the allowance the firm's teaser is returned instead. Useful for side-by-side questions; one call covers what opening each firm would.

Input parameters:

- `ids` (array, required): 2 to 5 firm ids (fo_...) or slugs

### `get_person` (~84 tokens)

Open a decision-maker

One decision-maker by id (pe_…) with their firm; contacts under the contacts-restricted rule. The person's firm is opened: Each firm whose full record is returned counts once per seat per calendar month toward the allowance of 500 firms a month (opening it again this month is free); past the allowance the firm's teaser is returned instead.

Input parameters:

- `id` (string, required)

### `get_list` (~100 tokens)

Open a list

One of the user's lists with its firms as ids and teasers (name, type, city, country, investment focus, AUM band, one-line description): per firm the status line text (status, status_updated_at), the mandate status and opened_this_month (already opened by this seat this month, so its full record costs nothing again). Full records come from get_investor or export_list. Counts nothing.

Input parameters:

- `id` (string, required)

### `my_notes` (~64 tokens)

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.

Input parameters:

- `firm_id` (string)

### `my_lists` (~24 tokens)

My lists

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

### `yb_hello` (~80 tokens)

Start a YedaBase session

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 user greets YedaBase, or asks where they left off.

### `list_playbooks` (~87 tokens)

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 multi-step task (shortlist, research, way in, reach out, pipeline, match and enrich, start).

### `get_playbook` (~136 tokens)

Open a 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 task (shortlist, research, way in, reach out, pipeline, match and enrich, start).

Input parameters:

- `name` (string, required): yb-start | yb-match-enrich | yb-shortlist | yb-research | yb-way-in | yb-reach-out | yb-pipeline

### `get_resource` (~97 tokens)

Read a 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 in pages of 2,000 rows with the header on every page. Nothing in these is a record.

Input parameters:

- `name` (string, required)
- `page` (integer)

### `get_help` (~103 tokens)

Help library

One topic from the YedaBase help library (sending limits, LinkedIn, sign-in, connecting each AI client, seats and billing, the monthly allowance of firms opened, 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.

Input parameters:

- `topic` (string)

### `yeda_status` (~116 tokens)

Account and session 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, firms opened this month (used, allowance, resets_on, per seat or pooled), 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. Useful at the start of a session or when asked where things stand.

### `save_to_list` (~127 tokens)

Save firms to a 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 firm ids per call. Returns list_id, added, already_present.

Input parameters:

- `create_if_missing` (boolean)
- `firm_ids` (array, required): Firm ids (fo_…)
- `list_name` (string, required): List name, up to 120 characters, e.g. "CRM matches 2026-10-15"

### `add_note` (~102 tokens)

Add a firm 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 own research on the firm, not for rows copied from a client's CRM.

Input parameters:

- `firm_id` (string, required)
- `text` (string, required)

### `workspace_note` (~81 tokens)

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.

Input parameters:

- `name` (string, required)
- `text` (string)

### `export_list` (~135 tokens)

Export a 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. Each page opens its firms: a firm counts once per seat per calendar month toward the allowance of 500 firms a month, and firms already opened this month (in the portal, through MCP or in an earlier export) are free. Firms past the allowance come back as teasers in blocked_firms. Up to 300 contacts per export (then contact columns are blank and contacts_truncated is true).

Input parameters:

- `list_id` (string, required)
- `page` (integer)

### `unlock_investor` (~130 tokens)

Open a locked investor (preview accounts)

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. Returns the record and the number of preview records left; when none are left it returns no_unlocks_left. On full-access accounts it returns the same result as get_investor. Work emails and LinkedIn profiles are not part of preview records.

Input parameters:

- `id` (string, required): Firm id (fo_…) or slug from search_investors

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-yedabase-yedabase/yedabase#diagnostics

## Score history

- 2026-11-06: 73
- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 69
- 2026-10-29: 69
- 2026-10-28: 68
- 2026-10-27: 68
- 2026-10-26: 67

## Common questions

### What is the YedaBase MCP server?

YedaBase is an MCP server listed in the public MCP registry as com.yedabase/yedabase. Search and open investor records: family offices, VCs, funds of funds, permanent capital, RIAs. This page covers its hosted endpoint (https://yedabase.com/mcp).

### Is the YedaBase MCP server safe to use?

YedaBase scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the YedaBase MCP server expose?

YedaBase exposes 21 tools: search_investors, get_investor, get_angles, list_fields, count_investors, and 16 more. Their descriptions and schemas cost roughly 4,492 tokens of context every time the server is loaded.

### Does the YedaBase MCP server require authentication?

Yes. YedaBase asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the YedaBase MCP server still maintained?

YedaBase is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the YedaBase MCP server?

VerifyMCP ran 12 checks on YedaBase, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about YedaBase: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://yedabase.com/mcp
- Website: https://yedabase.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-yedabase-yedabase/yedabase.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-yedabase-yedabase/yedabase/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-yedabase-yedabase/yedabase.json
- HTML version of this page: https://verifymcp.io/servers/com-yedabase-yedabase/yedabase
