# Vc Finder (npm · @pipeworx/mcp-vc-finder)

vc-finder — VC / angel investor graph (Bruce ask 2026-09-29; built private-first, PUBLIC since…

- Trust score: 84/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 78/100, [markdown](https://verifymcp.io/servers/pipeworx-io-vc-finder/vc-finder-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-vc-finder/vc-finder-mcp)
- npm · `@pipeworx/mcp-vc-finder`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-vc-finder/pipeworx-mcp-vc-finder.md), [page](https://verifymcp.io/servers/pipeworx-io-vc-finder/pipeworx-mcp-vc-finder)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-vc-finder`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-vc-finder).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1673 tokens (~167/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Vc Finder MCP server?

Vc Finder runs locally as an npm package, launched with npx -y @pipeworx/mcp-vc-finder. 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 pipeworx-io-vc-finder -- npx -y @pipeworx/mcp-vc-finder
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-vc-finder": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-vc-finder"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-vc-finder": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-vc-finder"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-vc-finder -- npx -y @pipeworx/mcp-vc-finder
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-vc-finder": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-vc-finder"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-vc-finder --command npx --arg -y --arg @pipeworx/mcp-vc-finder
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-vc-finder:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-vc-finder"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-vc-finder": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-vc-finder"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-vc-finder -t stdio -c npx -a -y @pipeworx/mcp-vc-finder
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-vc-finder": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-vc-finder"
      ]
    }
  }
}
```

## 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-05 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (10)

### `vc_search_investors` (~253 tokens)

Search VC firms, CVCs, solo GPs, accelerators and angel groups by stated investment strategy — sector, stage, check size, geography. Stated-only (Phase 2); coverage is partial and every result carries its own per-fact sources.

Input parameters:

- `check_usd` (number): A check size in USD that must fall inside the investor's stated [check_min_usd, check_max_usd] range
- `geo` (string): HQ country, e.g. "US"
- `investor_type` (string): org_type filter: vc_firm, cvc, family_office, accelerator, angel_group, syndicate, solo_gp, pe_growth, studio
- `limit` (number): Max results (default 20)
- `name` (string): Substring/partial name search over canonical names and aliases (FTS5 trigram) — tolerant of truncation and minor character-level variation, not a full edit-distance fuzzy match
- `sector` (string): Stated sector/focus area, e.g. "devtools", "fintech"
- `stage` (string): Stated financing-round stage, e.g. "seed", "series_a"

Output parameters:

- `coverage` (string)
- `coverage_note` (string)
- `data_as_of` (string|null)
- `result` (array)

### `vc_get_investor` (~90 tokens)

Get one investor organization by id: identity, aliases, external ids (CRD/SEC#), funds, its investing people (partners, each with the contact routes they published, their source page and a personal/role label), the firm's own published contact routes, stated strategy, and per-fact sources.

Input parameters:

- `investor_id` (string, required): Organization id, from vc_search_investors

Output parameters:

- `coverage` (string)
- `coverage_note` (string)
- `data_as_of` (string|null)
- `result` (object|null)

### `vc_get_fund` (~66 tokens)

Get one private fund by id: name, vintage, VC-fund flag (ADV Schedule D 7.B), gross asset value, managing organization, and per-fact sources.

Input parameters:

- `fund_id` (string, required): Fund id, from vc_get_investor's funds list

Output parameters:

- `coverage` (string)
- `coverage_note` (string)
- `data_as_of` (string|null)
- `result` (object|null)

### `vc_get_company` (~43 tokens)

Get one company by id: identity, sector, maturity stage, and its financing rounds.

Input parameters:

- `company_id` (string, required): Company id, from vc_search_rounds

Output parameters:

- `coverage` (string)
- `coverage_note` (string)
- `data_as_of` (string|null)
- `result` (object|null)

### `vc_search_rounds` (~136 tokens)

Search financing rounds by sector, stage and date window — answers "funding rounds this week/quarter". Sourced from SEC Form D and newswire funding announcements; coverage is partial.

Input parameters:

- `date_from` (string): ISO date, inclusive lower bound on announced_date
- `date_to` (string): ISO date, inclusive upper bound on announced_date
- `limit` (number): Max results (default 20)
- `sector` (string): Company sector
- `stage` (string): financing_round_stage: pre_seed, seed, series_a, series_b, series_c_plus, growth, pe, ipo, other

Output parameters:

- `coverage` (string)
- `coverage_note` (string)
- `data_as_of` (string|null)
- `result` (array)

### `vc_who_invested_in` (~63 tokens)

List the investors named in a company's financing rounds — role (lead/participant), amount where disclosed, and the evidence (source URL + quoted snippet) behind each edge.

Input parameters:

- `company_id` (string, required): Company id, from vc_search_rounds

Output parameters:

- `coverage` (string)
- `coverage_note` (string)
- `data_as_of` (string|null)
- `result` (array)

### `vc_get_evidence` (~75 tokens)

Get the full provenance of one claim by id: source URL, source type, retrieval date, the extractor version, confidence, and the verbatim evidence text. Every other tool's "sources" field is a list of these ids.

Input parameters:

- `claim_id` (string, required): Claim id, from any other tool's sources array

Output parameters:

- `result` (object|null)

### `vc_find_investors_for_company` (~424 tokens)

Explainable stated-fit matcher (v0): for a company's sector, stage, check size and geography, rank candidate investors by an EXPLAINABLE CHECKLIST of five criteria (sector_match, stage_match, check_size_match, geo_match, active) plus relevant_portfolio_count — never a single opaque score. sector_match is true when the firm states the sector OR has observed portfolio companies in it; stage_match when it states the stage OR is on an observed round at that stage; check_size_match when its stated check range OR the range of disclosed round sizes it has been on contains check_usd (round sizes, not its own check). sector_basis / stage_basis / check_basis say which evidence decided (stated, observed, both). Accelerators (Y Combinator, Techstars, Antler, ...) are excluded unless include_accelerators is true. Each firm carries relevant_partner — the most senior investing person known there, with their published contact routes — or null when none is known. geo accepts any country spelling or ISO code (US, USA, United States) or a region (north_america, europe, asia_pacific, global); geo_match uses the firm's stated investment geography when it has one, else its HQ, and is null when there is no evidence either way. Sorted by criteria_met, then relevant_portfolio_count, then deals in the last 24 months, then sector focus (fewer declared sectors first), then name.

Input parameters:

- `check_usd` (number): Target check size in USD
- `geo` (string): Company country or region, e.g. "US", "United States", "north_america"
- `include_accelerators` (boolean): Also rank accelerators (Y Combinator, Techstars, Antler, ...). Default false.
- `limit` (number): Max candidates (default 10)
- `sector` (string, required): Company sector, e.g. "devtools"
- `stage` (string, required): Round stage being raised, e.g. "seed"

Output parameters:

- `coverage` (string)
- `coverage_note` (string)
- `data_as_of` (string|null)
- `result` (array)

### `vc_search_people` (~327 tokens)

Search investing people — partners, principals, associates, scouts, venture partners, fund GPs, angels, syndicate leads — by role, firm, the firm's sector, the firm's HQ geography, or name. Returns each person's current firms and which kinds of contact route they published (email, LinkedIn, X, personal site). Only people in an investing role are included. People and their contact routes come from public sources — the firm's own site or the person's own published page — and every route carries the page it was published on and the quoted text showing it. Phone numbers and home addresses are never collected. Anyone can request removal at support@pipeworx.io.

Input parameters:

- `firm` (string): Firm name, partial match over names and aliases
- `firm_id` (string): Organization id, from vc_search_investors
- `geo` (string): The firm's HQ country or region, e.g. "US", "United States", "europe"
- `limit` (number): Max results (default 20)
- `name` (string): Part of the person's name
- `role` (string): Investing role: partner, principal, associate, scout, venture_partner, operating_partner, angel, syndicate_lead, solo_gp, fund_gp, other_investor (or an org role such as gp, managing_director)
- `sector` (string): The firm's sector: a normalized leaf (e.g. "ai_infrastructure") or the firm's own stated tag
- `with_contact` (boolean): Only people who published at least one contact route

Output parameters:

- `coverage` (string)
- `coverage_note` (string)
- `data_as_of` (string|null)
- `result` (array)

### `vc_get_person` (~141 tokens)

Get one investing person by id: investing role, roles and firm history, companies, their own investments, and every contact route they published (email, LinkedIn, X, personal site), each with the page it was published on, the quoted text showing it, and whether it is a personal or a role address. Phone numbers and home addresses are never collected. People and their contact routes come from public sources — the firm's own site or the person's own published page. Anyone can request removal at support@pipeworx.io.

Input parameters:

- `person_id` (string, required): Person id, from vc_search_people, vc_get_investor partners, or relevant_partner

Output parameters:

- `coverage` (string)
- `coverage_note` (string)
- `data_as_of` (string|null)
- `result` (object|null)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-vc-finder/pipeworx-mcp-vc-finder#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80

## Common questions

### What is the Vc Finder MCP server?

Vc Finder is an MCP server listed in the public MCP registry as io.github.pipeworx-io/vc-finder. vc-finder, VC / angel investor graph (Bruce ask 2026-09-29; built private-first, PUBLIC since… This page covers its npm package (@pipeworx/mcp-vc-finder).

### Is the Vc Finder MCP server safe to use?

Vc Finder scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Vc Finder MCP server expose?

Vc Finder exposes 10 tools: vc_search_investors, vc_get_investor, vc_get_fund, vc_get_company, vc_search_rounds, and 5 more. Their descriptions and schemas cost roughly 1,618 tokens of context every time the server is loaded.

### Is the Vc Finder MCP server still maintained?

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

### What licence is the Vc Finder MCP server under?

Vc Finder declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Vc Finder MCP server?

VerifyMCP ran 16 checks on Vc Finder, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-vc-finder
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-vc-finder
- Repository: https://github.com/pipeworx-io/mcp-vc-finder
- Website: https://pipeworx.io/packs/vc-finder
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-vc-finder/pipeworx-mcp-vc-finder.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-vc-finder/pipeworx-mcp-vc-finder/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-vc-finder/pipeworx-mcp-vc-finder.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-vc-finder/pipeworx-mcp-vc-finder