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.

F4 Raise

REMOTE · APP.F4.FUND

Ranks VC firms for a startup from a short description, with similar companies each firm backed.

Available components

+3 this week 73 Trust /100

Last scanned (17 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 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 Security63
Transport & Reachability100
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 959 tokens (~239/item across 4 items; 3 tools + 1 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 Management43
  • Stability observed for 13 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 3 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 12 Nov 26 +1

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

  • 10 Nov 26 +1

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

  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 67

    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 21 Nov 2026 · Probed https://app.f4.fund/api/public/raise/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.f4.fund CN=WE1,O=Google Trust Services,C=US 17 Oct 2026 15 Jan 2027 ECDSA 256 ECDSA-SHA256 a1aaa90b4ed806fa1362ed3150ba6bd3
SANs: app.f4.fund
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.f4.fund. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
fund. DS published 41510 8 Verified
f4.fund. No DS 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; includeSubDomains
content-security-policy object-src 'none'; frame-ancestors 'self'; base-uri 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy accelerometer=(),autoplay=(),camera=(),display-capture=(),encrypted-media=(),fullscreen=(self),geolocation=(),gyroscope=(),magnetometer=(),microphone=(),midi=(),payment=(),usb=(),xr-spatial-tracking=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.f4.fund/api/public/raise/mcp Verified 200
http (plaintext) http://app.f4.fund/api/public/raise/mcp HTTPS enforced 301 https://app.f4.fund/api/public/raise/mcp
MCP tools · 3 exposed · ~784 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
email_report_link ~185

Use this when a founder asks to have their F4 Raise report link emailed to them, giving their own address and the code from a find_vc_firms result. Emails the founder one message with a personal link that opens F4's free report form with the description already filled in. It needs the code at the end of the report link in a find_vc_firms result, and sends at most one email per code. F4 stores the email address with the search for 13 months and may email the founder about their raise. Every email includes a link to stop future emails. Each address has daily and weekly limits. The answer shows a masked address.

NameTypeReqDescription
codestringyesThe code at the end of the report link in a find_vc_firms result.
emailstringyesThe founder's email address, as the founder gave it.
NameTypeReqDescription
issuesarray––
maskedEmailstring––
messagestring––
retryAfterSecondsinteger––
statusstringyes–

No examples provided.

find_vc_firms ~454

Use this when a founder asks which venture capital investors to pitch, wants an investor list for a fundraise, or asks which VC firms back a kind of startup. Not for fundraising mechanics such as SAFEs, valuation or dilution, or for investor contact details. Ranks up to 20 public VC firms for a startup from a plain-language description of 10 to 500 characters. Each firm comes with up to three public companies it backed that resemble the startup, and a link to its F4 page. The result also carries one link to a free, longer report on f4.fund built from the company's pitch deck, which ranks about 100 firms. The optional stage removes firms whose stated stages are all two or more steps away from it, so a firm one stage away can remain. The optional round size removes firms whose smallest cheque is more than twice the round. The optional location lists firms whose stated geography excludes it after the firms that invest there. These are applied only when given. The optional website is used for its domain, and its home page may be read. F4 stores the description, website domain, stage and round size to fill in the report form and count how the plugin is used. Each call saves a new search and prefilled report link. It sends no email and contacts no firm, and it returns no contact details.

NameTypeReqDescription
descriptionstringyesWhat the startup does and for whom, in plain language, in the founder's words. 10 to 500 characters.
locationstring–Where the startup is based, only if the founder stated it. Firms whose stated geography excludes it are listed after the firms that invest there.
roundSizeUsdinteger–The size of the round in US dollars, only if the founder stated it. Firms whose smallest cheque is more than twice the round are removed.
stagestring–The funding stage of the round, only if the founder stated it. Firms whose stated stages are all two or more steps away from it are removed, so a firm one stage away can remain.
websitestring–The startup's website, only if the founder stated it. Only the domain is used.
NameTypeReqDescription
appliedobject––
codestring––
countinteger––
emailOfferedboolean––
firmsarray––
issuesarray––
messagestring––
methodstring––
missingstring––
reportUrlstring––
retryAfterSecondsinteger––
statusstringyes–

No examples provided.

get_vc_firm_details ~145

Use this when the user asks about a specific VC firm by name, or about a firm in a find_vc_firms result. Returns the public profile of one VC firm: name, location, website, a short thesis, the stages it has invested at, check size, sectors, geographies and up to 10 recent public portfolio companies. The firm is a slug from a find_vc_firms result or a name. It returns no contact details and no team names, and it covers only firms that have a public F4 page.

NameTypeReqDescription
firmstringyesA firm slug from a find_vc_firms result, or the firm's name.
NameTypeReqDescription
candidatesarray––
firmobject––
issuesarray––
messagestring––
notestring––
retryAfterSecondsinteger––
statusstringyes–

No examples provided.

Install

How do I install the F4 Raise MCP server?

F4 Raise is a hosted endpoint at https://app.f4.fund/api/public/raise/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.

remote · app.f4.fund

# add to Claude Code
claude mcp add --transport http fund-f4-raise 'https://app.f4.fund/api/public/raise/mcp'
Common questions

What is the F4 Raise MCP server?

F4 Raise is an MCP server listed in the public MCP registry as fund.f4/raise. Ranks VC firms for a startup from a short description, with similar companies each firm backed. This page covers its hosted endpoint (https://app.f4.fund/api/public/raise/mcp).

Is the F4 Raise MCP server safe to use?

F4 Raise 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 F4 Raise MCP server expose?

F4 Raise exposes 3 tools: find_vc_firms, get_vc_firm_details, email_report_link. Their descriptions and schemas cost roughly 784 tokens of context every time the server is loaded.

Does the F4 Raise MCP server require authentication?

No. We connected to F4 Raise without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the F4 Raise MCP server still maintained?

F4 Raise is still listed as active in the MCP registry. We last reached this channel on 21 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 F4 Raise MCP server?

VerifyMCP ran 14 checks on F4 Raise, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. 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.