# Fund Momentum [Health: Active] **Category:** ๐Ÿ’ป Developer Tools **Repository:** https://github.com/schneidavie/fundmomentum **GitHub Stars:** 0 **Views:** 0 **Installs:** 0 **Upvotes:** 0 **Directory Page:** https://allmcps.com/mcp/fund-momentum ## Description 920+ active VC funds with live investor signals ## Tools Capabilities this server exposes over MCP: - **search_funds** โ€” Search actively deploying funds by stage, country, industry - **get_fund** โ€” Full fund profile with GP intelligence and a provenance block - **get_changes** โ€” Only the funds that changed since a timestamp โ€” for incremental sync - **get_fund_signals** โ€” Bullish/contrarian signals, deployment status, thesis tags - **get_gp_profile** โ€” Individual GP profiles and backgrounds - **match_startup** โ€” AI-powered fund matching based on startup description ## Claude Desktop Quick Installation Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client: ```json "mcpServers": { "fund-momentum": { "url": "https://fundmomentum.vc)**" } } ``` ## Documentation & README # Fund Momentum โ€” Live VC Intelligence Platform > 1000+ actively deploying VC funds ยท 413 disclosed LPs ยท GP Signal Profiles ยท FM15 Ranking ยท MCP Server for AI agents **[fundmomentum.vc](https://fundmomentum.vc)** ยท [MCP Docs](https://fundmomentum.vc/mcp) ยท [FM15 Ranking](https://fundmomentum.vc/fm15-2026) ยท [Smithery](https://smithery.ai/servers/djschneida/fundmomentum) ## Try it right now โ€” no key, no signup `search_funds` and `get_fund` answer 10 calls per caller per UTC day with **no credential at all**. Paste this: ```bash curl -s https://fundmomentum.vc/_api/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"search_funds","arguments":{"stage":"seed","country":"Germany","limit":5}},"id":1}' ``` Real data, no card, no email address. Quota headers, the free key and the other four tools: [MCP Server](#mcp-server). --- ## What is Fund Momentum? Fund Momentum is a live VC intelligence platform built for founders raising capital. We track **1000+ actively deploying VC funds** โ€” all raised capital since September 2024 โ€” plus **413 disclosed institutional LPs**, with weekly-updated GP Signal Profiles that go beyond fund basics. **The problem:** Most VC databases are graveyard tours. Funds that stopped deploying 18 months ago, GPs who moved on, theses that haven't been updated since the fund closed. Founders pitch 40 investors and discover half of them aren't writing checks anymore. **The solution:** Fund Momentum only lists funds that raised capital since September 2024. Every fund has verified deployment signals, not scraped summaries, and every fund profile carries a provenance block naming its source, last verification date and confidence. > The counts above are generated, not typed. [`scripts/sync-counts.sh`](https://github.com/schneidavie/fundmomentum/blob/HEAD/scripts/sync-counts.sh) > reads a live `SELECT COUNT(*)` from the [server card](https://fundmomentum.vc/_api/well-known/mcp/server-card) > and rounds the fund count down, so the published figure is always an > understatement rather than a stale boast โ€” see [Keeping the numbers honest](#keeping-the-numbers-honest). --- ## MCP Server Connect Claude, Cursor, or any MCP-compatible AI directly to Fund Momentum. ### The keyless trial `search_funds` and `get_fund` answer **10 calls per caller per UTC day with no credential at all**. No signup, no card, no key. This is the front door โ€” see real data before you decide anything. The curl at the top of this README is a complete, working call. Every response carries a `_meta` block telling you where you stand: ```json "_meta": { "auth": "keyless_trial", "calls_used": 1, "calls_limit": 10, "calls_remaining": 9, "resets_at": "2026-08-26T00:00:00.000Z" } ``` The keyless trial covers `search_funds` and `get_fund` only. `get_changes` is free but needs a key โ€” see below. ### Getting a key Both routes are free and take under a minute. **Humans:** [fundmomentum.vc/mcp](https://fundmomentum.vc/mcp) documents the MCP plans and the client setup; you subscribe and copy the key itself at [fundmomentum.vc/pricing](https://fundmomentum.vc/pricing). **Autonomous agents:** self-register and get a key **and 25 free credits** back in the same response. ```bash curl -s https://fundmomentum.vc/_api/agent/register \ -H "Content-Type: application/json" \ -d '{"agent_name":"your-agent-name","email":"you@example.com"}' ``` `201 Created`: ```json { "api_key": "...", "agent_credits": 25, "status": "registered", "free_credits_granted": 25, "email_verified": false, "credits_usable_now_on": ["search_funds", "get_fund", "get_changes"], "locked_until_email_verified": ["get_fund_signals", "get_gp_profile", "match_startup"], "cost_per_call": "โ‚ฌ0.01", "credits_never_expire": true, "mcp_endpoint": "https://fundmomentum.vc/_api/mcp", "auth_header": "X-API-Key", "buy_more": "https://fundmomentum.vc/for-agents" } ``` No payment, no approval step: an agent registers and makes a useful call in the same second. The 25 credits work **immediately** on `search_funds`, `get_fund` and `get_changes`. #### Unlocking the Pro tools Clicking the verification link in the registration email unlocks `get_fund_signals`, `get_gp_profile` and `match_startup` **on the same 25 credits**. It is free, one click, and not an upgrade โ€” it only proves the mailbox is real. Calling a locked tool before then returns `403`: ```json { "error_reason": "email_verification_required", "credits_remaining": 25, "tools_available_now": ["search_funds", "get_fund", "get_changes"], "tools_locked_until_verified": ["get_fund_signals", "get_gp_profile", "match_startup"], "cost_to_unlock": "โ‚ฌ0" } ``` The split exists because an unmetered grant of 25 calls against the โ‚ฌ29/mo tools was worth farming. Verification is the cheapest thing that makes a throwaway address useless without putting a human in the path of the first call. Registration is idempotent by mailbox. POSTing again with an address that already exists returns `200` with `"status": "existing"` and your **current** balance; it does not grant another 25. Matching is on the normalised mailbox, so `you+1@gmail.com`, `you+2@gmail.com` and `y.o.u@gmail.com` all resolve to the same account. New accounts are capped at **3 per IP per UTC day**. Over that, registration answers `429` and names the keyless fallback rather than leaving you stuck. Re-registering an existing address does not count against it. Every agent-tier response then carries its balance in `_meta`: ```json "_meta": { "credits_remaining": 24, "cost_per_call": "โ‚ฌ0.01", "billing": "per_call" } ``` `buy_more` is added to that block once `credits_remaining` drops below 100. #### When the credits run out Calls cost **โ‚ฌ0.01** each beyond the free 25, and credits never expire. An exhausted balance answers **HTTP `402`**: ```json { "error_reason": "no_credits", "credits_remaining": 0, "free_credits_on_registration": 25, "cost_per_call": "โ‚ฌ0.01", "credits_never_expire": true, "autonomous_payment_available": false, "buy_url": "https://fundmomentum.vc/for-agents", "fallback": { "tools": ["search_funds", "get_fund"], "calls_per_day": 10, "how": "send the request without an X-API-Key header" } } ``` This used to surface as JSON-RPC error `-32001`. It is now an HTTP `402` โ€” update any handler that matches on the old code. **A human has to top up.** Top-ups run through Stripe Checkout, which needs a person once; an agent cannot pay for itself. Machine payment (MPP / x402 pay-per-call) is planned but **not live**, which is why the error carries `autonomous_payment_available: false` โ€” do not build a flow that assumes an agent can buy its own credits. Once a human has topped up, the agent spends the balance unattended. Until then the fallback in that payload is real: drop the `X-API-Key` header and `search_funds` and `get_fund` still answer 10 calls per day with no credential. ### Quick Setup (Claude Desktop) Add to your `claude_desktop_config.json`: ```json { "mcpServers": { "fund-momentum": { "url": "https://fundmomentum.vc/_api/mcp", "headers": { "X-API-Key": "YOUR_API_KEY" } } } } ``` Restart Claude Desktop. Done. Drop the `headers` block entirely to run on the keyless trial. ### Example Queries ``` "Which seed funds in DACH invest in B2B SaaS and are deploying now?" "What is Speedinvest bullish on right now?" "Match my startup: AI-native fintech, seed stage, raising โ‚ฌ3M, Vienna" "What should I know before pitching Point Nine Capital?" "What changed in the fund database since last Monday?" ``` ### Available Tools (6) | Tool | Title | Tier | Description | |---|---|---|---| | `search_funds` | Search VC funds | Free | Search actively deploying funds by stage, country, industry | | `get_fund` | Get fund profile | Free | Full fund profile with GP intelligence and a provenance block | | `get_changes` | Get changed funds since | Free | Only the funds that changed since a timestamp โ€” for incremental sync | | `get_fund_signals` | Get fund investor signals | Pro | Bullish/contrarian signals, deployment status, thesis tags | | `get_gp_profile` | Get General Partner profiles | Pro | Individual GP profiles and backgrounds | | `match_startup` | Match startup to funds | Pro | AI-powered fund matching based on startup description | All six tools are read-only and non-destructive, and advertise it: `readOnlyHint: true`, `destructiveHint: false`, `idempotentHint: true`, `openWorldHint: false`. An agent can call any of them without a confirmation prompt โ€” nothing here mutates state. `search_funds` and `get_fund` were previously documented as **Starter**. They are **Free**. ### Incremental sync โ€” use `get_changes`, not a polling loop **Do not re-run `search_funds` on a schedule.** `get_changes` exists for exactly that job and is dramatically cheaper. The loop: 1. Call `get_changes` with a `since` timestamp. Omit `since` to get the last 7 days. 2. Keep the `next_since` and `etag` from the response. 3. Next poll, send `next_since` as `since` and the previous `etag` as `if_none_match`. 4. If nothing changed in that window, the reply is `unchanged: true` with zero rows โ€” a few bytes instead of a full page. ```json { "jsonrpc": "2.0", "method": "tools/call", "params": { "name": "get_changes", "arguments": { "since": "2026-08-20T00:00:00Z", "if_none_match": "\"2126d79bb6487457b97d8b05eb84253e\"", "limit": 50 } }, "id": 1 } ``` `since` accepts an ISO 8601 timestamp or a unix epoch in milliseconds as a string. `limit` is 1โ€“200, default 50. A changed window answers with the cursor fields plus the rows: ```json { "since": "2026-08-20T00:00:00.000Z", "since_defaulted": false, "next_since": "2026-08-25T16:00:21.418Z", "returned": 2, "total_changed": 4, "has_more": true, "etag": "\"2126d79bb6487457b97d8b05eb84253e\"", "changes": [ { "slug": "cloudberry-ventures-deeptech-fund", "name": "Cloudberry Ventures DeepTech Fund", "country": "United Kingdom", "fundingStage": "seed", "fundSize": "โ‚ฌ50M", "change_type": "signal_updated", "changed_at": "2026-08-24T04:00:22.242Z", "confidence": "high", "url": "https://fundmomentum.vc/funds/cloudberry-ventures-deeptech-fund" } ] } ``` When `has_more` is `true`, call again with the returned `next_since` before sleeping. **Plain HTTP alternative.** The same data is on `GET /_api/changes`, with the cursor as an ordinary conditional request โ€” keep the `ETag` response header and send it back as `If-None-Match`. An unchanged window answers `304 Not Modified` with an empty body. ### API Reference **Endpoint:** `POST https://fundmomentum.vc/_api/mcp` **Protocol:** JSON-RPC 2.0 over streamable HTTP **Server card:** [`/_api/well-known/mcp/server-card`](https://fundmomentum.vc/_api/well-known/mcp/server-card) **Auth:** `X-API-Key` header, or `Authorization: Bearer ` โ€” or nothing at all on the keyless trial ```python import requests r = requests.post( "https://fundmomentum.vc/_api/mcp", headers={"X-API-Key": "YOUR_KEY", "Content-Type": "application/json"}, json={ "jsonrpc": "2.0", "method": "tools/call", "params": { "name": "search_funds", "arguments": {"stage": "seed", "country": "Germany", "limit": 10} }, "id": 1 } ) print(r.json()) ``` ```typescript const r = await fetch("https://fundmomentum.vc/_api/mcp", { method: "POST", headers: { "X-API-Key": "YOUR_KEY", "Content-Type": "application/json" }, body: JSON.stringify({ jsonrpc: "2.0", method: "tools/call", params: { name: "get_fund_signals", arguments: { slug: "speedinvest" } }, id: 1 }) }); const data = await r.json(); ``` More in [examples/developers.md](https://github.com/schneidavie/fundmomentum/blob/HEAD/examples/developers.md) and [examples/founders.md](https://github.com/schneidavie/fundmomentum/blob/HEAD/examples/founders.md). --- ## GP Signal Profiles Beyond fund size and portfolio, Fund Momentum extracts how each GP actually thinks: - **Thesis Tags** โ€” specific investment focus areas - **Bullish Signals** โ€” what they're excited about right now - **Contrarian Signals** โ€” where they're betting against the consensus - **Deployment Score** โ€” how actively they're writing checks - **Founder Dos & Don'ts** โ€” how to pitch this specific fund Built from primary research: GP blog posts, fund websites, LinkedIn, published interviews. Not scraped summaries. --- ## FM15 โ€” Founder Alignment Ranking The FM15 is our semi-annual ranking of the 15 best **emerging** VC managers, scored on four dimensions: | Dimension | What we measure | |---|---| | LP Trust Signal | LP quality, re-ups, fund size trajectory | | Early Track Record | Portfolio performance, notable exits | | Thesis Sharpness | Specificity and differentiation of investment focus | | Founder Alignment | GP background, check size fit, post-investment support | **No AUM sorting. No paid inclusion. Primary research only.** โ†’ [View FM15 H1 2026](https://fundmomentum.vc/fm15-2026) --- ## MCP Pricing These tiers cover the MCP server and API only. | Tier | Price | API Calls | Tools | |---|---|---|---| | Keyless trial | โ‚ฌ0, no signup | 10/day per caller | `search_funds`, `get_fund` | | Free | โ‚ฌ0 | 100/mo | `search_funds`, `get_fund`, `get_changes` | | Starter | โ‚ฌ9/mo | 1,000/mo | `search_funds`, `get_fund`, `get_changes` | | Pro | โ‚ฌ29/mo | 10,000/mo | All six tools incl. signals | | Enterprise | Custom | Unlimited | All six tools, custom contract & SLA | The keyless, Free and Pro rows are generated from the server card. The Starter and Enterprise rows are still typed by hand โ€” the card exposes no tier block for them, so treat [fundmomentum.vc/pricing](https://fundmomentum.vc/pricing) as authoritative if those two ever disagree with this table. โ†’ [MCP plans & client setup](https://fundmomentum.vc/mcp) ยท [Subscribe & get a key](https://fundmomentum.vc/pricing) Founder and investor-signal plans for the platform itself are priced separately โ†’ [fundmomentum.vc/pricing](https://fundmomentum.vc/pricing) --- ## Keeping the numbers honest Fund and LP counts, the keyless and Free allowances and the Pro price in this README are **generated, not typed**. [`scripts/sync-counts.sh`](https://github.com/schneidavie/fundmomentum/blob/HEAD/scripts/sync-counts.sh) reads them from the live server card and rewrites the values between the `` marker pairs, plus `version` and `description` in [`server.json`](https://github.com/schneidavie/fundmomentum/blob/HEAD/server.json). Two numbers are **not** covered: the **Starter** and **Enterprise** rows in the pricing table. The server card exposes `authentication.free_tier` and a Pro price via `tools[].price`, but no tier block, so there is nothing to read them from. They stay hand-typed until the card grows one โ€” see the note at the top of [`scripts/sync-counts.sh`](https://github.com/schneidavie/fundmomentum/blob/HEAD/scripts/sync-counts.sh) for how to wire them up when it does. The fund count is published rounded down to the nearest hundred โ€” `1000+` today โ€” matching the site's own copy and the server card's note that marketing figures round the live count down. It still moves on its own as the database grows; it is simply never ahead of the truth. ```bash scripts/sync-counts.sh ``` ```bash scripts/sync-counts.sh --check ``` [`.github/workflows/sync-counts.yml`](https://github.com/schneidavie/fundmomentum/blob/HEAD/.github/workflows/sync-counts.yml) runs it weekly and commits any drift. [`.github/workflows/publish-mcp.yml`](https://github.com/schneidavie/fundmomentum/blob/HEAD/.github/workflows/publish-mcp.yml) runs it before every registry publish, so a release can never ship a stale count. To sync a number in a new spot, wrap it in a marker pair and it is picked up on the next run. The markers are invisible in rendered Markdown. --- ## Links - **Platform:** [fundmomentum.vc](https://fundmomentum.vc) - **MCP docs, plans & API keys:** [fundmomentum.vc/mcp](https://fundmomentum.vc/mcp) - **Founder / investor-signal pricing:** [fundmomentum.vc/pricing](https://fundmomentum.vc/pricing) - **Server card:** [fundmomentum.vc/_api/well-known/mcp/server-card](https://fundmomentum.vc/_api/well-known/mcp/server-card) - **Registry:** `io.github.schneidavie/fund-momentum` - **FM15 Ranking:** [fundmomentum.vc/fm15-2026](https://fundmomentum.vc/fm15-2026) - **Newsletter:** [schneida.substack.com](https://schneida.substack.com) - **Smithery:** [smithery.ai/servers/djschneida/fundmomentum](https://smithery.ai/servers/djschneida/fundmomentum) --- *Maintained by [Michael Schneider](https://www.linkedin.com/in/schneidavie) ยท Vienna, Austria*