World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Agentic fundraising intelligence: 950+ tracked VC funds and 751 disclosed LPs over MCP
一覧は利用スコア(100 点満点)で並びます。内訳は次のとおり
| 人気 | 4/80 | GitHub スターか週間ダウンロード数。大きい方を 60、小さい方を 20 で数えます |
|---|---|---|
| 新しさ | 12/12 | 30 日以内のリリースかコード更新で満点 |
| 応答中 | 8/8 | 前回の確認でクラウドのエンドポイントが応答 |
| 利用スコア | 24/100 |
品質: 基本チェック 4/5 項目に合格(表示のみ、並び順には不使用) · 勢い: データなし (「急上昇」タブでのみ使用)
使っているAIアプリを選んで、設定をコピーしてください。
ひとことで AI にインストールしてもらう
Fund Momentum をインストールして。https://mcp.popnx.com/i/schneidavie-fund-momentum.md に従い、コマンドを見せて、私が OK するまで実行しないで。パソコンで作業できる AI(Claude Code や Cursor など)に貼り付けます。手順を読み、コマンドを見せて、あなたの OK を待ちます。キー不要・登録不要。 · AI が読む全文を見る
チェック 4/5 合格 · 質問内容は提供元のサーバー(fundmomentum.vc)を通ります · ✓ コマンド確認済み 2026年11月13日
まず:どの AI を使っていますか?
使っているアプリを選ぶと、下に手順が表示されます。
Claude につなげます · 約 2 分
キー不要、インストール不要 · claude.ai かデスクトップアプリで一度設定すれば、チャットで使えます · 無料アカウントは 1 つまで · Team/Enterprise はオーナー(Owner)が追加
CustomizeConnectors
ここからコピーして Claude の同じ名前の欄に貼り付け、Continue を押します
Fund Momentumhttps://fundmomentum.vc/_api/mcpClaude が検出したサインイン設定の画面で Continue を押す · Authentication は作者の説明どおり(Sign in now・Sign in when needed・No sign in)を選び Add を押します
+ConnectorsFund Momentum
Fund Momentum を使って、私に何ができるか教えて、1 つやってみせて✓ Claude が Fund Momentum を使っていると言うか、回答に Fund Momentum のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
ChatGPT との接続はプランしだい
フル MCP:Web 版 ChatGPT の Business・Enterprise・Edu · Pro:読み取り/取得の権限で接続、データを変えるツールは使えないことがあります · Plus:公式ドキュメントで未確認。プラグイン画面にカスタム MCP を追加する項目があれば試せます · Web のみ
Plugins+Add custom MCP server
名前を入れ、Connection にアドレスを貼り付け、注意事項にチェックして Create as a plugin を押します
Fund Momentumhttps://fundmomentum.vc/_api/mcp新しいチャットを開き、入力前にプラグインの一覧から Fund Momentum を選びます
Fund Momentum を使って、私に何ができるか教えて、1 つやってみせて✓ ChatGPT が Fund Momentum を使っていると言うか、回答に Fund Momentum のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に OpenAI のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Claude Code につなげます · 約 2 分
キー不要、インストール不要
Mac:Command+スペースで Terminal と入力 · Windows:PowerShell を開く
claude mcp add --transport http --scope user fund-momentum https://fundmomentum.vc/_api/mcpFund Momentum が一覧にあり、接続済みと表示されれば OK です
Fund Momentum を使って、私に何ができるか教えて、1 つやってみせて✓ Claude Code が Fund Momentum を使っていると言うか、回答に Fund Momentum のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Cursor につなげます · 約 2 分
キー不要、インストール不要
Fund Momentum を使って、私に何ができるか教えて、1 つやってみせて✓ Cursor が Fund Momentum を使っていると言うか、回答に Fund Momentum のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Cursor のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
VS Code につなげます · 約 2 分
キー不要、インストール不要
Fund Momentum を使って、私に何ができるか教えて、1 つやってみせて✓ VS Code が Fund Momentum を使っていると言うか、回答に Fund Momentum のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に VS Code のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Windsurf、Zed、Gemini CLI など MCP を使える他のアプリは追加方法がそれぞれ違います。アプリ一覧で確認してください
Web 経由でつなぐアプリ用のアドレス
https://fundmomentum.vc/_api/mcpJSON 設定は下の「開発者向け」にあります
Claude Code
claude mcp add --transport http --scope user fund-momentum https://fundmomentum.vc/_api/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"fund-momentum": {
"url": "https://fundmomentum.vc/_api/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"fund-momentum": {
"type": "http",
"url": "https://fundmomentum.vc/_api/mcp"
}
}
}説明は自動翻訳です。変数名は原文のままです。迷ったら原文を確認してください。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
このサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。
インターネット経由でつなげるアプリ
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
ツールの名前と説明は、サーバーが2026年11月17日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。
search_fundsSTART HERE for any question about funds. Search actively deploying venture capital funds by stage, country, industry and recent closes. Works with no API key at all (keyless trial); see the Cost line at the end for per-fund pricing on agent credits. Returns name, slug, country, s
get_fundTHEN: get the detailed profile of one fund, using a slug returned by search_funds. COST: free, no API key required. Every response carries a `provenance` block stating where each field came from (including per-field sources), when it was last verified, and how confident Fund Mome
get_changesFOR STAYING CURRENT, not for discovery: return only the funds whose data changed since a given timestamp. COST: free, no API key required. With no key it reaches back at most 7 days; a free key widens that to 30 days, and a paid caller is not limited. A shortened window is declar
get_fund_signalsDRILL DOWN on a fund you already identified with search_funds or get_fund. Returns investor signals: GP thesis, bullish and contrarian signals, founder dos and don'ts, deployment status and source URLs. This is the tool to use before writing an outreach message to a specific fund
get_gp_profileDRILL DOWN to the people: General Partner profiles for a fund you already identified. Use this when the question is who to approach and what they personally focus on, rather than what the fund does. COST: included in Pro, or €0.10 per call over MPP if you have no key. A fund with
match_startupALTERNATIVE ENTRY POINT when you do not know what to search for. Describe a startup in plain language and receive the top 10 matching funds, each with a slug, a reason and a score. Use this instead of search_funds when the brief is qualitative ('climate hardware, pre-seed, Europe
check_lp_coverageSTART HERE for any question about limited partners (LPs). Answers "does Fund Momentum cover my geography and LP type" with COUNTS ONLY: how many disclosed LPs match, how many of those have backed emerging managers, and how many have a known warm path in Michael's own network (`kn
search_lpsTHEN: return limited partner records (name, slug, LP type, HQ country and city, geographic focus, website, emerging-manager backing, verified flag, and michael_network: {has_warm_path: boolean, matches?}) filtered by country, LP type and emerging-manager backing, at most 25 per c
get_usageSTART HERE for 'how many calls or credits do I have left'. COST: free, no API key required, and it does not count against the keyless 10 calls per day (it is subject to the per-minute pace limit like every call). Returns your tier (keyless, free, starter, pro, enterprise or agent
send_feedbackTell the Fund Momentum team about a bug, a data problem or a missing feature. COST: free, no API key required, and it does not count against the keyless 10 calls per day; limited to 5 per caller per UTC day. Stores one short message and nothing else happens: nobody is notified in
request_warm_introAsk Michael for a warm intro to a fund or an LP. Fulfilled BY HAND through the same queue and Slack notification the website's own "Request a warm intro" button uses -- this is not an automated connection and carries no guaranteed timeline. A known match (get_fund's or search_lps
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月19日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント schneidavie で確認済みです
コードの最終更新:3 日前
リポジトリにライセンスファイルが見つかりません
1061ミリ秒で応答(HTTP 200)
サインイン不要
11件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/servers/schneidavie-fund-momentum)質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。
まだレビューはありません
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック5項目のうち4項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は3 日前、最新バージョン(1.9.0)がレジストリに届いたのは22 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URL で接続するので、リモート MCP を受け付けるアプリでも使えます。例:Web 版 ChatGPT(Business 以上はフル MCP、Pro は読み取りのみ)。
同じカテゴリには:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同じカテゴリでほかの作者のもの。コマンドは確認済み。公式を先に、次にスター順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| これ Fund Momentum | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 動く場所 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 |
| キーが必要 | いいえ | いいえ | いいえ | いいえ | いいえ | いいえ |
| Claude で + から追加 | いいえ | いいえ | いいえ | いいえ | いいえ | いいえ |
| 基本チェック | 4/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| ライセンス | – | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 料金 | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし |
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
Agentic fundraising intelligence for founders and emerging fund managers · 1000+ tracked VC funds · 812 disclosed LPs · LP Radar · Remote MCP server with pay-per-call
[fundmomentum.vc](https://fundmomentum.vc) · MCP Docs · LP Radar · FM15 Ranking · Smithery
search_funds, get_fund, get_changes and check_lp_coverage answer 10 calls per caller per UTC day between them with no credential at all. Paste this:
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.
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 subscribers (€199/month or €1,499/year, card checkout). See LP Radar over MCP.
Fund Momentum is agentic fundraising intelligence for founders and emerging fund managers. It tracks 1000+ 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 812 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
reads a live
SELECT COUNT(*)from the 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.
Connect Claude, Cursor, or any MCP-compatible AI directly to Fund Momentum.
search_funds, get_fund, get_changes and check_lp_coverage answer 10 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:
"_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. get_usage and send_feedback are also free and keyless, but unmetered: they never count against the daily allowance. 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.
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 (plus unmetered get_usage, send_feedback) | 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 is generated from the live tool definitions.
Both routes are free and take under a minute.
Humans: fundmomentum.vc/mcp documents the MCP plans and the client setup; you subscribe and copy the key itself at fundmomentum.vc/pricing.
Autonomous agents: no registration and no email are required at all. There is no `email` field on this endpoint.
curl -s https://fundmomentum.vc/_api/agent/register \
-H "Content-Type: application/json" \ -d '{"agent_name":"your-agent-name"}'
201 Created:
{
"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. check_lp_coverage never costs a credit, and search_lps is never sold on credits. See LP Radar over MCP.
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:
"_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.
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. 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.
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:
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 challenges in error.data.challenges, and the request id echoed back. Pay and retry with the credential in params._meta["org.paymentauth/credential"]; the receipt comes back in result._meta["org.paymentauth/receipt"]. A credential that does not verify answers -32043, never -32042, so you are not asked to pay twice.
Checked by the protocol's own validator against this server:
$ mppx validate https://fundmomentum.vc
Summary: 15 passed, 0 failed, 1 skipped
Everything structural passes, including the mainnet token and recipient addresses. The one skip is the payment step itself: the validator provisions a funded wallet on testnet only, and mainnet has no faucet. That step passes on the identical testnet deployment, with a real on-chain payment and a verified receipt (25/25).
Out of credits used to surface as JSON-RPC error -32001. It is now an HTTP 402. Update any handler matching the old code.
If you would rather not pay at all, the fallback is real: drop the X-API-Key header and search_funds, get_fund, get_changes and check_lp_coverage still answer 10 calls per day with no credential.
max_credits and billingsearch_funds costs 1 credit (€0.01) per fund returned, and an empty result costs nothing.
`max_credits` (optional, integer 1 to 25) caps the page at that many rows. It only lowers limit, it never raises it. Values above 25 are clamped to 25. Zero, negative and non-integer values are rejected before any charge. If you leave it out, your limit applies (default page: 10). Starter and Pro subscribers are never capped by it.
`billing` is added to every search_funds response:
{ "credits_charged": 4, "balance_after": 8, "next_page_cost": 4, "next_offset":