YedaBase MCP server: search and open investor records (family offices, VCs, fund
YedaBase MCP server: search and open investor records (family offices, VCs, funds of funds, permanent capital, RIAs) from Claude, ChatGPT and other AI clients.
active Production-safe Score 95/100 http no auth
At a glance
| Endpoint | https://yedabase.com/mcp |
|---|---|
| Source | https://github.com/ChosenV24/yedabase-mcp |
| Transport | http |
| Tools | 21 |
| Auth | none |
| First seen | 2026-10-12 01:26:07 |
| Last checked | 2026-11-17 21:49:18 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 335 / 608 ms |
| Last successful check | 2026-11-17 21:49:18 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (21)
search_investors— Search the licensed investor database (Family office, Venture capital & startup investor, Fund of funds, Principal & permanent capital, RIA;get_investor— Full record of one firm: investor category, overview, inclusion evidence, the category's module columns (FoF strategies, PPC type, RIA segmeget_angles— Conversation angles for one firm: other firms that spoke at the same events/podcasts, shared causes, and similar investors (same type + counlist_fields— Investor categories and their Type lists, field definitions (with the categories each field applies to), allowed values and the rules for plcount_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 thecompare_investors— Returns the comparable fields of 2 to 5 firms in one call: category, type, location, primary and secondary domains, stage, check size, AUM aget_person— One decision-maker by id (pe_…) with their firm; contacts under the contacts-restricted rule. The person's firm is opened: Each firm whose fget_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): permy_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 notmy_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 reclist_playbooks— The seven YedaBase playbooks (step-by-step methods: Start, Match & Enrich, Investor Shortlist, Investor Research, Way In, Reach Out, Pipelinget_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 preget_resource— The same content as the MCP resources, inline: index (hashed firm index, CSV), adv-cache (public SEC Form ADV extract, CSV), vocabulary (fieget_help— One topic from the YedaBase help library (sending limits, LinkedIn, sign-in, connecting each AI client, seats and billing, the monthly allowyeda_status— Where this person stands: access level (preview or full), seat, workspace, onboarding notes done or missing and the YedaBase folder path, lisave_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 toadd_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=workspace_note— Read (text omitted) or replace (text given) one workspace note with a fixed name: about-us, connectors, events, team (shared by the workspacexport_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 pagunlock_investor— Preview accounts only: opens one locked firm's full record (overview, AUM as stored, decision-maker names and positions, philanthropy, news,
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:49:18 | ✓ | ✓ | 388 ms | 91 | active |
| 2026-11-17 21:34:11 | ✓ | ✓ | 328 ms | 91 | active |
| 2026-11-17 21:19:00 | ✓ | ✓ | 488 ms | 91 | active |
| 2026-11-17 21:03:53 | ✓ | ✓ | 277 ms | 94 | active |
| 2026-11-17 20:48:36 | ✓ | ✓ | 198 ms | 94 | active |
| 2026-11-17 20:33:31 | ✓ | ✓ | 382 ms | 91 | active |
| 2026-11-17 20:18:29 | ✓ | ✓ | 487 ms | 91 | active |
| 2026-11-17 20:02:59 | ✓ | ✓ | 233 ms | 94 | active |
| 2026-11-17 19:47:30 | ✓ | ✓ | 279 ms | 94 | active |
| 2026-11-17 19:32:24 | ✓ | ✓ | 237 ms | 94 | active |
| 2026-11-17 19:17:20 | ✓ | ✓ | 244 ms | 94 | active |
| 2026-11-17 19:01:46 | ✓ | ✓ | 340 ms | 91 | active |
| 2026-11-17 18:46:40 | ✓ | ✓ | 473 ms | 91 | active |
| 2026-11-17 18:31:39 | ✓ | ✓ | 373 ms | 91 | active |
| 2026-11-17 18:16:36 | ✓ | ✓ | 215 ms | 94 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://yedabase.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/yedabase-com-mcp # JSON