MCP server registry
Business operationsPublic source

Fundraise MCP Server

Startup fundraising intelligence for AI agents. 16 tools covering SAFE/convertible note conversion, dilution modeling, valuation estimation, runway calculation, metric benchmarking, term sheet comparison, red flag…

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

01

Real math — SAFE conversion handles cap, discount, MFN, and picks the better deal for the investor (as SAFEs actually work)

02

Real data — YC companies API (2000+), SEC EDGAR (10,000+ SAFE filings), live exchange rates (166 currencies)

03

Stage-aware — benchmarks, checklists, and multiples adjust by stage (pre-seed through Series C)

04

Founder-first — red flag detection tells you what investors will ask before they ask it

Architecture

How Fundraise MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

01

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

02

MCP client

Discovers schemas, sends calls, and receives typed content.

03

Fundraise MCP Server

Validates the request and owns 16 documented tool contracts.

04

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: rmcp

This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.

Tool catalog

What can an agent ask Fundraise MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

16 named tools

safe_convert

SAFE conversion at priced round (cap, discount, or both — uses better of two)

see documentation
dilution_model

Full dilution model: founders, investors, SAFE conversions, option pool shuffle

see documentation
valuation_estimate

Revenue multiple valuation by stage, sector, and growth rate

see documentation
runway_calculate

Months of runway with burn growth, revenue offset, zero-cash date

see documentation
financial_projection

MRR/ARR projections with churn impact, month-by-month

see documentation
metric_benchmark

Compare your metrics vs stage benchmarks (CAC, LTV, churn, NRR, burn multiple, etc)

see documentation
red_flag_check

Identify issues investors will flag (burn multiple, concentration, growth, LTV/CAC)

see documentation
data_room_checklist

Stage-appropriate document checklist for data rooms

see documentation
term_compare

Side-by-side term sheet comparison with dilution calc and flag detection

see documentation
currency_convert

Multi-currency conversion for international rounds (166 currencies, live rates)

see documentation
yc_search

Search 2000+ YC companies by batch, industry, or keyword (live API)

see documentation
sec_search

Search SEC EDGAR for SAFE agreements and fundraising filings (live API)

see documentation

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

16 see documentation
  • Review the server documentation and deployment credentials before enabling it for an agent.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.
rmcp

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install
cargo install mcp-fundraise
MCP client configuration
{
  "mcpServers": {
    "fundraise": { "command": "mcp-fundraise" }
  }
}

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Source record

Release and repository metadata for this catalog entry.

View public repository ↗
Version
1.0.0
License
Apache-2.0
Tools
16
Revision
3547ef93bc67
Updated
May 27, 2026
Transportsstdio