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.

InvestorMatch (public, no sign-in)

REMOTE · INVESTORMATCH.PRO

Search InvestorMatch's public directory of VC investors and fundraising guides. No sign-in needed.

+3 this week 89 Trust /100

Last scanned (3 hours ago)

Scores higher than 97% of remote servers

Reachable. Last reached 5 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 480 tokens (~120/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
    • Stability: 0.97 → pass security
  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

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

  • 27 Oct 26 +1

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

  • 25 Oct 26 +1

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

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

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

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 · Probed https://investormatch.pro/mcp/public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=investormatch.pro CN=YE2,O=Let's Encrypt,C=US 18 Sept 2026 17 Dec 2026 ECDSA 256 ECDSA-SHA384 5d16d562bd2c99e8ff3b182bb0a366fcc13
SANs: investormatch.pro
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of investormatch.pro. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
pro. present 33289 8 Verified
investormatch.pro. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy default-src 'self';script-src 'self' 'unsafe-inline' https://js.stripe.com https://www.googletagmanager.com https://www.google-analytics.com https://plausible.io;style-src 'self' 'unsafe-inline';font-src 'self' data:;img-src 'self' data: https: blob:;connect-src 'self' https://api.stripe.com https://www.google-analytics.com https://plausible.io https://api.openai.com https://api.anthropic.com https://storage.googleapis.com https://*.r2.cloudflarestorage.com;frame-src 'self' https://js.stripe.com https://hooks.stripe.com;media-src 'self' https:;object-src 'none';base-uri 'self';form-action 'self';frame-ancestors 'self';script-src-attr 'none';upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer
permissions-policy accelerometer=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(self "https://js.stripe.com" "https://checkout.stripe.com"), usb=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://investormatch.pro/mcp/public Verified 200
http (plaintext) http://investormatch.pro/mcp/public HTTPS enforced 301 https://investormatch.pro/mcp/public
MCP tools · 4 exposed · ~389 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
get_investor ~84

Get a venture capital firm's full public InvestorMatch profile by its slug (from search_investors): thesis, stages, sectors, check size, partners and their focus, recent portfolio companies, funds and how the firm prefers to be approached. Contact emails are never included.

NameTypeReqDescription
slugstringyesThe firm's slug, e.g. "sequoia-capital".

No output schema declared.

No examples provided.

list_investor_filters ~28

List the exact stage, sector and location values search_investors accepts as filters.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_fundraising_guides ~75

Search InvestorMatch's published fundraising guides and articles (pitch decks, investor outreach, valuations, term sheets and more). Returns up to 10 articles with a title, excerpt and link. Leave query empty for the latest articles.

NameTypeReqDescription
querystring–Topic keywords, e.g. "cold email to investors".

No output schema declared.

No examples provided.

search_investors ~202

Search InvestorMatch's public directory of venture capital firms. Filter by firm name (query), stage, sector and HQ location; results are sorted alphabetically, 25 per page (up to page 20). Each result has the firm's stages, sectors, check size, a thesis summary and a link to its InvestorMatch profile. The accepted stage, sector and location values are listed by list_investor_filters, and a firm's full profile is in get_investor.

NameTypeReqDescription
locationstring–A location slug from list_investor_filters, e.g. "london".
pageinteger–Page number, 1-20 (default 1).
querystring–Part of the firm's name, e.g. "sequoia".
sectorstring–A sector from list_investor_filters.
stagestring–A stage from list_investor_filters, e.g. "Seed".

No output schema declared.

No examples provided.

Install

How do I install the InvestorMatch (public, no sign-in) MCP server?

InvestorMatch (public, no sign-in) is a hosted endpoint at https://investormatch.pro/mcp/public, 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.

remote · investormatch.pro

# add to Claude Code
claude mcp add --transport http pro-investormatch-investor-match-public 'https://investormatch.pro/mcp/public'
Common questions

What is the InvestorMatch (public, no sign-in) MCP server?

InvestorMatch (public, no sign-in) is an MCP server listed in the public MCP registry as pro.investormatch/investor-match-public. Search InvestorMatch's public directory of VC investors and fundraising guides. No sign-in needed. This page covers its hosted endpoint (https://investormatch.pro/mcp/public).

Is the InvestorMatch (public, no sign-in) MCP server safe to use?

InvestorMatch (public, no sign-in) scores 89 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 InvestorMatch (public, no sign-in) MCP server expose?

InvestorMatch (public, no sign-in) exposes 4 tools: search_investors, get_investor, list_investor_filters, search_fundraising_guides. Their descriptions and schemas cost roughly 389 tokens of context every time the server is loaded.

Does the InvestorMatch (public, no sign-in) MCP server require authentication?

No. We connected to InvestorMatch (public, no sign-in) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the InvestorMatch (public, no sign-in) MCP server still maintained?

InvestorMatch (public, no sign-in) 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.