fundmomentum

# Fund Momentum: the agentic pulse of Venture Capital

> Agentic fundraising intelligence for founders and emerging fund managers · <!--fm:funds-->1100+<!--/fm:funds--> tracked VC funds · <!--fm:lps-->721<!--/fm:lps--> disclosed LPs · LP Radar · Remote MCP server with pay-per-call

**[fundmomentum.vc](https://fundmomentum.vc)** · [MCP Docs](https://fundmomentum.vc/mcp) · [LP Radar](https://fundmomentum.vc/lp-radar) · [FM15 Ranking](https://fundmomentum.vc/fm15-2026) · [Smithery](https://smithery.ai/servers/djschneida/fundmomentum)

## Try it now: no key, no signup

`search_funds`, `get_fund`, `get_changes` and `check_lp_coverage` answer <!--fm:keyless_calls-->10<!--/fm:keyless_calls--> calls per caller per UTC day between them 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).

**New: LP data over MCP.** `check_lp_coverage` tells you, free and with no key, how many limited partners match a country and LP type. `search_lps` returns the LP records themselves for [LP Radar](https://fundmomentum.vc/lp-radar) subscribers (€199/month or €1,499/year, card checkout). See [LP Radar over MCP](#lp-radar-over-mcp).

---

## What is Fund Momentum?

Fund Momentum is agentic fundraising intelligence for founders and emerging fund managers. It tracks **<!--fm:funds-->1100+<!--/fm:funds--> VC funds**, every one of which raised capital since September 2024. Around 300 fund closings are covered as primary research, not scraped rows. **LP Radar** maps **<!--fm:lps-->721<!--/fm:lps--> disclosed LPs** and shows which of them back Fund I and II managers.

Your agent queries it over a remote MCP server. A founder asks Claude or ChatGPT who backs their round. An autonomous agent registers itself and pays per call.

**Why it exists:** a fund list ages fast. Funds stop deploying, GPs move on and theses drift. A fund that just closed has capital to deploy, so that is where Fund Momentum starts. Every fund profile carries a provenance block naming its source, the date it was last checked and a confidence level.

> The counts above are generated, not typed. [`scripts/sync-counts.sh`](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`, `get_fund`, `get_changes` and `check_lp_coverage` answer **<!--fm:keyless_calls-->10<!--/fm:keyless_calls--> calls per caller per UTC day between them, 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 those four tools. Keyless `get_changes` looks back at most **7 days** and answers `since_floor_applied: true` when it shortens your window; a free key widens that to 30 days. See [Incremental sync](#incremental-sync-use-get_changes-not-a-polling-loop).

### Access without registration

There is no signup wall. An agent can discover this server, pay for what it needs and get data with **no human, no account and no email** at any point.

| Access | How you get it | What works | Limits |
|---|---|---|---|
| **Keyless** | Nothing. Just call the endpoint. | `search_funds`, `get_fund`, `get_changes` (7-day window), `check_lp_coverage` | 10 calls/caller/UTC day |
| **Anonymous key** | `POST {"agent_name":"..."}` to `/_api/agent/register` | All six fund tools on credits. **25 free credits** on creation. | 3 new keys per IP, 10 per /24, per day |
| **Paid, inline** | Nothing. Call a Pro tool, get `402`, pay, retry. | All six fund tools, priced per call | €1,000 per payer per day |
| **Paid, prepaid** | `POST /_api/agent/credits/topup`, pay the challenge | All six fund tools on credits | €5 / €20 / €50 / €100 |
| **Linked** *(optional)* | `POST /_api/agent/link` with an email | Everything above, plus invoices and a dashboard | Grants no extra access |

Per-call prices are not repeated here, because a typed price drifts. Each tool states its own in its description, and [`/_api/mcp-tools`](https://fundmomentum.vc/_api/mcp-tools) is generated from the live tool definitions.

### 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:** no registration and no email are required at all. There is **no `email` field** on this endpoint.

```bash
curl -s https://fundmomentum.vc/_api/agent/register \
  -H "Content-Type: application/json" \
  -d '{"agent_name":"your-agent-name"}'
```

`201 Created`:

```json
{
  "api_key": "fm_agent_...",
  "agent_id": "agt_...",
  "status": "registered",
  "agent_credits": 25,
  "free_credits_granted": 25,
  "cost_per_free_call": "€0.01",
  "credits_never_expire": true,
  "tools_on_credits": ["search_funds", "get_fund", "get_changes"],
  "tools_paid_per_call": {
    "get_fund_signals": "…",
    "get_gp_profile": "…",
    "match_startup": "…"
  },
  "payment": {
    "protocol": "mpp",
    "methods": ["tempo_usdc"],
    "topup_endpoint": "/_api/agent/credits/topup",
    "daily_spend_limit": "€1000.00"
  },
  "link_email_endpoint": "/_api/agent/link",
  "mcp_endpoint": "https://fundmomentum.vc/_api/mcp"
}
```

No payment, no approval, no human: an agent registers and makes a useful call in the same second. The key is returned **once**. Only a SHA-256 hash is stored, so a lost key cannot be recovered.

`operator_url` and `contact` are optional free text and are never verified. Send an `email` and it is ignored with a note rather than rejected, so callers written against the old contract keep working.

The 25 credits work on **all six fund tools**. Free tools cost 1 credit (€0.01); the Pro tools are priced per call, as listed in [`/_api/mcp-tools`](https://fundmomentum.vc/_api/mcp-tools). `check_lp_coverage` never costs a credit, and `search_lps` is never sold on credits. See [LP Radar over MCP](#lp-radar-over-mcp).

#### Why there is no email step

An earlier release gated the Pro tools behind a clicked verification link. That was wrong for three reasons, and it is gone.

Most agents cannot read email, so it put a human step inside a flow that promises "register and call in the same second". It shared the `users` table with the human Google sign-up, so a person who had signed in with Google and then called this endpoint got back `status: "existing"`, a **null** API key, zero credits, and a response claiming all six tools were available. And it bought almost no protection anyway: throwaway addresses are free.

**Access control is pricing.** Pro data costs money per call, always, with no free path. Identity is the API key or, for inline payments, the paying wallet.

New keys are capped at **3 per IP** and **10 per /24** per UTC day. Over that, registration answers `429` naming both escape routes rather than leaving you stuck: the keyless tools, and inline payment, neither of which needs a key.

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.

#### Paying, with no account at all

**Autonomous machine payment is live on Tempo mainnet.** A Pro tool called with **no key whatsoever** answers HTTP `402` carrying a payment challenge over [MPP](https://mpp.dev). Pay it in USDC on Tempo (chain `4217`), retry, and you get the data plus a receipt. Nothing is registered and no account exists at any point.

```bash
curl -fsSL https://tempo.xyz/install | bash
tempo wallet login
tempo request -X POST --json '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"get_fund_signals","arguments":{"slug":"speedinvest-africa-fund"}},"id":1}' https://fundmomentum.vc/_api/mcp
```

The same flow tops up a key, so an agent never has to stop:

```bash
curl -s -X POST https://fundmomentum.vc/_api/agent/credits/topup \
  -H "X-API-Key: fm_agent_..." -H "Content-Type: application/json" \
  -d '{"amount_eur":20}'
```

`amount_eur` is 5, 20, 50 or 100. €20 buys 2,000 credits. The daily ceiling is checked **before** a challenge is issued, so you are never invited to pay for something that would then be refused. Spending is capped at **€1,000 per payer per UTC day**.

Prices are quoted in EUR and settle in USDC, converted at the ECB daily reference rate plus a 1.5% buffer for intraday movement and fees. There is no rounding up to the cent: €0.01 charges $0.0118, not $0.02.

The challenge arrives on a standard `WWW-Authenticate: Payment ...` header, and a paid response carries a `Payment-Receipt` header with the on-chain reference.

**Over MCP the shape is different, because it has to be.** An MCP client ignores the body of a `402`: it decides on the status line. So a caller that speaks MCP over Streamable HTTP (an `mcp-method` header, or an `Accept` listing both `application/json` and `text/event-stream`) gets HTTP `200` carrying a JSON-RPC error instead: `error.code` `-32042`, the c