Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Vc Finder

NPM · @PIPEWORX/MCP-VC-FINDER · 2 COMPONENTS

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

+4 this week 84 Trust /100

Last scanned (8 hours ago)

Scores higher than 81% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-vc-finder). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +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.

  • 3 Nov 26 +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.

  • 1 Nov 26 +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.

  • 30 Oct 26 +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.

  • 29 Oct 26 80

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-vc-finder@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-vc-finder
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-vc-finder/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3560932162
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:f1934fa1207e9bc66ca7d0ce74f61c205b2aa5eab8f371490e89733a12b2d718da4caeae69f62253fd9a0a5bed593e6abb2a5f5ddecc9d080fb038ca8

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~1,618 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
vc_find_investors_for_company ~424

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.

NameTypeReqDescription
check_usdnumber–Target check size in USD
geostring–Company country or region, e.g. "US", "United States", "north_america"
include_acceleratorsboolean–Also rank accelerators (Y Combinator, Techstars, Antler, ...). Default false.
limitnumber–Max candidates (default 10)
sectorstringyesCompany sector, e.g. "devtools"
stagestringyesRound stage being raised, e.g. "seed"
NameTypeReqDescription
coveragestring––
coverage_notestring––
data_as_ofstring|null––
resultarray––

No examples provided.

vc_get_company ~43

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

NameTypeReqDescription
company_idstringyesCompany id, from vc_search_rounds
NameTypeReqDescription
coveragestring––
coverage_notestring––
data_as_ofstring|null––
resultobject|null––

No examples provided.

vc_get_evidence ~75

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.

NameTypeReqDescription
claim_idstringyesClaim id, from any other tool's sources array
NameTypeReqDescription
resultobject|null––

No examples provided.

vc_get_fund ~66

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.

NameTypeReqDescription
fund_idstringyesFund id, from vc_get_investor's funds list
NameTypeReqDescription
coveragestring––
coverage_notestring––
data_as_ofstring|null––
resultobject|null––

No examples provided.

vc_get_investor ~90

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.

NameTypeReqDescription
investor_idstringyesOrganization id, from vc_search_investors
NameTypeReqDescription
coveragestring––
coverage_notestring––
data_as_ofstring|null––
resultobject|null––

No examples provided.

vc_get_person ~141

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.

NameTypeReqDescription
person_idstringyesPerson id, from vc_search_people, vc_get_investor partners, or relevant_partner
NameTypeReqDescription
coveragestring––
coverage_notestring––
data_as_ofstring|null––
resultobject|null––

No examples provided.

vc_search_investors ~253

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.

NameTypeReqDescription
check_usdnumber–A check size in USD that must fall inside the investor's stated [check_min_usd, check_max_usd] range
geostring–HQ country, e.g. "US"
investor_typestring–org_type filter: vc_firm, cvc, family_office, accelerator, angel_group, syndicate, solo_gp, pe_growth, studio
limitnumber–Max results (default 20)
namestring–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
sectorstring–Stated sector/focus area, e.g. "devtools", "fintech"
stagestring–Stated financing-round stage, e.g. "seed", "series_a"
NameTypeReqDescription
coveragestring––
coverage_notestring––
data_as_ofstring|null––
resultarray––

No examples provided.

vc_search_people ~327

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.

NameTypeReqDescription
firmstring–Firm name, partial match over names and aliases
firm_idstring–Organization id, from vc_search_investors
geostring–The firm's HQ country or region, e.g. "US", "United States", "europe"
limitnumber–Max results (default 20)
namestring–Part of the person's name
rolestring–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)
sectorstring–The firm's sector: a normalized leaf (e.g. "ai_infrastructure") or the firm's own stated tag
with_contactboolean–Only people who published at least one contact route
NameTypeReqDescription
coveragestring––
coverage_notestring––
data_as_ofstring|null––
resultarray––

No examples provided.

vc_search_rounds ~136

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.

NameTypeReqDescription
date_fromstring–ISO date, inclusive lower bound on announced_date
date_tostring–ISO date, inclusive upper bound on announced_date
limitnumber–Max results (default 20)
sectorstring–Company sector
stagestring–financing_round_stage: pre_seed, seed, series_a, series_b, series_c_plus, growth, pe, ipo, other
NameTypeReqDescription
coveragestring––
coverage_notestring––
data_as_ofstring|null––
resultarray––

No examples provided.

vc_who_invested_in ~63

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.

NameTypeReqDescription
company_idstringyesCompany id, from vc_search_rounds
NameTypeReqDescription
coveragestring––
coverage_notestring––
data_as_ofstring|null––
resultarray––

No examples provided.

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.

npm · @pipeworx/mcp-vc-finder

# add to Claude Code
claude mcp add pipeworx-io-vc-finder -- npx -y @pipeworx/mcp-vc-finder
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.