Fund Momentum MCP Server
A remote MCP server for fundraising agents. Connect it to Claude or ChatGPT and research 950+ tracked VC funds in the chat you already work in. Start with no API key: search_funds, get_fund, get_changes and check_lp_coverage answer 10 calls a day with no signup.
This page is for people using an AI assistant. Building an autonomous agent that registers and pays for itself, with no human in the loop? Go to /for-agents →
Endpoint: POST https://fundmomentum.vc/_api/mcp
This page (/mcp) is documentation and does not accept POST. Requests sent here are rejected by the CDN before they reach the server. The server itself lives at /_api/mcp.
Try it before you subscribe. No signup.
On Claude Code or the Claude CLI, this is the whole setup:
No key in that command on purpose. You get 10 calls a day immediately; add the key later when you want more. Other clients: see the three steps below.
Set the connector up with no API key at all and ask your assistant for German seed funds. search_funds, get_fund, get_changes (7-day window) and check_lp_coverage answer 10 calls per caller per UTC day with no account and no key. That is enough to judge the data before you pay for it. Follow the steps below and leave the key out.
If you would rather confirm it is live without touching your assistant, this is the same call from a terminal:
Every response carries a _meta block with calls_used, calls_remaining and resets_at, so you always know where you stand. When you need more, the Free tier costs €0 and raises it to 100 calls/month, with a longer get_changes window.
How pay-per-call works
An autonomous agent can pay for itself. It registers with POST {"agent_name":"..."} to /_api/agent/register and gets a key plus 25 free credits. No email field.
When credit runs out, a paid tool answers HTTP 402 with a payment challenge. The agent pays it in USDC on Tempo through MPP and sends the call again. It gets the data plus a receipt. No account and no human in the loop.
A timed-out call returns the same challenge on retry. You never pay twice for one call. A wrong slug is rejected before any challenge is issued.
Prices are set in EUR. get_fund and get_changes cost €0.01 per call. search_funds costs €0.01 per fund returned, up to 150 funds per key per UTC day; the full list in one go is on the Pro plan. Every response reports matched and truncated. get_fund_signals and get_gp_profile cost €0.10. match_startup costs €0.25. Payments are final. No refunds. LP records are not sold per call: search_lps needs an LP Radar subscription on the key.
Endpoints, the payment flow and the limits in full: fundmomentum.vc/for-agents →
Available Tools
Find tracked VC funds by stage, country and industry, or by recent close with closed_since (newest close first). Returns slugs for get_fund. Works with no key.
One fund's full profile by slug: the latest covered close (type, date, amount as stated, source) and a provenance block with per-field sources. Works with no key.
Funds added, updated or with a new published close (close_updated) since a timestamp. Pass back next_since and etag instead of repeating searches. Works with no key over a 7-day window.
Deployment signals and thesis tags for one fund.
Backgrounds and track records of a fund's partners.
Describe a startup in plain text. Returns the 10 closest fund matches.
How many LPs match a country and LP type. Counts only, no names. Works with no key.
LP records, up to 25 per call, unlimited calls, on the key of an LP Radar account. Not sold per call or on credits.
Full parameter reference, accepted enum values and error codes, as plain Markdown that your assistant can read too: /_api/mcp-tools →
Every tool is read-only. Nothing you call here changes anything, in your account or in ours.
LP coverage is free here; LP records need LP Radar. check_lp_coverage returns counts only, with no key. search_lps returns records on the key of an account subscribed to LP Radar (€199 per month or €1,499 per year, card checkout, unlimited calls), and is never sold per call or on credits.
New closes, pulled or pushed
Every fund close we publish is written into the fund record. get_fund returns it as last_close: first, interim or final close, the date, the amount and currency exactly as the fund announced them, and the link to our post and the press release. search_funds with closed_since lists the funds that closed after a date, newest first, and get_changes marks them close_updated.
Webhooks (Pro and Enterprise). Subscribe an HTTPS endpoint and each new close arrives as a signed close_updated event, optionally filtered by stage, country and industry:
The response carries a signing secret, shown once. Each delivery has an FM-Signature: t=…,v1=… header: HMAC-SHA256 of "t.body" with that secret. Answer 2xx within 10 seconds; failures are retried with backoff for about two days. GET /_api/webhooks/list shows health and recent deliveries, POST /_api/webhooks/test sends a signed ping, POST /_api/webhooks/delete removes one. Up to five per key. Payload, headers and retry schedule: /_api/mcp-tools →
Every get_fund also says where each field came from in provenance.field_sources: the fund's own verified claim first, then our editors, our close coverage, the fund's website, and automated extraction last. GP names are only kept when a fetched source names them in full.
Four things to try first
Paste any of these into Claude, ChatGPT or Cursor once the connector is set up. Each one was run against live data. They chain the tools in the order that works, which is the single most common thing people get wrong: search first, then use the slug it gives you.
Using the Fund Momentum connector: find pre-seed funds headquartered in Austria that are actively deploying. For the three most relevant, pull the full profile and the investor signals, and tell me for each what they say founders get wrong. Start with search_funds and use the slugs it returns.
Using the Fund Momentum connector: call get_changes with since set to last Monday and show me every fund that was added or updated. Group them by country and flag anything above €100M. Keep the etag so I can ask again tomorrow without re-reading everything.
Using the Fund Momentum connector: I am building climate hardware for industrial heat decarbonisation, pre-seed, based in Europe. Run match_startup, then for the top five pull the GP profiles and tell me who personally to approach and why.
Using the Fund Momentum connector: give me a full briefing on Calm/Storm Ventures before my call. Find the fund with search_funds, then pull the profile, the investor signals and the GP profiles. Tell me their thesis, cheque size, how far into the fund they are, and what they look for. Cite the provenance for anything I might repeat back to them.
Connect in 3 steps
Subscribe at fundmomentum.vc/pricing
Free (100 calls/mo) · Starter €9/mo · Pro €29/mo
Copy your API key from Account Settings
Install for your AI client
Choose your AI client below and follow the steps.
Add Fund Momentum as a custom connector:
- Settings → Connectors → Add → Add custom connector
- Enter the following connector details:
- Name:
fund-momentum - MCP server URL:
https://fundmomentum.vc/_api/mcp
- Name:
- When prompted, add your API key as an
X-API-Keyheader. - From the Connectors page, open Fund Momentum settings and set Tool permissions to Always Allow.
- Ask Claude — "What can I do with Fund Momentum?"
Or paste directly into your config file:
Pricing
Free
€0/mo
- 100 calls/month
- search_funds, get_fund, get_changes
- Or 10 calls/day with no key at all